Re: Efl bindings and permission problems in CPAN

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

Comment on Re: Efl bindings and permission problems in CPAN

Replies are listed 'Best First'.
Re^2: Efl bindings and permission problems in CPAN by Anonymous Monk on Sep 17, 2022 at 11:51 UTC
Renaming unfortunately is no option, since the XS packages are derived from the C structs ( sure its an option, c structs dont control xs module name, you can use anything https://perldoc.perl.org/perlxs#The-MODULE-Keyword	[reply]
Re^3: Efl bindings and permission problems in CPAN by Anonymous Monk on Sep 17, 2022 at 19:54 UTC
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...	[reply]
Re^4: Efl bindings and permission problems in CPAN by bliako (Abbot) on Sep 19, 2022 at 14:49 UTC
so you want to remove an existing and obsolete module from CPAN and then add yours which is named differently to replace its functionality? If yes, then state the problem a bit more abstractly. Even if original module author agrees, this can create problems (anon's comment about recycling names, though comment does not contain supporting arguments). So, state your problem in abstract terms so that a general policy can be decided. my opinion.	[reply]