Re: GNOME Games split
On Tue, Oct 16, 2012 at 11:36:09PM +0200, Thomas H.P. Andersen wrote: > On Tue, Oct 16, 2012 at 10:33 PM, Robert Ancell > wrote: > > On 16 October 2012 23:01, Allan Day wrote: > >> > >> I wonder: are you looking for maintainers for any of these games, or > >> are you going to take charge of all of them? Also, are any of these > >> deemed to be "core" right now? > > > > We're currently discussing the maintainership of them at the moment: > > https://mail.gnome.org/archives/games-list/2012-October/msg1.html > > Short answer, I think if anyone was looking to maintain a project > > (e.g. someone who is learning GNOME) then they'd be very welcome. > > As I wrote in the linked mail I would like to keep maintaining > swell-foop and five-or-more. > For the rest my plan was to keep doing the regular releases, build > fixes, porting, etc to keep the games alive. But I would love to see > someone take over maintainership and active development of the > individual games. I will also gladly "mentor" anyone interested in > gradually taking over if there is need for that. I like gnome and gtk and I like games so I can help here, but I need mentoring because I don't make any release and I don't know the "good way" to mantain a gnome module. -- Daniel Garcia 0034 668 810 742 It's not magic, it's wadobo! http://wadobo.com pgp3IyTglBCU9.pgp Description: PGP signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: About lib version and git
On Tue, Jan 16, 2018 at 9:35 PM, Philip Withnall wrote: > On Tue, 2018-01-16 at 12:17 -0600, Federico Mena Quintero wrote: > > It doesn't really matter when you do it. There are some important > > things: > > > > * Make sure the new header files are parallel-installable with the > > old > > ones. > > > > * Make sure the soname in the library changes. Grep for LT_VERSION > > here: https://wiki.gnome.org/MaintainersCorner/Releasing - although > > I'm > > not sure how this works in Meson. > > > > Just to avoid apps that use the old API to inadvertently try to > > compile/link with the new one. > > There is a documentation page covering this in its entirety: > > https://developer.gnome.org/programming-guidelines/unstable/parallel-in > stallability.html.en > > Pay attention to all of it; if there’s only one part of your library > which is not parallel installable, the whole thing is effectively not > parallel installable. I've changed the version number and the build names so now for the next version all goes with a different name, so I think that this will allow different versions of libgepub running in the same system. https://gitlab.gnome.org/GNOME/libgepub/commit/d721c7ebba040b935d3c8e0456ccf5a4a674e531 These are all files that will install libgepub: local local/lib local/lib/libgepub-0.6.so local/lib/girepository-1.0 local/lib/girepository-1.0/Gepub-0.6.typelib local/lib/libgepub-0.6.so.0.0.0 local/lib/libgepub-0.6.so.0 local/lib/pkgconfig local/lib/pkgconfig/libgepub-0.6.pc local/share local/share/gir-1.0 local/share/gir-1.0/Gepub-0.6.gir local/include local/include/libgepub-0.6 local/include/libgepub-0.6/gepub-widget.h local/include/libgepub-0.6/gepub-archive.h local/include/libgepub-0.6/gepub-text-chunk.h local/include/libgepub-0.6/gepub-doc.h local/include/libgepub-0.6/gepub.h With this change, anyone that uses libgepub should specify the version in his code and link with -lgepub-0.6 for example. Is this the recommended way to do that? Regards. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
El mié., 27 feb. 2019 15:10, Daniel Mustieles García < daniel.mustie...@gmail.com> escribió: > Hi Andre, > > I think Gtranslator's old bugs could be simply deleted or closed, since > the new version fixes most of them, and the other ones are deprecated. > > Ccing Daniel García, so he can give us his opinion about this. > Yes, old bug can be deleted. > Thanks! > > El mié., 27 feb. 2019 a las 14:35, Andre Klapper () > escribió: > >> On Tue, 2019-02-26 at 08:19 +0100, Andre Klapper wrote: >> > Currently GNOME Bugzilla does not show the "Browse" product page when a >> > product has been disabled for new bug entry >> >> Fixed now thanks to the help of Carlos and Olav. Pages like >> https://bugzilla.gnome.org/page.cgi?id=browse.html&product=gnome-shell >> work again so you can see all your old boogs and triage them! Right? >> >> If you want your project's (open) Bugzilla tasks to get copied to >> Gitlab one day in the future: A ticket at >> https://gitlab.gnome.org/Infrastructure/GitLab/issues/ >> is welcome to sort out things. >> We still have 22015 open tickets in 190 Bugzilla products... >> >> Happy cleanup! >> andre >> -- >> Andre Klapper | ak...@gmx.net >> https://blogs.gnome.org/aklapper/ >> >> >> ___ >> desktop-devel-list mailing list >> desktop-devel-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/desktop-devel-list >> > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
