Re: RFC: packaging layout for Odin
On Fri, Jan 09, 2009 at 05:12:34PM +0100, David Paleino wrote:
> On Fri, 9 Jan 2009 16:57:38 +0100, Michael Hanke wrote:
> > Sure. The other half of the topic is: Someone has to check each upstream
> > release whether upstream was correct in bumping or not bumping SO
> > version, negotiating with upstream to correct (if necessary), changing
> > package names accordingly, forcing the package through NEW, ...
> >
> > Significant increase in workload for a number of people due to 'what if
> > a random...'
>
> What's wrong in:
>
> > > Probably upstream should be educated on a better usage of this, [..]
>
> ? :)
>
> Maybe I'm just too confident in upstream's education?
That is pretty much independent of upstream -- educated or not, you
still need to check, SO name still causes the package name to change,
package name change still causes package to go through new, and somebody
has to process it.
If we are honest, this kind of package will never have a popcon stat
with three digits (simply because it is very very very special
interest). Having it (IMHO) overengineered will cause an unreasonable
workload on some project members -- with close to no benefit (again
IMHO).
> > > > Moreover, the cpp are the actual templates that are used to develop own
> > > > sequences -- IMHO this is more than plain documentation. Just take a
> > > > look at the actual user interface.
> > >
> > > Yes, I already started the GUI before sending my first mail.
> > >
> > > And, IMHO, they're still documentative: you're "allowed" to write a sequence
> > > from scratch, aren't you? (Ok, probably you wouldn't do that, but still can)
> > >
> > > Those are, as Andreas pointed, "example sequences" -- they are best fit in
> > > /usr/share/doc/<something>/examples/ IMHO.
> >
> > As I said -- that is my oppinion, but since you package -- you decide.
>
> I don't really like this kind of replies, I'm one who always tries to find a
> common ground.
>
> What if we add the -doc package to odin's Recommends:, and provide symlinks
> in /usr/share/odin/ ?
>
> Also, I'm thinking of adding a README.Debian with the information from
> http://od1n.sourceforge.net/sequences.html , and a debian/NEWS (which should
> pop up upon installation) informing users to read in /usr/share/doc/.../ how to
> use the templates.
>
> The idea of debian/NEWS is not bad at all IMHO: we could warn users "Hey, if you
> want templates, install odin-doc"
I still think this is a matter of taste -- I still see no part of odin
that would not be installed on any system were it would be used. These
are biig machines and we are talking about 2 MB (at most). Splitting the
package only increases the likelyhood of somebody being frustrated
because things do not 'just-work'. Not wasting archive space would be
something worth considering, but again: 2 MB.
Michael
--
GPG key: 1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050
Reply to: