[pkg-fso-maint] Renaming gsm0710muxd?

Luca Capello luca at pca.it
Wed Feb 18 18:43:49 UTC 2009


Hi Joachim!

On Wed, 18 Feb 2009 17:24:13 +0100, Joachim Breitner wrote:
> I have brought it up before: What we package as gsm0710muxd is a fork
> of the muxer written by the pyNeo guy, and they are incompatible.

Well, what I knew was that FSO would have migrated to pyNeo's
gsmu0710muxd in the long term:

  http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-January/001033.html

> In a while, the FSO team will replace it by their own
> re-implementation[1], this time with a proper name (fso-abyss).

I hope "proper" was a joke...

> But Josh (who just subscribed this list) from the pyNeo team has
> already created Debian packages for their software,

Are you saying that there is another Debian package called gsm0710muxd
and this is different from the pkg-fso one?  I hope Josh's package has
never gone public yet, otherwise we are in a very bad situation, which
adds more to the already shitty one.

> and I would like to get their packages into the repository as soon as
> possible (waiting for something happening from the “competing” stack
> would not be motivational enough).

I fully agree and the latest news completely change the considerations I
made at

  http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-January/001046.html

> I couldn’t immediately find out whether fso-abyss is already function
> and usable with the current frameworkd. If it is, then it’s clear what
> to do: Package fso-abyss, change the dependency in fso-frameworkd to
> that and then package the original gsm0710muxd together with thy pyNeo
> stuff

fso-abyss is already at version 0.3.0, thus I would expect it being
functional, at least this is what I understand from the README.  The
best thing would be to ask on the smartphones-* mailing lists.

The major problem, however, is that as soon as we switch to it we will
probably need an fso-frameworkd snapshot.  And this will delay any
fso-frameworkd upload to main, again.

> But if not, how should we proceed?
>
>  * Rename gsm0710muxd to fso-gsm0710muxd and make appropriate
> Depends/Conflicts, until we can use fso-abyss?
>  * Upload pyNeo’s gsm0710muxd as pyneo-gsm0710muxd, with the possibility
> of upsetting the original author? We could still later rename it back
> when fso-abyss can be used.
>  * Put pyNeo package somewhere else until fso-abyss is ready?

I would go with the first option, for two reasons:

1) gsm0710muxd is pyNeo's software and we should credit it

2) Michael Lauer stated that he will not use the fso-gsm0710muxd name

     http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-January/001035.html

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090218/14189949/attachment.pgp 


More information about the pkg-fso-maint mailing list