Hi, Am Mittwoch, den 06.03.2013, 19:58 +0900 schrieb Kiwamu Okabe: > I started jhc Debian package. > And I created many patches for jhc. > But...jhc's upstream author, John, doesn't reply mailing list... > It's difficult that maintain many patches without any repositories. > > Then, I have decided to fork jhc, named Ajhc. > # pain full... > > http://ajhc.github.com/ > > I have written LED blinking demo for Cortex-M3 with Ajhc. > Ajhc is very useful for small domain or low layer domain. > > https://github.com/ajhc/demo-cortex-m3 > http://www.youtube.com/watch?v=3R9sogReVHg > > Now I have some question. > > Q1. Can I maintain both jhc and Ajhc packages on Debian? > Or should I maintain only one of them? There should be only one package in Debian. Preferably, there should also only be one upstream version of jhc. It is unfortunate that John is not very responsive, but he is also not completely off the project (there is a mail in December). I suggest that you mention your ajhc fork on the jhc mailing list, and state that you’d prefer not to fork jhc if it can be avoided. You should also mention it on haskell-cafe, maybe this will start a discussion about the future of jhc. For Debian I’d prefer if the situation has settled before deciding which package should be in Debian. > Q2. Is it good that Ajhc support installation with cabal? No opinion here. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part