RFS: libengsas packages
Lisandro Damián Nicanor Pérez Meyer
lisandro at debian.org
Mon Apr 1 17:01:34 UTC 2013
On Mon 01 Apr 2013 13:27:52 Joachim Langenbach escribió:
[snip]
> > - How stable the API is?
>
> The API is not that stable right now, but we are backporting everything
> possible to the 0 API version, which does not affect the API. So e. g. the
> current version of Meganizer is using the 0 API.
>
> > - According to [0] you don't actually maintain any other package in
> > Debian. Packaging libs it's not an easy task, and it's usually not
> > recommendable for packaging begginners. Please note that I'm not
> > implying that you are one, but [2] suggest so :-)
>
> Your absolutly right. I'm a beginner in packaging. But to package
> Meganizer, it is needed to package libengsas first ;-) Actually, I have
> done my first packaging steps with Meganizer (which, in an early version,
> was the source of libengsas).
Non-stable API and a new maintainer are stuff that do not go along very well
:-/
While it's normally correct to ship the lib as a separate package, in this
case and as long as there is only one app using it, let me suggest you to ship
it with the app as a bundled lib, without the headers.
Once you get more used to packaging and the API becomes stable you could
consider packaging them separately.
Kinds regards, Lisandro.
--
"With great power comes great responsibility."
Peter Parker's uncle.
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20130401/a1d497bf/attachment.pgp>
More information about the pkg-kde-talk
mailing list