On Wed Oct 07 06:21:22 2015, KAPPA wrote:
Show quoted text> Switching to GtkBuilder requires resources. It may be planned but
> right now, libglade works ok and Gtk2::GladeXML works ok if only has
> some minor problems when installing from CPAN.
Unarchiving and updating Gtk2::GladeXML also requires resources; not only Gtk-Perl project resources, but Gnome sysadmin resources.
Show quoted text> The proposed change is more about CPAN and its client ecosystem than
> about Gtk/GNOME. I suppose that we are able to fix it without
> bothering GNOME people. I am ready to upload and co-maintain this.
IMO comaint isn't really an option here; that would mean we (the Gtk-Perl project) were open to to expending resources on software that was effectively abandoned by the upstream developers over 6 years ago. For people who are already using Gtk-Perl, and more importantly, people who might want to use it in the future, the way forward is to use Gtk2::Builder instead of Gtk2::GladeXML. You should take this fact into account for your future project planning.
So, from here, what I will do is I will ask the Gnome sysadmins to unarchive Gtk2::GladeXML.
If I get push access to the Gtk2::GladeXML repo, I'll apply your updated meta file; in addition, I will clearly mark the module as deprecated in favor of Gtk2::Builder, and do a "final" release for this module. I will also clearly state in the POD that any code that is using Gtk2::GladeXML should be migrated to Gtk2::Builder, and not to expect any more releases for Gtk2::GladeXML. From that point on, the only changes that will be accepted will be patches for changes made by the upstream Gnome libglade project; seeing as how the Gnome devs aren't making any more releases for libglade, I don't expect any new changes to Gtk2::GladeXML.
If I don't get push access, or if I do get a chance to make a release and you want more changes past that point, what I recommend you do is to fork the module from Git, and create a new module on CPAN, making it explicitly clear that 1) the upstream library for this module is deprecated, and 2) that you are the sole point of support for that module, not the Gtk-Perl project.
If you do decide to fork and release to CPAN, do not use the Gtk2:: toplevel namespace; Gtk2::Ex:: would be more appropriate.
You could also use something like pinto to build a private CPAN repo to publish your forked module, if you don't feel like going through the work of supporting a module on CPAN.
I'll update this ticket once I hear back from the Gnome sysadmins.