tags 296596 +experimental thanks On Wed, Feb 23, 2005 at 03:15:25PM +0100, martin f krafft wrote: > Package: debpool > Version: 0.1.11 > Severity: wishlist > > I am looking for a way to replace my brittle Makefiles with an > archive system, which I can use to pre-publish my Debian packages, > my NMUs, and any sponsored packages I make. The logical approach > here seems to be to use sections: stage, nmu, and sponsor. Thus, > I would like to be able to have the following sources.list line give > access to the first and third: > > http://server/path/to unstable stage sponsor > > The problem here is that this would require me to change > debian/control's Section field to target the right section. I would > prefer not to do this, since I know I will forget to change it back > before uploading the package to ftp-master. > > I see three solutions: > > - make debpool handle an override-style file, which maps source > package name to section on the archive > > - add a field to the source package debian/control stanza, such > as: > Debpool-Section: stage > and fall back to the regular main/contrib/non-free handling if > the field is not present. Not sure if this is okay by the > policy. > > - process incoming and check for $PACKAGE.debpool-meta, which can > define section (and distribution, while we're at it... unstable > makes little sense for private archives). > > Do you see this as a viable addition to debpool? > > In addition, it would be awesome if I could select single packages > > http://server/path/to unstable stage/gjay sponsor/zsync > > which would only pull in the packages for the corresponding source > packages. The solution here is to create indices for each file and > to drop them into separate directories sibling to each section's > binary-$ARCH and source directories. > > Please tell me what you think about that?
Hmmmm. I'll have to consider it some; while an overrides file is the
classic way of doing things, it also has some drawbacks (not to say it
doesn't work for the main archive, but that doesn't mean it's the best way
of handling a small archive, either).
I doubt I'd use a debian/control field; it would probably confuse too many
people and make them needlessly twitchy. A meta-file that can be included
with an upload is an interesting possibility, and could potentially handle
other things as well; I will need to think more about it, though.
I am somewhat more hesitant about the second issue, though it would be
possible to do with the package meta-files. I suspect the best answer might
be to get the hook system built, which would allow custom scripts to do
this sort of thing on the fly, for each site.
--
Joel Aelwyn <[EMAIL PROTECTED]> ,''`.
: :' :
`. `'
`-
signature.asc
Description: Digital signature
