[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFC: packaging layout for Odin



On Fri, 9 Jan 2009 15:28:05 +0100 (CET), Andreas Tille wrote:

> On Fri, 9 Jan 2009, David Paleino wrote:
> 
> > libodindata1, libodindata-dev, libodindata1-dbg
> > libodinpara1, libodinpara-dev, libodinpara1-dbg
> > libodinqt1, libodinqt-dev, libodinqt1-dbg
> > libodinseq1, libodinseq-dev, libodinseq1-dbg
> > libtjutils1, libtjutils-dev, libtjutils1-dbg
> >
> > (only the libraries, they sum up to 15 packages -- and yes, the -dbg ones
> > are IMHO needed, we don't want our non-developer-users to recompile stuff
> > on their own, right?)
> 
> Well, what about
> 
>     [..]
> 
> IMHO these 2 (3) packages might do vor the moment if every single
> library is not really huge and does not really different things.

Yes, this is what I wrote at the end of my mail. But this is ok if they're for
private-use-only.

>     libodin-dbg (I'm not really convinced, perhaps you are doing some
>                  work which is of really rare use, but I would leave
>                  the decision to you)

That's common practice in library packaging -- if a bug shows up, gdb isn't
really useful if no debugging symbols are provided. And, it's just simpler
telling a user "do apt-get install libodin-dbg" then "do:

apt-get source odin
apt-get build-dep odin
DEBBUILDOPTS=nostrip debian/rules binary
dpkg -i ../...
"

Do you agree? ;)

(in my vision, *we* are the maintainer with coding/packaging skills, and should
do everything to make users' life the easiest possible).

> [..]
> 
> > Then there is /usr/share/doc/odin/:
> >
> > $ tree
> > .
> > `-- [..]
> >        `-- sequences
> >            |-- odinepi.cpp
> >            |-- [..]
> >            `-- tj_verve.cpp
> > $
> 
> Hmm, *.cpp sounds rather like 'examples' than 'sequences' ...
> 
> > It's a total of 1,6M, so we can decide to have an extra single "odin-doc"
> > package (I thought at odin-samples, odin-coils and odin-sequences, but those
> > are just examples, so IMHO not worth having their own separated packages)
> 
> Just move examples to the -dev package if they are not to large.

Agreed.

> [..]
> > Also, it is possible that they all are internal but libtjutils -- in this
> > case I'd do libodin1 and libtjutils1.
> 
> I would ask upstream about the role of the libraries.

Asked upstream, CCed the list.

Kindly,
David

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

Attachment: signature.asc
Description: PGP signature


Reply to: