[Gpe-list] libschedule -> libgpeschedule ?

[Neil Williams]

Re-sending this without a GnuPG signature as a last-ditch effort to get
it through whatever filtering is preventing me posting to the list. If
this gets through, please can someone look at the attachment detection
code so that GnuPG signatures are allowed? Ta.

It's not always ideal to choose a common word for a library package and
when I first packaged libschedule for Debian (aiming eventually at
Emdebian), I wanted to make sure that libschedule was clearly identified
as related to GPE and not related to lots of other programs out there
that may have something to do with scheduling but not GPE. So I renamed
libschedule as libgpeschedule using patches for Debian.

In doing so, I underestimated the amount of ongoing work and just plain
awkwardness that would result during the builds of packages using
libschedule, like gpe-calendar.

There still is the potential for confusion about the purpose of a
package called libschedule in Debian so I'm wondering if there is any
appetite here to consider a rename upstream? There's no actual name
collision (yet), just a lack of clarity.

libsoundgen and libhandoff are OK. I know GPE has been developing
nicely as a stand-alone environment but if having GPE in Debian is a
GoodThing(tm) then it would be nice to consider issues outside GPE when
creating or transitioning libraries.

Comments?

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/