Date: Thu, 24 Mar 2011 11:30:26 -0700 From: Doug Barton <dougb@FreeBSD.org> To: perryh@pluto.rain.com Cc: jumper99@gmx.de, freebsd-ports@freebsd.org Subject: Re: [HEADS UP] Ports Infrastructure Changes Message-ID: <4D8B8DC2.3060205@FreeBSD.org> In-Reply-To: <4d8aff41.geXhDZxdzW%2Bc8d48%perryh@pluto.rain.com> References: <alpine.BSF.2.00.1103192316110.84574@dee.signature.nl> <AANLkTim5Lf31sJH634sb976xDsekg53jQmvenYcuR9dq@mail.gmail.com> <op.vsslnf05oxde33@pete01.gateway.2wire.net> <4D8A2A79.4010908@FreeBSD.org> <xn0hbyv0sk7vg6002@news.gmane.org> <4D8A4732.20804@FreeBSD.org> <4d8aff41.geXhDZxdzW%2Bc8d48%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/24/2011 01:22, perryh@pluto.rain.com wrote: > Doug Barton<dougb@freebsd.org> wrote: > >>> This would be a good time to include ports-mgmt/pkg_search into >>> the base system... >> >> It would be a better idea to put the pkg_* tools IN the ports tree >> where they belong. :) > > Wouldn't this lead to a chicken-egg problem for those who use > packages? How would one go about installing the package installer? 1) The system installer installs the package that contains the latest version of the pkg_* tools by default. 2) Have a stub program in the base whose only purpose is to download and install the latest version of the pkg_* tools. The benefits of this are that we can introduce new features to the pkg_* tools very quickly, rather than with a 3 year (or more) lead time like we do now. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D8B8DC2.3060205>