Bug#517650: lintian: changes made to collection scripts are not reflected unless a package changes
Raphael Geissert <atomo64+debian@gmail.com> writes:
> Russ Allbery wrote:
>> The one tweak that I'd make is to list all of the files that a given
>> collection script creates in the Output field still, but use that only
>> to determine which files to remove when the version is out of date.
>
> I didn't consider that because most (if not all) of the collection
> scripts either open files for writting (and not appending) or remove
> them before writting/appending anything to them.
Oh, I see. Yes, you're right, we don't need that.
> I'm not quiet sure what you are concerned about, could you please
> elaborate?
Never mind, I just misunderstood something in your original message. Your
implementation plan sounds fine to me.
> Good :) but in order to properly do it I would like to drop the Order
> entry from the collection/*.desc files and implement a simple
> dependencies resolver. That would allow a chain-reaction-like execution
> of collection scripts.
Yup.
> I've also though about running the check scripts as soon as their
> Needs-Info collection scripts are done, while the other collection
> scripts keep running; but I think I'm dreaming too much. I mean, it is
> not impossible, but would need quite some changes to be made on the
> frontend. Talking of which, I think it needs a cleanup and some of its
> code moved to modules; it is not easy to read and hack.
Yes. I was concentrating on cleaning up lib first and getting everything
into a proper module structure with documentation first, but that was just
my internal sequencing, and I'm happy to see people tackle this in a
different order. I'd like to see most of lintian moved into modules with
a cleaner conceptual organization.
It would probably be worth running the object structure by the list first
before tackling major restructurings, of course (for anyone who wants to
work on this).
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: