[Top][All Lists]

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

[Gnumed-devel] Re: Packaging (Was: Naming convention)

From: Andreas Tille
Subject: [Gnumed-devel] Re: Packaging (Was: Naming convention)
Date: Tue, 8 Sep 2009 11:20:21 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Sep 08, 2009 at 01:02:30AM -0700, Jim Busser wrote:
>       bitmaps
>               into --> /usr/share/gnumed/
>               ... but why not into /usr/share/gnumed/Gnumed/

I think this is for historical reasons.  I guess at some point I did a
"cd /usr/share/gnumed/" in the /usr/bin/gnumed script and bitmaps were
seeked relative to this PATH.  There was no need to change this because
it kept on working that way.  (Sorry, no better reason than "because I
alwasy did so" and it works.)

>               would it be better named /client ?

I had no reason to diverge from upstream names.
>       connectors
>       gm-from-cvs.bat
>       gm-from-cvs.conf
>       gm-from-cvs.log
>       gnumed
>       gnumed-client.desktop
>       GnuPublicLicense.txt
>       locale
>               --> do the above have destinations ??
>               (apart from gm-from-cvs.conf
>                 which supplies gnumed.conf)
>               (and gnumed which I gather supplies
>                       usr/bin/gnumed

Well, executable files (*.sh) should be somewhere in the PATH (perhaps I
had reserved /usr/share/gnumed/bin for putting things there - I do not
remember, sorry).  The locale files will be moved to /usr/share/locale
where all translation go in Debian.  The *.desktop file goes to
/usr/share/applications where it belongs to and there is no need to keep
the license file separately because it is required to be in
/usr/share/doc/<packagenname>/copyright (and you should not provide
extra license files.

> - doc from tarball:
>       gm_ctl_client.1
>               ??
>       gnumed.1
>               ??

-> /usr/share/man/man1

>       gnumed.conf.example # it's just gm-from-cvs.conf
>               ??

-> There is no need to provide such an example in the package.

>               --> into /home/jbusser/.gnumed/scripts
>               (as
>               but there also resides
>                       hook_script.pyc
>               which originated from ??

Ignored for packaging.

>       user-manual
>               --> into /usr/share/doc/gnumed/


>       additionally in Debian appear the following, but they
>       appear limited to Tille-Debianized-docs
>               /usr/share/doc/gnumed-client/
>                       changelog.Debian.gz
>                       copyright
>                       README.Debian

That's the usual required Debian doc.

>   debian etc/
>         gnumed/
>               gnumed-client.conf      # from gm-from-cvs.conf?
>               gnumed-client_public.conf       # Andreas' creation?

The latter is outdated and should not be shipped any more.

>                       (both derived from gm-from-cvs.conf ?)

I think I adapted gnumed.conf.example.

>               mime_type2file_extension.conf
>                       (derived from
>                       mime_type2file_extension.conf.example ?

Hmmm, do we actually really need this in Debian? Mimetype image/x-bmp
should work out of the box - probably I should drop this file from the

Kind regards


Klarmachen zum Ă„ndern!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]