[Debian GNUstep maintainers] [Debian GNUstep maintainers]

[Gürkan Sengün]

--Signature=_Thu__23_Dec_2004_20_52_46_+0100_kJ_+r84mLw==KtRL
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I have some suggestions

>I think it's best to using the mailing list to discuss about the GNUstep=3D
> packaging policy.
I agree

>1- First we should discuss about names of simple packages (i.e with only=3D
> one app, or only one framework, or only one bundle...)
> 1.1- Source packages:
>	 <name>.app or <name>.framework ...
>	Should <name> should be the same than upstream (using lowercase) ?
>	For libraries there is a Debian policy and a Debian libraries packaging=3D
> guide.
i have named all the software based on gnustep packages names (source and b=
inary) like this
debian pkg name		example
application.app		textedit.app
sometool.tool		mknfonts.tool
some.bundle		wildmenus.bundle
extension.service	latex.service
and.framework		pdfkit.framework

apropos frameworks, can someone package slideshowkit? from here:
http://home.gna.org/gsimageapps/

i have packaged Cenon.app documentation as cenon-doc. would cenon.app-doc b=
e better? i'm not sure on this

i *did* change upstream name where appropriate: gmines -> mines, gshisen ->=
 shisen. i would also change gworkspace to workspace

> 1.2- Binary packages
>	I suggest same names than in source package.
as 1.1

>2- Wrappers
> 2.1- Wrapper name
>	Should we use same name than upstream (with uppercase) ?
>	Should we suffix with .app, if the name is too generic or confusive (li=3D
>ke Desktop) ?

same as in 1.1, TextEdit, Shisen, i have added wrapper scripts for
mknfonts.tool (update-nfonts) and WildMenus (to turn it on/off, write some =
value
into user prefs using defaults). I would NEVER add .app to the binary, that=
'll
confuse gworkspace probably. .app are directories that you start. having
non-directory files like that will break consistency and concept of "fat bi=
naries".

there is two of this! gnustep-app-wrapper and gnustep-tool-wrapper

> 2.2- Manpages
>	Any suggestions ?
they are worthless if they are not shipped upstream. but for debian policy =
satisfaction i write them, althought that's probably not the best solution.

>3- Menu
> 3.1 Menu title:
>	I suggest same than wrapper name
Yes I agree, that's best.


>4- Complex packages (that mix apps, frameworks, tools or libraries like =3D
>addresses-for-gnustep)
i have a little example of 3 apps and one tool at www.linuks.mine.nu/i_debi=
an/backbone/
if that's possible i'd do it that way.

>4.1- Source packages:
>	How to name them ?
>4.2- Binaries packages
>	Any suggestions ?
as in 1.1?=20
Did you ever see the Installer.app on OPENSTEP? i'm not sure if i have a=20
screenshot of it, but i should make one,
http://www.linuks.mine.nu/openstep/

debian menu files should have a icon, but the policy was saying 16colors (n=
ot so
strict anymore) and xpm... now how are we going to handle this? i know
our preferede Window Maker doesn't show icons. but fvwm, gnome, kde do.

yours,
g=FCrkan

--Signature=_Thu__23_Dec_2004_20_52_46_+0100_kJ_+r84mLw==KtRL
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFByyIQfI36WwmZVIsRAnWOAJ9mfzvbJIYrNeTG5ZSFIM4MdZGsMQCfUPaW
MziToFxDL65M29yBp0eeFps=
=NFXr
-----END PGP SIGNATURE-----

--Signature=_Thu__23_Dec_2004_20_52_46_+0100_kJ_+r84mLw==KtRL--