[needs-packaging] gelemental

Assigned to team MOTU.

http://revu.tauware.de/details.py?upid=305

Checking it out.

 - You could point out that you re-packed the tarball. It seems there's only a .tar.bz2 on the web page.
 - Use your shiny new @ubuntu.com mail address. :-)
 - I'd rather name the doc package ...-doc
 - what do you need the .xpm for?
 - if you don't plan to split out the libgelemental-dev and libgelemental0 package, it's probably no use to ship the headers and the .pc file.
 - please don't install the .la file.

Many thanks for your comments Daniel, as usual you are a big help :-).

>You could point out that you re-packed the tarball. It seems there's only a .tar.bz2 on the web page.

Added note to debian/copyright

>Use your shiny new @ubuntu.com mail address.

Done.

>I'd rather name the doc package ...-doc

Done

>what do you need the .xpm for?

Sorry about that, I did change it already but did not add the revu link to it.

>if you don't plan to split out the libgelemental-dev and libgelemental0 package, it's probably no use to ship the headers and the .pc file and please don't install the .la file.

3 packages are now created from the source package:

gelemental (which provides libgelemental1):

binary, shared library, icons/.desktop and i8n

libgelemental-dev:

development libraries (.a, .la and .pc) and headers

gelemental-doc:

all api documentation

Please let me know if you think I should change anything.
Here is the new link:

http://revu.tauware.de/details.py?upid=308

I'm the maintainer of gElemental. Thank you for your work on packaging it! I'm about to release a new major version which will be API-incompatible (the last break for a while, hopefully) and change several names (libgelemental to libelemental, pygElemental to pyElemental, etc.). It should be done in the next week or so--I'll comment here again at that time.

Thanks for letting us know. We plan to release this package for hardy, so we have plenty of time to incorporate your changes.
Just a little remark about your .desktop file:

Can you remove the encode field (is deprecated)?
Can you change the comment field in line with the Gnome HIG (mainly rewording it starting with an imperative verb, like, view the periodic table)?

I know the last one is a pain as it involves new translations ....

If you have any comment on the packages I'll be glad to hear them.

I have just released 1.2.0. The .desktop file was changed according to your notes. Other changes affecting packaging include:

* gElemental is now licensed under GPLv3+.
* The compose library functions have been relicensed and merged into my libmisc bundle; they should no longer need a separate mention in debian/copyright.
* libgelemental has been renamed to libelemental.
* A full man page is now included.

There is also a Python binding, pyElemental, if you want to bother with it.

>I have just released 1.2.0

New ubuntu version is up for review here:

http://revu.tauware.de/details.py?upid=318

>There is also a Python binding, pyElemental

Yes, I have seen the Python bindings but since it is a different tarball it needs another package.
I could also merge the two tarballs and have them all in a single source package but I'm reluctant to do that as I don't like as a principle to mess with upstream stuff. For instance in this case it would make the package less maintainable for us (e.g. a change in the bindings would mean a rebuild of source and all binaries).

Added libglibmm-2.4-dev and libpango1.0-dev dependancies to libelemental-dev (required by pkg-config):

http://revu.tauware.de/details.py?upid=322

>There is also a Python binding, pyElemental

https://bugs.edge.launchpad.net/ubuntu/+bug/147810

 - I'd add the note about the re-packed tarball to debian/changelog - that's the place that most other maintainers would look for that piece of information; I guess.
 - Why does gelemental provide libelemental0? This is not really discoverable.

 - I'd rename gelemental-doc to libelemental-doc as it seems to be API docs, not docs on gelemental itself.

>I'd rename gelemental-doc to libelemental-doc

Done.

>Why does gelemental provide libelemental0

The Description fields have been amended.

>I'd add the note about the re-packed tarball to debian/changelog

Done.

http://revu.tauware.de/details.py?upid=324

Thanks!

Daniel et al.,

I have prepared two different versions:

1) 3 binary packages, application and shared library together, requires lintian override

REVU: http://revu.tauware.de/details.py?upid=336

2) 4 binary packages, application and shared library two separate binary pakages

REVU: http://revu.tauware.de/details.py?upid=337

Let me know which one you think makes more sense and I will keep working on that.

Thanks.

Also note that, in accordance to current standards, I removed the .la file from the -dev package in my working tree (not yet uploaded to REVU).

I decided to go for the 4 binary packages:

http://revu.tauware.de/details.py?upid=359

Thanks for your continued work! Minor note: in the configure target in debian/rules, you have "--enable-api_docs" instead of "--enable-api-docs".

Thanks for your comment Kevin, please let them coming!
Re. --enable-api-docs vs. --enable-api_docs, it doesn't matter as - and _ are parsed the same way.
I just used what configure seems to indicate as the best choice, see line 22048 of configure.

https://launchpad.net/ubuntu/hardy/+source/gelemental/1.2.0-0ubuntu1