DragonFly kernel List (threaded) for 2003-11
Re: HEADS UP: Name change committed
Garance A Drosihn wrote:
At 9:05 PM -0800 11/18/03, Matthew Dillon wrote:
:That get me wondering what's DragonFly's plan to have branches?
I'd personally rather not have branches. I think we can
do it by simply using tags.
I think that once DragonFly goes "production", users will want
branches. They'll want something like the freebsd-security
(or maybe call it freebsd-safe) branch.
I'm not sure that will be needed once we vfs layering is complete along
with the packaging system. All of the security updates can be pushed out
via a tagging inside the packaging system. Hence everything in the system
will have a tag on it. ex:
Not uptodate; current: 1.27
Or something along those lines. This should prevent the huge mistake(s)
goes on now with MFC'ing items. This will allow users to try new
out affecting the rest of the system. Hence sh 1.27 needs a newer libc.
packaging system will then make use of the vfs layering and install them
out conflicting with the current libc which everything currently uses.
With the goals
DragonFly is working towards security branches won't be needed anymore.
will have fine grained control over what is installed and limitless ways
they can run