On 27 May 2012 00:46, Ron <[email protected]> wrote: > These kind of go against the original spirit of what was intended for > the hooks, but for people who want these things, that's a tradeoff they > need to choose for themselves. The thing that keeps them within it > though, is that they are only required to build a specific *form* of > package. ie. if you don't have them installed, and you export the > same repo, you will still get a valid package of the same source, that > builds exactly the same binary packages. > > The *only* difference is, you'll get a format 1.0 style monolithic > diff without the quilt hook instead of the split up patch series. > Or you'll get a tarball re-exported from the upstream branch, instead > the pristine-tar hacked one - so it will have the same source, just > not the same checksum. (and if you already have the old orig tarball > present in the export dir, or fetch it with wget from a hook, then it > will re-use that and give you identical results to what p-t would too).
Errr... No. If somebody omits the quilt-patches hook, using the work flow I stole from the imagemagick package (using two branches, one for upstream patches, as discussed on debian-devel), and builds the package, none of the Debian patches will get exported to debian/patches, and as a result, the package will be built from pristine sources + debian directory. Actually, this is somewhat troubling now I think about it :-( - the debian/changelog won't correspond with the package being built. Maybe this is a topic for another bug report... > And the TMPDIR part, you could actually do from an admin-config-hook ... Oh, ok, didn't realize this. Will have to try it. > Then your top level interface can either just be gitpkg itself, or a > (set of) very light wrapper(s) that just do(es) something like: > > MY_BUILDD="PPA" > gitpkg $@ I was thinking of something like this. Think I might have to write some code, and see how it turns out. -- Brian May <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
