DragonFly kernel List (threaded) for 2004-08
Re: cvsup, installer and booting
On Tue, 2004-08-03 at 20:51, George Georgalis wrote:
> On Tue, Aug 03, 2004 at 09:56:00PM +0200, Sascha Wildner wrote:
> >George Georgalis wrote:
> >>My first attempt installed and booted fine; but I had a problem
> >>with cvsup. I ended up using "*default release=cvs" in both
> >>dragonfly-cvs-supfile and FreeBSD-ports-supfile, but that gives me "*,v"
> >>files. Is there a way to use them locally or should I use "*default
> >>release=cvs tag=." to get actual Makefiles?
> >I think you should use DragonFly-src-supfile:
> Thanks Sascha,
> contrary to the doc, that file doesn't exist, but I am using
> from /usr/share/examples/cvsup/ -- though it is not clear to me whether
> I need FreeBSD-standard-supfile since I use DragonFly-supfile?
> // George
You only need Dragonfly-supfile (which grabs the dragonfly source) and
FreeBSD-ports-supfile (which grabs freebsd's ports system, which is kind
of a hack on dragonfly for the time being, while the low-level hooks
needed for dragonfly's package management system are being
implemented). They grab two completely different things into different
directories under /usr, and thus can both have the same prefix.
As an example (and hopefully this doesn't confuse things further), if
you were using FreeBSD you would use FreeBSD-standard-supfile to grab
the source, and FreeBSD-ports-supfile to grab ports. Since you're NOT
using FreeBSD, rather DragonFlyBSD, you want to grab the DragonFly
source, which Dragonfly-supfile does for you.
Hopefully that clears things up.