Advice needed: uploading hledger to wheezy-backports?
Hi,
(Please Cc' me any reply I should read, as I don't read the list.)
I need to make hledger available for some Wheezy users.
I was able to backport the current sid version of:
- haskell-hledger
- haskell-hledger-lib
- haskell-data-pprint
- haskell-tabular
- haskell-cmdargs
- haskell-pretty-show
... and the resulting hledger binary package seems to work fine.
The only changes I had to do on each package was the reverting of the
substvars for descriptions, and downgrading the versioned build-dep on
haskell-devscripts. So far, so good.
Out of these 6 packages, only the two last packages are available on
Wheezy, and thus require special care to avoid breaking reverse
library dependencies.
The only reverse library dependency I could find for these packages in
Wheezy is libghc-diagrams-cairo-dev depending on
libghc-cmdargs-dev-0.9.5-7e669 (ditto for the -proc package).
So, in the *current* state of things, once all this has migrated to
testing, it seems to me that I could easily:
- upload the 6 aforementioned backported packages to
wheezy-backports
- "binNMU" haskell-diagrams-cairo in wheezy-backports, once
haskell-cmdargs is in there
On the short term, this seems quite manageable.
However, the list of packages from the build-dependency tree that need
backporting grew a bit with hledger 0.22.1, and I'm afraid it could
easily come to a point when I would have to backport or "binNMU"
(rebuild against the Haskell stack in wheezy-backport) dozens of
Haskell libraries in wheezy-backports, just to avoid creating
co-installability issues for Haskell libraries that are shipped
in Wheezy.
All in all, I must say this sounds a bit scary, and I am very tempted
to keep this backport private, and avoid taking a responsibility whose
scope can grow in hard (for me) to predict ways.
Thoughts, suggestions? Anyone interested in maintaining this set of
packages in the official wheezy-backports?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
Reply to: