On Sat, 13 Jun 2009 23:41:18 +0200 Sam Geeraerts <[email protected]> wrote:
> Karl Goetz schreef: > > On Fri, 12 Jun 2009 20:38:43 +0200 > > Sam Geeraerts <[email protected]> wrote: > > > >> Karl Goetz schreef: > > (For the lists benefit:) > > For single source:binary packages its really easy. A line like this > > should remove the package. > > > > DONT_CHROOT=1 ensure_updated helix-player helix-player $RELEASE$i > > "./remove-package helix-player" '' > > > I've looked at Builder some more: './remove-package FOO' comes down > to 'reprepro remove FOO', which deletes the FOO source and binary > packages. E.g.: ./remove-package firefox-3.0 means that you can't > 'apt-get install firefox-3.0' or 'apt-get source firefox-3.0', but > you still can 'apt-get install firefox-3.0-dom-inspector' (which is a > binary from the firefox-3.0 source package). > I could believe it. I wont bother trying to fix it in our current builder implementation, unless its causing freedom issues we've not noticed. kk > Disclaimer: this is an educated guess, not tested in practice. > > -- Karl Goetz, (Kamping_Kaiser / VK5FOSS) Debian contributor / gNewSense Maintainer http://www.kgoetz.id.au No, I won't join your social networking group
signature.asc
Description: PGP signature
_______________________________________________ gNewSense-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
