reopen 469651 thanks On Thu, Mar 06, 2008 at 03:04:57PM +0100, Bernhard R. Link wrote: > * Marc Haber <[EMAIL PROTECTED]> [080306 12:34]: > > However, in my repository, the .changes files are copied into the pool > > as well, and so is an .interdiff.gz file which holds a diff of the > > package in question to the previous version in Debian, therefore > > making it easy to see which changes were done during the backport > > process. > > > > To allow this, it would be great if reprepro would allow a hook script > > to be defined in conf/distributions which would be called after a > > changes to the repository/pool were done. Via environment variables, > > it could be fed with the operation being invoked, the name and version > > of the package being installed, the source directory and the target > > directory to enable it to do its own copies and/or moves independently > > from reprepro. > > I believe this is already possible with "Log", e.g. something like: > > Log: > --changes scriptnametocall > > If that misses anything you need, please reopen this bug or file a new > one.
That looks generally good. I'd like to have access to reprepro's command line somehow (to find out the path to the file that is being added, for example). Additionally, the docs are kind of terse. Sure, one can easily find out that the script is passed at least nine parameters, action, distribution, type of file, component, arch, package name, version, "--" and a list of files being processed, but if that were in the man page, I wouldn't have filed this bug in the first place since I'd have found the directive myself. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
