Re: design of an apt-src program
On Sun, 16 Jun 2002, Joey Hess wrote:
>
> Requirements:
>
> 1. Simple command to install a source tree.
> 2. Simple command to remove a source tree.
> 3. Customizable source tree locations. Put it wherever you want it.
> 4. A way to query for the location of a source tree, so software that needs
> to include stuff from it to build, or build parts of it, can work.
> 5. An upgrade command that updates the source trees, ideally first checking
> for local modifcations to each and aborting if so (or generating forward
> patches).
> 6. Use by regular users, but also usable by root to install in canoical
> locations (/usr/src).
> 7. Sources installable from CD, etc.
> 8. An interface familiar to anyone who knows apt.
> 9. A way to list available source trees and their locations.
> 10. Handle source dependencies amoung source trees; build-dep satisfaction on
> tree install and upgrade.
> 11. Support auto-rebuilds on upgrade?
>
12: allow certain default global settings. I.e. on a server you may
never want to link with the X libraries, you may always want to compile
with mmx instructions, etc. never strip binaries etc. etc.
[...]
>
> Some interesting packages to look at in research this include:
>
Gentoo seems to be the flavor of the month. Why not look into how they do
things? My understanding is it is like the BSD ports but I've never
actually tried it.
--
Jaldhar H. Vyas <jaldhar@debian.org>
It's a girl! See the pictures - http://www.braincells.com/shailaja/
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: