MaxPerl has asked for the wisdom of the Perl Monks concerning the following question:

Dear Perl Monks,

I am happy to present you my bindings of the Enlightenment Foundation libraries under Perl-Efl. Even if there is much to do, the Elementary stuff is already very usable (see for example the editor under eSourceHighlight and the examples at the Perl-Efl distribution). In the newest version there is also support for the Emotion multimedia library :-)

Unfortunately I have a problem with uploading the module to CPAN. There seems to be a conflict with the old module EFL which isn't active developed since 2010 and can't be compiled with actual versions of the efl-lib. The author wrote me, that he would transfer the permissions but has no access to PAUSE/CPAN anymore. Has someone an idea, how I could get my module to CPAN? I think it is a very useful GUI library...

Thanks in advance and best wishes,

Max

2022-09-18 Athanasius linkified links.

  • Comment on Efl bindings and permission problems in CPAN

Replies are listed 'Best First'.
Re: Efl bindings and permission problems in CPAN
by hippo (Archbishop) on Sep 16, 2022 at 22:53 UTC

    Simple solution: pick another name. If your module isn't even close to the existing one in terms of API then you will be doing everyone (including yourself) a big favour by calling it something else.


    🦛

Re: Efl bindings and permission problems in CPAN
by pryrt (Abbot) on Sep 16, 2022 at 16:52 UTC
    According to perlfaq7, if you cannot contact the original owner (or, by inference, if the original owner no longer has PAUSE credentials), you should be able to email modules@perl.org and explain the situation (include the email response from the original owner if you have it)
Re: Efl bindings and permission problems in CPAN
by MaxPerl (Acolyte) on Sep 17, 2022 at 10:39 UTC

    Thanks for your answers. I have already asked modules@perl.org, but got no reaction until now. Obviously I still have to wait a little bit..

    Renaming unfortunately is no option, since the XS packages are derived from the C structs (I think, this led to the permission problem and not the not equal anyway module name per se :-S

        of course, it would be possible. But I use for example elm_widget_type_get() (and will use it more in future) and translate the returned c-struct with a simple regex pattern into the appropriate perl name. So it is a sensfull design decision, that I don't want to give up for a old, not anymore maintained module that can't be compiled with current versions of efl... Not to mention all the work a redesign would require...
Re: Efl bindings and permission problems in CPAN
by InfiniteSilence (Curate) on Sep 17, 2022 at 20:07 UTC

    There should be a deadwood flag with a community-set limit on modules. Does not compile; too old...it really should go into the chopper.

    Celebrate Intellectual Diversity

      Recycling names is an iffy proposition