[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sponsors.



Yes, I realize that each os has its own way of doing things.  If it
were in OpenBSD, it would become the new pkg tools just like you suggest
in FreeBSD, just a different directory: src/usr.sbin/pkg_install.  However
you slice it, you've got the 'current' os releases people are using that won't
necessarily work with the bsdports tree, and the future ones that will.  That
is the issue I meant to raise.  This either will have to be addressed, or
a minimum os revision be required for people to use the initial tree.  And
a headache of a tracking system to determine when 'new features' are introduced
into the bsdports tree and what os revisions they require and who can install
what ..

On Mon, Aug 28, 2000 at 11:47:46PM -0700, David O'Brien wrote:
> On Tue, Aug 29, 2000 at 01:26:41AM -0500, Todd T. Fries wrote:
> > Hmm, question.  If we use the bsdports tree to build pkg_* and install them
> > as a package, this means a bootstrap stage compatible with the least common
> 
> The FreeBSD way of doing this would be to import the bsdports pkg_*
> source tree into src/contrib, and then update it perodically.  This way
> the development happens by the bsdports group, but the software is in the
> base system so it can be depended on being present.
> 
> -- 
> -- David    (obrien@NUXI.com)

-- 
Todd Fries .. todd@fries.net

To unsubscribe: send mail to <majordomo@unixathome.org>
with "unsubscribe bsdports" in the body of the message