On Thu, Mar 13, 2014 at 4:12 PM, Bo Shi <[email protected]> wrote: > My old debian/rules file for wal-e 0.6.x for use in launchpad was > quite minimalist (below) and seemed to work well enough. The new beta > includes a Makefile that seems to be primarily targeted at very > specific environments (pypi, travis). Does anyone know of a flag or > method to instruct dh to ignore the upstream Makefile?
I have a functional set of packaging I use constantly. https://launchpad.net/~drfarina/+archive/wal-e/+packages I sometimes copy it out to a public PPA for a yet-un-mentioned inspection (because it's just a set of snapshots and for Heroku operations, with no particular concern to being useful to anyone else), but as it turns out I haven't changed the structure of that package (e.g. rules) in a while...years, probably, and it seems work perfectly, including with the project Makefile. I created it with 'stdeb'. Consider it recommended. But I havne't had to use stdeb more than once... The thing that makes my WAL-E package weak compared to a real debian package are my lousy changelog hygiene (I don't care, there are no arm's lengths consumers), and probably other un-itemized weaknesses because I am no expert at that. -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
