Hash: SHA1

Hello Jonas and the list!

On 10-06-05 03:51 AM, Jonas Smedegaard wrote:
> Lower that package relation to suggests, and document the benefit of
> installing that suggestion (without explaining the reason it is only
> suggested, that is development-grade info IMO) in both long description
> (i.e. in debian/control) and in a debian/README.Debian file (which CDBS
> then automagically includes in the binary packages).


> And try post to bug#544347 again - cc'ing menucci who seem to have
> somewhat taken over maintainership and perhaps haven't noticed that old
> bug.


>> Maybe it would be nice to also create the scenic-doc package, to
>> separate the doc from the Python code. (though both are architecture:
>> all)
> Certainly - if there is documentation of a reasonable amount then it
> should be in a separate binary package.

Done. :)

>> For now, the docbook documentation (viewable with yelp) are in an
>> unusual location. (/usr/share/scenic/docbook) It should probably go to
>> /usr/share/gnome/help/scenic/C/scenic.xml like all gnome docs. Our
>> docbook doc is made of several XML files and images, though, and we
>> have two manuals...
> I am not very familiar with yelp, but seems to me that if the project is
> not otherwise tied specifically to Gnome and if yelp supports reading
> from non-gnome directories, then you shouldn't jump through hoops to
> install the documentation Gnome-style, but instead jump through hoops to
> get yelp to recognize it.  More importantly you should register with
> doc-base (which might be all that is needed for yelp integration too?).

Each .doc-base file must be for the doc of only one binary package, but
there are two manuals in Scenic! (not that I agree with that...)

Meanwhile, my current .doc-base file is installed properly, but it is
not shown by dhelp.

> Well, my excuses currently is a) I have too little time (developing and
> setting up sms service in the field for an experimental theater group),
> and b) I cannot do clean-room package compilations due to a major part
> of my laptop being readonly (heating problem caused a power outage
> during a partition resize - all data seems fine but I cannot know for
> sure, and every time I try fsck'ing that heating problem strikes again).
> In other words: my trouble is unrelated to the code quality :-)

Don't worry. Me and the Scenic team has tested it a lot since the last
few months, and on Debian unstable as well. There is no Trojan horse in
the app! - only an easter egg. I wish you to overcome these technical
problems quickly.

Here is a list of the current lintian warnings for the four packages:

- ---------------------------------- scenic-doc
aa...@plouf:~/src/debian/build-area$ lintian -Iv --pedantic
N: Setting up lab in /tmp/k1R8QxDI2F ...
N: Processing 1 packages...
N: ----
N: Processing binary package scenic-doc (version 0.5.11-1) ...
P: scenic-doc: no-upstream-changelog
N: Removing /tmp/k1R8QxDI2F ...

- -----------------------------------  scenic
aa...@plouf:~/src/debian/build-area$ lintian -Iv --pedantic
N: Setting up lab in /tmp/EfBpUFMNoH ...
N: Processing 1 packages...
N: ----
N: Processing binary package scenic (version 0.5.11-1) ...
P: scenic: no-upstream-changelog
I: scenic: hyphen-used-as-minus-sign usr/share/man/man1/scenic.1.gz:52
I: scenic: unused-override scenic source: hyphen-used-as-minus-sign
N: Removing /tmp/EfBpUFMNoH ...

- ------------------------------------ midistream
aa...@plouf:~/src/debian/build-area$ lintian -Iv --pedantic
N: Setting up lab in /tmp/DSFZ66tQGW ...
N: Processing 1 packages...
N: ----
N: Processing binary package midistream (version 0.5.11-1) ...
P: midistream: no-upstream-changelog
I: midistream: hyphen-used-as-minus-sign
I: midistream: hyphen-used-as-minus-sign
I: midistream: hyphen-used-as-minus-sign
I: midistream: unused-override midistream source: hyphen-used-as-minus-sign
N: Removing /tmp/DSFZ66tQGW ...

>>> sugar-0.88
>>> That one also demonstrates quite well IMO how a large amount of
>>> package dependencies are easier to track indirectly declared in
>>> debian/rules, as they they can be grouped and comments added as needed.
>> This is very interesting and am I looking forward to learn more about
>> this. I will make some tests soon.
> I am happy to hear that you are interested in those features.  They are
> some of my newest additions to CDBS :-)

Should I get into that for the first package of Scenic? How new is it? I
am looking forward to use these advanced goodies, but I am still a
beginner at packaging... :)

Best regards,

Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


pkg-multimedia-maintainers mailing list

Reply via email to