On Sun, 20 Apr 2008 16:27:58 +0900 Junichi Uekawa wrote: > Hi,
Hi! :) > > > Again assuming that the above is correct, I don't think that this logic > > is appropriate for aptcleanup. [...] > > I think the design of aptcleanup could be changed as follows. [...] > > 1.2.1) query the BTS about the bug and find out whether the bug > > is still present *and* still RC in the > > unpinned_candidate_version [...] > > Well, what do you think about my proposed redesign of aptcleanup? [...] > Your logic sounds reasonable, patch is welcome. It's going to be a > major rewrite since aptcleanup currently is a very simple script. I have to learn Ruby before I can implement my redesign. This is a non-negligible obstacle... Anyway, let's implement it step by step in a bottom-up strategy. I will need the help of a Ruby guru like you, though. First brick I will need is a means to query the BTS about one or more bugs in order to get their status in a given package/version (step 1.2.1 above). I've just filed a wishlist bug for this feature (see #476988): could you please implement it in apt-listbugs? I think that /usr/sbin/apt-listbugs is the right place where this feature should be added, but I would rather avoid making invasive modifications to /usr/sbin/apt-listbugs by myself, since I am still a Ruby illiterate. In the meanwhile, I'll try and learn a bit of Ruby, so that I will (hopefully) be able to modify /usr/share/apt-listbugs/aptcleanup by myself (or, at worst, with minimum assistance from you). -- http://frx.netsons.org/doc/index.html#nanodocs The nano-document series is here! ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgpatX48p1w9V.pgp
Description: PGP signature
