Date: Wed, 07 Oct 1998 17:20:26 -0500 From: Jacques Vidrine <n@nectar.com> To: asami@FreeBSD.ORG (Satoshi Asami) Cc: ports@FreeBSD.ORG Subject: Re: What's the right way to handle old bsd.port.mk? Message-ID: <E0zR1wY-0006GF-00@spawn.nectar.com> In-Reply-To: <199810072128.OAA11079@silvia.hip.berkeley.edu> References: <199810072128.OAA11079@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Point me to the documentation in question and I'd be glad to add a paragraph or two about keeping up with ports if it appears to be needed. Hmm, now I get why NetBSD has their makefiles as part of the collection rather than part of the base system. Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org On 7 October 1998 at 14:28, asami@FreeBSD.ORG (Satoshi Asami) wrote: > * What should a port that needs to know PORTOBJFORMAT do on a system > * with an older bsd.port.mk? > > Nothing. Ports shipped with releases go out with matching > bsd.port.mk's; people using ports-current are expected to get the > latest bsd.port.mk. > > The latter part is becoming more of a problem lately; maybe if you can > go look into documentation to make it clearer, it will be a much > better use of your time IMO. :) > > Satoshi > -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNhvpKjeRhT8JRySpAQESoQP/WWqC7FyqzlKxdSYN9jPLktTl475xmg64 pmJryRVh4/uoa6PGBc9ajMmAzzqbjWPLlJ6b/XcMWC6idtkrD3J2aElCAE50Mpfe 0uXG4jYFAX4G201YLkbAXO/nR6R2eK1BWBX1jKSd57t2tkA66uXP2vYvHbCkp5oB Oo3k924XhyI= =+o0K -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0zR1wY-0006GF-00>