Date: Wed, 01 Mar 2006 13:24:46 -0700 From: Scott Long <scottl@samsco.org> To: Garance A Drosehn <gad@freebsd.org> Cc: arch@freebsd.org, current@freebsd.org Subject: Re: HEADS UP: Importing csup into base Message-ID: <4406030E.6020209@samsco.org> In-Reply-To: <p06230908c02ba3dee4c9@[128.113.24.47]> References: <20060301170306.GZ55746@elvis.mu.org> <p06230908c02ba3dee4c9@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosehn wrote: > At 6:03 PM +0100 3/1/06, Maxime Henrion wrote: > >> >> So I think it is now time to import csup in FreeBSD base system >> so that our users finally have a way to update their sources >> with a bare install, and am requesting comments/opinions/problem >> reports on the matter as long as it doesn't degenerate into a >> bikeshed. > > > I wonder if we should handle this more like perl (or X11?), where > it remains a port, but a port which is always installed along > with the base-system install. My hope is that with the new > C-based implementation, 'csup' would be useful to other projects. > (any cvs-based open-source project, not just operating systems). > perl is the way it is to help ease the transition back 5+ years ago with FreeBSD 4. I'd kinda like to declare that transition a completed success. Adding more one-off special cases to sysinstall only makes it harder to maintain, harder to build releases, etc. > I would also be happy to see it as part of the freebsd base system, > so I only mention the above alternative because I'm wondering what > would be the best way to handle a project like this... Make it part of the base system. It's no different than having cvs in the base system. It also doesn't have any foreign dependencies, which was the main reason that cvsup was never assimilated. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4406030E.6020209>