On Nov 16, 2016, at 07:48 AM, Johannes Schauer wrote: >> 1) Allow for passing wildcards to --extra-package. Then I could do >> something like `sbuild ... --extra-package=/path/to/itp/*.deb` and >> have it pick up all the debs in that directory. >> >> 2) Provide a shortcut option for --extra-package. > >it seems that what you want is not to pass individual .deb files but a >repository of them. Why not just put all your .deb into a directory, call >"apt-ftparchive release" to create a Release file, start a http server inside >that directory with "python3 -m http.server 8000 --bind 127.0.0.1" and then >use: > >sbuild --extra-repository="deb [trusted=yes] http://127.0.0.1:8000 ./" > >This sounds like much but since you explained that you are doing this very >often you could: > > - put the --extra-repository into your ~/.sbuildrc using $extra_repositories > - configure a webserver to always serve from your chose directory locally (if > you don't like the idea to have yet another service running in the > background, you could even use an inetd based http server) > - regenerate your archive using a simple inotify watcher on your chosen > directory > >Then, whenever you have a new .deb, you'd just throw it into that directory >and when you call "sbuild" (without arguments) it would pick up everything >you need. > >Would that not be superior to complicating the sbuild command line?
It's certainly possible, and I used to do some very similar things, but when my old approach broke, I started to investigate what sbuild could do natively. --extra-package is a nice feature, but then my first inclination was to try using a wildcard in the path instead of a hardcoded single file. When that failed, I thought I'd request this simple enhancement. It's not really a CLI API change per se since you don't really need to add a new command line switch, just do the globbing in sbuild. I totally understand if you don't want to do it though. Thanks for listening!
pgp329HljjINO.pgp
Description: OpenPGP digital signature