Re: Debian GNOME Policy, Mark II
- To: debian-gtk-gnome@lists.debian.org
- Subject: Re: Debian GNOME Policy, Mark II
- From: Colin Walters <walters@debian.org>
- Date: 18 Jan 2003 11:43:34 -0500
- Message-id: <1042908214.11139.25.camel@space-ghost>
- In-reply-to: <20030118080821.GQ1857@lazarus>
- References: <1042539568.15001.10.camel@aries.180sw.com> <1042826839.26408.15.camel@space-ghost> <20030118014633.GA1857@lazarus> <1042869026.8697.22.camel@space-ghost> <20030118063059.GP1857@lazarus> <1042875006.9601.2.camel@space-ghost> <20030118080821.GQ1857@lazarus>
On Sat, 2003-01-18 at 03:08, Jeff Waugh wrote:
> <quote who="Colin Walters">
>
> > I understand what the maintainership issues are, but what other user
> > issues are you thinking of?
>
> Consider gnome-vfs-extras, which is split out in upstream for licensing
> reasons. That's already rough, but if it were split into its component
> methods, they would be very hard to 'discover'.
To comply with policy then, all we'd need to do is rename it to
gnomevfs-methods-extra.
> An easy answer to this is that users should always use the 'gnome'
> metapackage, but that's not always how users work. ;-)
>
> (There are other examples of this granularity becoming a usability issue,
> including themes, etc., but I've stuck with vfs methods for now.)
Well, in the gnome-vfs-extras case there really isn't another good
choice.
I guess in summary I don't really think that splitting out GnomeVFS
methods will increase this problem.
Reply to: