Re: design of an apt-src program
>>"Joey" == Joey Hess <email@example.com> writes:
Joey> 1. Simple command to install a source tree.
Joey> 2. Simple command to remove a source tree.
Joey> 3. Customizable source tree locations. Put it wherever you want it.
Joey> 4. A way to query for the location of a source tree, so
Joey> software that needs
Joey> to include stuff from it to build, or build parts of it, can work.
Joey> 5. An upgrade command that updates the source trees, ideally
Joey> first checking for local modifcations to each and aborting
Joey> if so (or generating forward patches).
Joey> 6. Use by regular users, but also usable by root to install in canoical
Joey> locations (/usr/src).
Joey> 7. Sources installable from CD, etc.
Joey> 8. An interface familiar to anyone who knows apt.
Joey> 9. A way to list available source trees and their locations.
Joey> 10. Handle source dependencies amoung source trees; build-dep
Joey> satisfaction on tree install and upgrade.
Joey> 11. Support auto-rebuilds on upgrade?
Could one support a local CVS repository? So an initial
installation of a source tree call a cvs import in a post-inst
script; and an update of the source import it into the vendor branch?
I would love to be able to have triggers that build parts of
the tree when dependent parts are updated. Being able to specify the
commands to be called would be nice -- One could use
cvs-buildpackage, pbuider, cvs-pbuildepackage, or whatever, in order
to have the tree rebuilt.
Joey> Let the command be "apt-src". It would support these actions:
Joey> apt-src install foo
Joey> apt-get source foo into dir under current directory. Possibly
Joey> rename directory to remove version number.
Possible call a script (cvs import, cvs-inject) when done.
Joey> If foo is already installed here, upgrade it instead.
Umm. I would like to have an explicit command to do this, and
have a a post upgrade run of cvs-upgrade kinda things.
Joey> Check that build-deps are satisfied (via apt-get build-dep foo).
Joey> Check that source-deps are satisfied as well; if not install them
That would be nice.
Joey> Support a --build to make it compile the tree after download.
With options to call alternate build commands, which
themselves could be CVS aware.
Joey> apt-src remove foo
Joey> remove source tree for foo, checking source-deps of source trees
Joey> installed by this user first.
Hmm. I don't know how to incorporate this into a local CVS paradigm
Joey> Since this can be used by regular users, this needs to be stored in user
Joey> home dirs for regular users ~/.apt-src/status ? For root, it can be in
This should definitely be a configuration option. All my
coworkers and I can share a repository/build tree, with proper group
As part of an ongoing effort to keep you, the Fortune reader, abreast
of the valuable information the daily crosses the USENET, Fortune
presents: News articles that answer *your* questions, #1: Newsgroups:
comp.sources.d Subject: how do I run C code received from sources
Keywords: C sources Distribution: na I do not know how to run the C
programs that are posted in the sources newsgroup. I save the files,
edit them to remove the headers, and change the mode so that they are
executable, but I cannot get them to run. (I have never written a C
program before.) Must they be compiled? With what compiler? How do
I do this? If I compile them, is an object code file generated or
must I generate it explicitly with the > character? Is there
something else that must be done?
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org