Hi, the dependencies could (and should) certainly be maintained by the Debian Haskell Group, i.e. in https://salsa.debian.org/haskell-team/DHG_packages The mattermost binary itself, as it does not provide libghc-* package, not necessarily, and it might be best if you maintain as the sole maintainer. Cheers, Joachim Am Sonntag, den 28.01.2018, 20:19 +0800 schrieb YunQiang Su: > Ohh, matterhorn needs some new packages and some packages to be updated. > This is my work. > > Please have a review. > http://mips64el.sparklingly.org/debian-ghc/ > > On Tue, Jan 23, 2018 at 11:24 PM, YunQiang Su <syq@debian.org> wrote: > > Hi, folks, > > > > Now I need to access mattermost from a small/low-performance dev board. > > With some search I found the matterhorn[1] > > > > matterhorn uses ghc, and depends on mattermost-api and mattermost-api-qc. > > matterhorn is a quite special software: it need to meet the api changes for > > mattermost server, so it has several versions in parallel. > > > > So here I am ask for some suggestion to package it. > > > > My plan is to: > > 1. put all of these code in a multi-orig struct. > > 2. build all of these version and install them into different dest. > > 3. maybe figure out a script to call these different version binary. > > 4. I don't intend to ship libghc-mattermost-api* packages. > > > > [1]. https://github.com/matterhorn-chat/matterhorn > > -- Joachim “nomeata” Breitner Debian Developer nomeata@debian.org • https://people.debian.org/~nomeata XMPP: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F https://www.joachim-breitner.de/
Attachment:
signature.asc
Description: This is a digitally signed message part