libecc
- Subject: libecc
- From: locutusofborg@debian.org (Gianfranco Costamagna)
- Date: Mon, 4 Sep 2017 15:29:41 +0000 (UTC)
- Message-id: <[🔎] 1260930292.4303143.1504538981792@mail.yahoo.com>
- In-reply-to: <20170830202252.7d848b5a@localhost>
- References: <CAFG-WzDr-tPvzBMrNDqueFMwR=+1pYFWvs5HuiLzT06NbJ5j9A@mail.gmail.com> <20170827140414.5c2fe0c7@localhost> <CAFG-WzDwAu1dv_BAzj+BV6Cu_D=pZGLU5zQNZ-qcy+pN00qxdg@mail.gmail.com> <CAFG-WzDGJ8ykz7nfqo2tSkpVQjiKc-cm4bLHo9AUNED0bx4ciA@mail.gmail.com> <20170830202252.7d848b5a@localhost>
Hello,
>DDs: What do you think regarding packaging that library? Would you
> sponsor libecc (once packaging has reached sufficient quality)?
I'll trust your opinion, after...
>In the meantime, you should fix the owner of the ITP bug as I remarked
>in my previous mail. And I'm still curious: Is there a specific need
>for that library? Is there something you want to package that uses it?
... reading that answer :)
also, debian-devel and debian-mentors mail lists are a good place to ask such
things, I don't want to do the work and get it removed by ftpmasters or rejected
due to poor quality/maintainability.
I can't promise to sponsor it, but if the work is correctly done, I don't see why
we shouldn't have an ecc library here :)
G.
Reply to: