I've read again through the OBSOLETE section. I'm prepared to drop a large
part of it.
Some descriptions contain very useful hints as to what's actually going on
(and some things are still there, the redirect from /usr/share/mk/bsd.port.mk
to ${PORTSDIR}/infrastructure/mk/bsd.port.mk)
The remaini
Daniel Jakots wrote:
> On Sat, 16 Apr 2022 20:59:08 -0400, Kurt Mosiejczuk
> wrote:
>
> > I'd like to lose that whole section since most of it is many many
> > years old and seems more of historical interest rather than practical
> > advice at this point.
> >
> > ok?
>
> ok danj@
I don't wor
On Sat, 16 Apr 2022 20:59:08 -0400, Kurt Mosiejczuk
wrote:
> I'd like to lose that whole section since most of it is many many
> years old and seems more of historical interest rather than practical
> advice at this point.
>
> ok?
ok danj@
Marc Espie writes:
> On Mon, Apr 18, 2022 at 07:07:59PM -0400, Kurt Mosiejczuk wrote:
>> On Mon, Apr 18, 2022 at 06:09:12PM +0200, Marc Espie wrote:
>>
>> > > Do we tell them to peak into FreeBSD ports anywhere?
>>
>> > Unless that's been removed from the ports FAQ or general advice recently,
On Mon, Apr 18, 2022 at 07:07:59PM -0400, Kurt Mosiejczuk wrote:
> On Mon, Apr 18, 2022 at 06:09:12PM +0200, Marc Espie wrote:
>
> > > Do we tell them to peak into FreeBSD ports anywhere?
>
> > Unless that's been removed from the ports FAQ or general advice recently,
> > yes.
>
> There's no refe
On Mon, Apr 18, 2022 at 06:09:12PM +0200, Marc Espie wrote:
> > Do we tell them to peak into FreeBSD ports anywhere?
> Unless that's been removed from the ports FAQ or general advice recently,
> yes.
There's no reference to NetBSD or FreeBSD in the ports FAQ.
While I have known folks to be told
Marc Espie writes:
> On Mon, Apr 18, 2022 at 09:31:05AM -0600, Aaron Bieber wrote:
>>
>> Marc Espie writes:
>>
>> > On Sun, Apr 17, 2022 at 12:21:32PM -0400, Kurt Mosiejczuk wrote:
>> >> Beyond which, we don't keep legacy pf.conf information around because the
>> >> other BSDs use an ancient
On Mon, Apr 18, 2022 at 09:31:05AM -0600, Aaron Bieber wrote:
>
> Marc Espie writes:
>
> > On Sun, Apr 17, 2022 at 12:21:32PM -0400, Kurt Mosiejczuk wrote:
> >> Beyond which, we don't keep legacy pf.conf information around because the
> >> other BSDs use an ancient version of PF and they might w
Marc Espie writes:
> On Sun, Apr 17, 2022 at 12:21:32PM -0400, Kurt Mosiejczuk wrote:
>> Beyond which, we don't keep legacy pf.conf information around because the
>> other BSDs use an ancient version of PF and they might want to migrate to
>> OpenBSD.
>
> We also don't tell people to peek into
Marc Espie:
> Could you please check other bsds as well ?
> That section is also useful when people grab a port from net/freebsd
> with which we share quite a few variables.
But we don't document all the new infrastructure that NetBSD and
FreeBSD have grown, so I don't think the section is actual
> On Apr 17, 2022, at 10:55 AM, Marc Espie wrote:
> On Sun, Apr 17, 2022 at 12:21:32PM -0400, Kurt Mosiejczuk wrote:
>> Beyond which, we don't keep legacy pf.conf information around because the
>> other BSDs use an ancient version of PF and they might want to migrate to
>> OpenBSD.
>
> We al
On Sun, Apr 17, 2022 at 12:21:32PM -0400, Kurt Mosiejczuk wrote:
> Beyond which, we don't keep legacy pf.conf information around because the
> other BSDs use an ancient version of PF and they might want to migrate to
> OpenBSD.
We also don't tell people to peek into FreeBSD's config for pf, wherea
On Sun, Apr 17, 2022 at 12:44:55PM +0200, Marc Espie wrote:
> > > Could you please check other bsds as well ?
> > > That section is also useful when people grab a port from net/freebsd
> > > with which we share quite a few variables.
> > That sounds like it would be better suited in the ports FAQ
On Sun, Apr 17, 2022 at 03:24:34AM -0400, Kurt Mosiejczuk wrote:
> On Sun, Apr 17, 2022 at 08:40:39AM +0200, Marc Espie wrote:
> > On Sat, Apr 16, 2022 at 08:59:08PM -0400, Kurt Mosiejczuk wrote:
> > > Had someone at work ask me a question about a port, and they found
> > > EXTRACT_CMD in the man p
On Sun, Apr 17, 2022 at 08:40:39AM +0200, Marc Espie wrote:
> On Sat, Apr 16, 2022 at 08:59:08PM -0400, Kurt Mosiejczuk wrote:
> > Had someone at work ask me a question about a port, and they found
> > EXTRACT_CMD in the man page and thought that was their answer. Execept
> > that is in the OBSOLET
On Sat, Apr 16, 2022 at 08:59:08PM -0400, Kurt Mosiejczuk wrote:
> Had someone at work ask me a question about a port, and they found
> EXTRACT_CMD in the man page and thought that was their answer. Execept
> that is in the OBSOLETE VARIABLES section.
>
> Most of the information in the OBSOLETE se
Had someone at work ask me a question about a port, and they found
EXTRACT_CMD in the man page and thought that was their answer. Execept
that is in the OBSOLETE VARIABLES section.
Most of the information in the OBSOLETE sections is ancient. I think the
newest variable listed is PERMIT_PACKAGE_CDR
17 matches
Mail list logo
