On Thu, Jan 31, 2008 at 12:31:19PM -0500, Lord of, St. Luke Valor wrote: > Any software engineer will willfully tell you that software development > involves planned chaos. It is obvious to this computer scientist that you > have enough experience with networking and system management to know that > 'keep it simple' is the order of the day. The easy way is scientific > enough. I suggest the easy solution to be the investigation, acquisition > and installation of software from the subversion project. It is a > replacement for CVS, which supersedes RCS and complements the apt suite. > > Think of it as one more tool in the toolkit.
Yes, we already make extensive use of Subversion in our environment. We store package sources in Subversion, build them into .debs, and insert them into a local APT repository. Our goal is to have our infrastructure follow the core operating system's lead as much as possible, and this goal seems to dovetail nicely with using locally maintained .debs and a local APT repo. Subversion, on the other hand, is not a packaging system and is not integrated with the core OS. We could very well distribute a set of scripts (using Subversion) that would apply the necessary configuration changes to our dozens of machines running Debian, but then we're back to the question of how to invoke these scripts, enforce dpkg dependencies, handle failure, interact with the user, and all of the other problems that dpkg and APT have already solved quite nicely. So I'm not sure how your suggestion to expand our use of Subversion will fix or work around the behavior in apt-ftparchive I'm asking about in this bug. john -- John Morrissey _o /\ ---- __o [EMAIL PROTECTED] _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
