[Debian GNUstep maintainers] RFS: GNUstep packages naming scheme

[Gürkan Myczko]

Hello Yavor,

> 1) Agree among ourselves about the naming scheme of GNUstep packages.

Check, with notes:

> 2) Ask for ftpmasters' opinion about it.

Did this already happen? Who will do so? When?

> 3) Eventually, make corrections according to ftpmasters' comments.

Can't wait...

> The general plan is to publish this document when it's ready and we
> all agree with its contents.  We should decide how to distribute it:

I don't want to be the blocker, so I agree, but still write my opinions 
on it.

> * As part of the gnustep-make-doc package.  This is straightforward
>   but somewhat "dirty" because it has little to do with upstream
>   GNUstep Make and its manual.  Another disadvantage is that updates
>   to the document will trigger unnecessary upgrades of the
>   gnustep-common package for all users that have it installed.
> 
> * As a separate native package:
>   - gnustep-policy (short and clear but may be confused with some
>     upstream policy).
>   - debian-gnustep-policy

Ok for me.

>   - pkg-gnustep-policy
>   - gnustep-team-policy

Also ok for me.

>   - something else.

Could go with meta-gnustep pkg to /usr/share/doc as well?

> * As a separate binary package of a native source package that also
>   provides Debian-specific stuff (dh_gnustep, etc.) we currently ship
>   in the gnustep-make package.
> 
> All of this is not urgent, I guess at least a few months will pass
> until it's ready.
> 
> Comments welcome (both for the document itself and the plan).

Plan comments above, document notes follow:

      Section: If a particular section is suitable, it should be used.
      For example, 'pikopixel.app' should be in the 'graphics' section,
      'fisicalab.app' in section 'education', 'lusernet.app' in 'news'.
      If no section is appropriate or if the app is basically closely
      related to GNUstep ('gworkspace.app' or 'systempreferences.app'
      being the perfect examples for this), use section 'gnustep'.

fine for me, but I'd like to have them all visible at one place,
the team qa page, we lost some to other teams, can packages be in 
multiple teams?

Otherwise, great document, thank you.

> _______________________________________________
> Debian GNUstep maintainers mailing list
> pkg-GNUstep-maintainers at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-gnustep-maintainers