Ticket #252 (closed defect: wontfix)

Opened 8 years ago

Last modified 4 years ago

Persistent database for new_packages hook?

Reported by: eternaleye Owned by: ciaranm
Priority: IfSomeoneSendsAPatch Milestone:
Component: misc Version: 0.22.2
Keywords: Cc:
Blocked By: Blocking:
Distribution: Gentoo

Description

On every sync, the new_packages hook rebuilds its database and diffs it against the updated tree. Would it not be simpler to save the updated database afterwards, and simply diff against that on the next sync? This would also note as new packages those added during external syncs, like layman or portage (for anyone who uses them), and those in local repositories which update _between_ syncs, like a user's own repository. This would also speed up syncs, especially on computers with slow disk access times. (on my laptop it takes a full 5 minutes to generate the database). Perhaps this could be implemented as an option?

Change History

comment:1 Changed 8 years ago by ciaranm

Well... It's a demo hook, so it's designed to be a good starting point rather than a complete solution...

comment:2 Changed 4 years ago by ciaranm

  • Status changed from new to closed
  • Distribution set to Gentoo
  • Resolution set to wontfix

We killed this hook.

Note: See TracTickets for help on using tickets.