DragonFly versioning plan

Justin Sherrill justin at shiningsilence.com
Tue Sep 13 19:25:26 PDT 2011

We could do that - technically, a forced install of a newer
pkg_install build from binary would work.  It still requires a
separate step from the user to remove that stopping point, and I'd
like updating to _always_ work, in general.

My opinion is that required updated pkgsrc tools should be considered
dependencies the same as with other software, and should get installed
when available and needed, same as any other part.  That doesn't
happen with pkgsrc - yet.

On Tue, Sep 13, 2011 at 12:46 AM, Matthew Dillon
<dillon at apollo.backplane.com> wrote:
>    This 'pristine' install from scratch is something we already generate
>    when we are doing a pkgsrc bulk build, its the first thing we do before
>    we start the bulk build process (building the bootstrap and a few selected
>    additional utilities).  We'd just package that up as a separate entity
>    that the user script can download separately, before moving on to the
>    bulk build.

More information about the Kernel mailing list