New release for ptlib/opal needed by ekiga
Hi, A new release of ekiga, 4.0.0, is made right now. As usually :o(, it needs new ptlib and opal library releases, 2.10.9 respectively 3.10.9. I will upload them shortly. Please contact me for any question. Cheers, -- Eugen Dedu Ekiga maintainer ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
[PATCH] rename session-save to -quit in man page
The gnome-session-properties(1) man page references gnome-session-save, which has been renamed to gnome-session-quit. Trivial patch. Please apply. This patch originated in development for SprezzOS 1.0.0. --- doc/man/gnome-session-properties.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/man/gnome-session-properties.1 b/doc/man/gnome-session-properties.1 index 97fa344..c7ef1af 100644 --- a/doc/man/gnome-session-properties.1 +++ b/doc/man/gnome-session-properties.1 @@ -21,4 +21,4 @@ If you find bugs in the \fIgnome-session-properties\fP program, please report these on https://bugzilla.gnome.org. .SH SEE ALSO .BR gnome-session(1) -.BR gnome-session-save(1) +.BR gnome-session-quit(1) -- 1.8.0 -- nick black http://www.sprezzatech.com -- unix and hpc consulting to make an apple pie from scratch, you need first invent a universe. From 547d856d0a3360e28bc2b51ec8041e01f1d06973 Mon Sep 17 00:00:00 2001 From: nick black nick.bl...@sprezzatech.com Date: Sat, 24 Nov 2012 23:47:34 -0500 Subject: [PATCH] rename session-save to -quit in man page --- doc/man/gnome-session-properties.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/man/gnome-session-properties.1 b/doc/man/gnome-session-properties.1 index 97fa344..c7ef1af 100644 --- a/doc/man/gnome-session-properties.1 +++ b/doc/man/gnome-session-properties.1 @@ -21,4 +21,4 @@ If you find bugs in the \fIgnome-session-properties\fP program, please report these on https://bugzilla.gnome.org. .SH SEE ALSO .BR gnome-session(1) -.BR gnome-session-save(1) +.BR gnome-session-quit(1) -- 1.8.0 signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Ekiga branched
Hello, I created a new branch for Ekiga 4.0.x and the tag EKIGA_4_0_0 for this release. Unfortunately, the recent history showed that we cannot keep up with gnome releases, so we called the new branch v4_0. The branch is in string freeze. Cheers, Eugen -- Eugen Dedu Associate Professor / Maître de conférences UFC/FEMTO-ST Institute Montbéliard, France tel. +33 (0)3 81 99 47 75 http://eugen.dedu.free.fr ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Using the Unicode ellipsis (…) instead of three periods
on., 05.12.2012 kl. 09.56 -0500, skrev Shaun McCance: On Tue, 2012-12-04 at 17:24 -0500, Matthias Clasen wrote: On Tue, Dec 4, 2012 at 1:48 PM, Philip Withnall phi...@tecnocode.co.uk wrote: On Tue, 2012-12-04 at 09:51 -0500, Matthias Clasen wrote: On Tue, Dec 4, 2012 at 9:21 AM, Shaun McCance sha...@gnome.org wrote: Is this really the right thing to do. Even the Microsoft page uses the rather wishy-washy Consider using the ratio symbol, as if they're not quite sure this is a good idea. It does look nicer, but it's semantically wrong. A time is not a ratio. How does Orca read it? I don't really have an answer to the philosophical question of what a 'ratio' really is and whether 9-colon-49 is any more correct than 9-ratio-49 when it comes to representing time. But I can say that Orca reads the one like the other: nine fortynine. Perhaps more importantly, the ratio character behaves differently in RtL locales than the colon character does. See: http://blogs.msdn.com/b/michkap/archive/2012/02/09/10265712.aspx If I write 09:53 with a colon, it’ll remain left-to-right in RtL locales because the colon is a Unicode number separator. If I write 09∶53 with a ratio character, it’ll appear as 53∶09 in RtL locales. (Tested in gedit.) Is this the behaviour we want? I'd say its up to the translators of each locale to say what format is most appropriate for their language. Date and time formats are translatable for a reason... It hadn't occurred to me to make the time display on audio/video controls translatable in yelp-xsl. I used to mark a lot more for translation, but I scaled back on the formatting stuff when I saw nobody did legitimate translations of them. I looked at the po files in totem and gnome-shell. Nobody seems to actually translate how times are formatted. Date format, yes. And there's the difference between using 12- or 24-hour clocks. But when it comes down to the format HH:MM:SS, nobody translates it. It's always the same. I always try to translate time to HH.MM.SS for Norwegian. Maybe I missed that in yelp-xsl, but then it's just a bug in the translation. Cheers Kjartan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Gnome shell is really awesome
I hear that you are adding Gnome 2 features, and I have sat and thought and pondered this for a long time. All Gnome 3 shell really needs is to be gone with global menu, add an application bar at the bottom, and add minimize. At the top add the same Gnome 2 bar way of launching applications. I don't hate Gnome shell, and you could move Activities to a new area on the screen such as the bottom right corner, or hell do it as hot corners and allow the user to choose which hot corner to use for it. Don't completely kill Gnome shell, or the way it handles multiple desktops, that part is perfect. It is also nice to note that this UI actually works rather well with touch screens, so hot corners would be awesome. Best of both worlds! Nobody likes global menus, and I especially hate them on multiple displays while working with a ton of applications. Also It would be nice to hit a hot key on my keyboard like the super key to bring up 'Activities'. You guys are great and thank you for the awesome software. Oh and for the sake of art work, put a white foot next to the Applications label on the menu to offset from the black and make the text labels white too. That would be slick, have the menus pop up like Gnome 3 style... I can picture it now and it would be gorgeous. If you want some mock up art, I will actually work on something in Gimp later today. Nothing over the top, keeping with the simplistic look and feel of Gnome, without being too flashy. Keeping the work that you have/want to put into it to a bare minimum. Again thank you all for this amazing software, and I know others demand it, but most of you work on this for free, and I wanted to let you all know that I do not forget this when using it, and that I appreciate the ever expanding and improvements you all make. Even with the regressions of Gnome 3 shell, it is still awesome. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Bugzilla upgrade? [was: Re: GNOME Bugmail: Gmail threading finally working!]
On 12/12/2012 10:28 AM, Andre Klapper wrote: IIRC, when upgrading from 2.20 to 3.4 we received gracious sponsoring by Canonical to pay Max for this task. If nobody has plans to try, this might be something to defer to the foundation board in order to organize sponsoring? A rundown of what happened last time: http://gnomejournal.org/article/96/canonical-upgrading-gnome-bugzilla-and-commercial-sponsorship -- Sumana Harihareswara http://brainwane.net ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
gnome desktop
I think Gnome should have a word under each icon so I do not have to guess what the picture is. After all an icon is just a picture. And you should not have to point to that icon to see that word. For this reason Gnome 2 is a much better lay out than Windows 7. But Windows 8 is a better layout than Gnome 3 for the very same reason. Remember , the first priority is to make the program easy to learn. Other than that you all do a super excelent job. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome goals for 3.6
Just a quick question about this topic. Which is the attribute equivalent to small? I'm migrating gnome-terminal and I need to change this value. Many thanks! 2012/5/21 Matthias Clasen matthias.cla...@gmail.com On Sun, May 20, 2012 at 1:25 PM, Piotr Drąg piotrd...@gmail.com wrote: Since my last email I have found examples of font size attributes, like this one: attributes attribute name=size value=1/ /attributes But value is different in almost every case, so I don't know how reliable this is. big is equivalent to scale=1.2 ___ gnome-i18n mailing list gnome-i...@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome goals for 3.6
Thanks!! :) 2012/12/17 Olav Vitters o...@vitters.nl On Mon, Dec 17, 2012 at 10:44:32AM +0100, Daniel Mustieles García wrote: Just a quick question about this topic. Which is the attribute equivalent to small? I'm migrating gnome-terminal and I need to change this value. $ python Python 2.7.3 (default, Aug 5 2012, 23:17:03) [GCC 4.7.1] on linux2 Type help, copyright, credits or license for more information. import pango pango.SCALE_ pango.SCALE_LARGE pango.SCALE_SMALL pango.SCALE_XX_SMALL pango.SCALE_X_SMALL pango.SCALE_MEDIUMpango.SCALE_XX_LARGE pango.SCALE_X_LARGE pango.SCALE_LARGE 1.2 pango.SCALE_SMALL 0.8 -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Fwd: [crossdesktop-devroom] deadline extension for the cross-desktop devroom
The deadline for the crossdesktop devroom has been extended by just a few days, you now have until this Friday to submit talk proposals! Christophe -- Forwarded message -- From: Lydia Pintscher ly...@kde.org Date: 2012/12/15 Subject: [crossdesktop-devroom] deadline extension for the cross-desktop devroom To: fos...@lists.fosdem.org, crossdesktop-devr...@lists.fosdem.org Cc: fosdem-crossdesktop-organizat...@googlegroups.com Hi! We are extending the deadline for the cross-desktop devroom to the 21st of December. You can find the original call for participation at https://lists.fosdem.org/pipermail/fosdem/2012-October/001643.html If you have a relevant topic to talk about please consider submitting a proposal now. There will not be another extension. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher KDE Community Working Group / KDE e.V. board member http://kde.org - http://open-advice.org ___ crossdesktop-devroom mailing list crossdesktop-devr...@lists.fosdem.org https://lists.fosdem.org/listinfo/crossdesktop-devroom ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.7.3
Hi all. GNOME 3.7 development is well underway, with the 3.7.3 snapshot that is marking the third release of this development cycle [1]. To compile GNOME 3.7.3, you can the jhbuild [3] modulesets [4] (which use the exact tarball versions from the official release). A slight complication is that gnome-control-center 3.7.3 does not build against network-manager-gnome 0.9.6.4 (you need current master), so the network panel can not be built. [1] http://live.gnome.org/ThreePointSeven/Features [2] https://live.gnome.org/ThreePointSeven/Features/DropOrFixFallbackMode [3] https://live.gnome.org/GnomeGoals/PortToGstreamer1 [4] http://library.gnome.org/devel/jhbuild/ [5] http://download.gnome.org/teams/releng/3.7.3/ The release notes that describe the changes between 3.7.2 and 3.7.3 are available. Go read them to learn what's new in this release: core - http://download.gnome.org/core/3.7/3.7.3/NEWS apps - http://download.gnome.org/apps/3.7/3.7.3/NEWS The GNOME 3.7.3 release is available here: core sources - http://download.gnome.org/core/3.7/3.7.3 apps sources - http://download.gnome.org/apps/3.7/3.7.3 WARNING! WARNING! WARNING! -- This release is a snapshot of early development code. Although it is buildable and usable, it is primarily intended for testing and hacking purposes. GNOME uses odd minor version numbers to indicate development status. For more information about 3.7, the full schedule, the official module lists and the proposed module lists, please see our colorful 3.7 page: http://www.gnome.org/start/unstable For a quick overview of the GNOME schedule, please see: http://live.gnome.org/Schedule -- Kjartan Maraas ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild
Hi, On Mon, Dec 24, 2012 at 5:53 AM, Lanoxx lan...@gmx.net wrote: Hi, I am using jhbuild and trying to compile anjuta (with anjuta-extras) to test a patch that was applied recently on anjuta-extras. When I run jhbuild build, then I get a huge list of missing system dependencies: (snip) jhbuild build: Required system dependencies not installed. Install using the command 'jhbuild sysdeps --install' or to ignore system dependencies use command-line option --nodeps I have already ran sanitycheck and bootstrap successfully? My OS is Ubuntu 12.10. As jhbuild says, you should run 'jhbuild sysdeps --install'. That tries to install the required packages if they are available in your distribution. -- Jiro Matsuzawa E-mail: jmatsuz...@gnome.org jmatsuz...@src.gnome.org matsuzawa...@gmail.com GPG Key ID: 0xECC442E9 GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Question: Standard formatting of date/time strings
Hi, In Glib there's a structure GDateTime, and there's a function which converts it into a string using a given format string, passed as a parameter. (Personally I work with glibmm, i.e. I use Glib::DateTime) I'd like to convert my datetime object to a string, but how do I choose the format? I'd like to use a format knowing it's a standard common format which will suit any locale. But the documentation says nothing about standard formats. So I checked how Gedit implements the inert-time plugin, and I found an array of format strings, hard-coded. I tried to find the format Nautilus uses but I couldn't find it in the source files... Are there some standard formats I (and everybody else) could use? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Undo system for Gnome applications
Hello, I noticed each Gnome application (Gedit, Gnote, Planner and many many more) has its own way to implement undo-redo capabilities. Is there a reason we don't use a common undo-redo interface? Even if the interface itself is very simple (and it is), using a common one minimizes code duplication, saves time and helps programs integrate. I think having an undo-redo interface in Gtk (or Glib) can be very useful, what do you think? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Gnome
I think Gnome should have a word under each icon, (including the left side ones) so I do not have to guess what the program is(or function) from a picture ( Guess what program is it? etc?! From a picture !). After all an icon is just a picture. And you should not have to point to that icon to see that word. For this reason Gnome 2 is a much better lay out than Windows 7. But Windows 8 is a better layout than Gnome 3 for the very same reason. When we went to touch screen design, we forgot to include a word under each and every icon(especially on left side). Remember , the first priority is to make the program easy to learn. Other than that you all do a super excellent job. Sorry if I sent this before. stdula...@netscape.net ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: build.gnome.org
I'm not sure how I missed this thread.. Regarding maintaining jhbuild up to gtk+ - I would actually like to see this up to at gnome-shell. We have a number of people who I have convinced to help volunteer to resolve bugs for GNOME 3.7, but are very frustrated with getting jhbuild to build for them. We really should make it a goal to get an SDK for our volunteers to help fix issues. We are considering doing a jhbuild hackfest once a month for volunteers to learn and understand how to build under jhbuild and grow enough builders to make it self sustaining. But getting a certain set of modules always in buildable state is a great goal and I hope we can do this. sri On Fri, Jan 18, 2013 at 12:39 AM, Jean-Baptiste Lallement jean-baptiste.lallem...@canonical.com wrote: On 01/16/2013 07:39 AM, Martin Pitt wrote: Hello Colin, Hi Martin, Colin, Colin Walters [2013-01-15 15:34 -0500]: On Tue, 2013-01-15 at 11:07 +0100, Martin Pitt wrote: We have experimented with that a bit, by building https://jenkins.qa.ubuntu.com/**view/Raring/view/JHBuild%** 20Gnome/https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/ Interesting! Looks quite useful. Are you doing anything with respect to the jhbuild sysdeps --install infrastructure or is the system package set maintained manually? Right now in our Juju charm it's a manual list: http://bazaar.launchpad.net/~**jibel/charms/quantal/jhbuild/** trunk/view/head:/files/**jhbuild.config/gnome-core.**sysdepshttp://bazaar.launchpad.net/~jibel/charms/quantal/jhbuild/trunk/view/head:/files/jhbuild.config/gnome-core.sysdeps I'm not quite sure why; Jean-Baptiste, did jhbuild sysdeps not work well enough in principle? In Quantal, there was missing dependencies, so I went the straightest way and installed them directly. Now that I have a better understanding how jhbuild works that's something I want to reconsider for Raring and avoid maintaining them in 2 different places. -- Jean-Baptiste IRC: jibel __**_ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/**mailman/listinfo/desktop-**devel-listhttps://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
Re: build.gnome.org
If you use the last point release moduleset[0] from tarballs I find the experience faster and less error prone. Then I configure the module I want to hack on to build from master and this usually works, in some weird cases, master requires master from another dependency, but this is very rare and addressable case. [0] ftp://ftp.gnome.org/pub/gnome/teams/releng/3.7.4/ 2013/2/7 Sriram Ramkrishna s...@ramkrishna.me: I'm not sure how I missed this thread.. Regarding maintaining jhbuild up to gtk+ - I would actually like to see this up to at gnome-shell. We have a number of people who I have convinced to help volunteer to resolve bugs for GNOME 3.7, but are very frustrated with getting jhbuild to build for them. We really should make it a goal to get an SDK for our volunteers to help fix issues. We are considering doing a jhbuild hackfest once a month for volunteers to learn and understand how to build under jhbuild and grow enough builders to make it self sustaining. But getting a certain set of modules always in buildable state is a great goal and I hope we can do this. sri On Fri, Jan 18, 2013 at 12:39 AM, Jean-Baptiste Lallement jean-baptiste.lallem...@canonical.com wrote: On 01/16/2013 07:39 AM, Martin Pitt wrote: Hello Colin, Hi Martin, Colin, Colin Walters [2013-01-15 15:34 -0500]: On Tue, 2013-01-15 at 11:07 +0100, Martin Pitt wrote: We have experimented with that a bit, by building https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/ Interesting! Looks quite useful. Are you doing anything with respect to the jhbuild sysdeps --install infrastructure or is the system package set maintained manually? Right now in our Juju charm it's a manual list: http://bazaar.launchpad.net/~jibel/charms/quantal/jhbuild/trunk/view/head:/files/jhbuild.config/gnome-core.sysdeps I'm not quite sure why; Jean-Baptiste, did jhbuild sysdeps not work well enough in principle? In Quantal, there was missing dependencies, so I went the straightest way and installed them directly. Now that I have a better understanding how jhbuild works that's something I want to reconsider for Raring and avoid maintaining them in 2 different places. -- Jean-Baptiste IRC: jibel ___ 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 -- Cheers, Alberto Ruiz ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: build.gnome.org
How do you set that up? Do you somehow install the tarballs into the jhbuild install directory? On Feb 6, 2013 9:35 PM, Alberto Ruiz ar...@gnome.org wrote: If you use the last point release moduleset[0] from tarballs I find the experience faster and less error prone. Then I configure the module I want to hack on to build from master and this usually works, in some weird cases, master requires master from another dependency, but this is very rare and addressable case. [0] ftp://ftp.gnome.org/pub/gnome/teams/releng/3.7.4/ 2013/2/7 Sriram Ramkrishna s...@ramkrishna.me: I'm not sure how I missed this thread.. Regarding maintaining jhbuild up to gtk+ - I would actually like to see this up to at gnome-shell. We have a number of people who I have convinced to help volunteer to resolve bugs for GNOME 3.7, but are very frustrated with getting jhbuild to build for them. We really should make it a goal to get an SDK for our volunteers to help fix issues. We are considering doing a jhbuild hackfest once a month for volunteers to learn and understand how to build under jhbuild and grow enough builders to make it self sustaining. But getting a certain set of modules always in buildable state is a great goal and I hope we can do this. sri On Fri, Jan 18, 2013 at 12:39 AM, Jean-Baptiste Lallement jean-baptiste.lallem...@canonical.com wrote: On 01/16/2013 07:39 AM, Martin Pitt wrote: Hello Colin, Hi Martin, Colin, Colin Walters [2013-01-15 15:34 -0500]: On Tue, 2013-01-15 at 11:07 +0100, Martin Pitt wrote: We have experimented with that a bit, by building https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/ Interesting! Looks quite useful. Are you doing anything with respect to the jhbuild sysdeps --install infrastructure or is the system package set maintained manually? Right now in our Juju charm it's a manual list: http://bazaar.launchpad.net/~jibel/charms/quantal/jhbuild/trunk/view/head:/files/jhbuild.config/gnome-core.sysdeps I'm not quite sure why; Jean-Baptiste, did jhbuild sysdeps not work well enough in principle? In Quantal, there was missing dependencies, so I went the straightest way and installed them directly. Now that I have a better understanding how jhbuild works that's something I want to reconsider for Raring and avoid maintaining them in 2 different places. -- Jean-Baptiste IRC: jibel ___ 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 -- Cheers, Alberto Ruiz ___ 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
Re: build.gnome.org
OK, what you're saying is that you get all the modules you want to get except the one module you want to hack on. You get that from git, and then it should work. This makes sense because it's not likely going to run into dependency problems like you would if you get all your packages from the master packages. The downside though is that you have to do a configure;make;make install for a lot of packages. Unless there is some hack on jhbuild to build from tarballs? sri On Wed, Feb 6, 2013 at 6:35 PM, Alberto Ruiz ar...@gnome.org wrote: If you use the last point release moduleset[0] from tarballs I find the experience faster and less error prone. Then I configure the module I want to hack on to build from master and this usually works, in some weird cases, master requires master from another dependency, but this is very rare and addressable case. [0] ftp://ftp.gnome.org/pub/gnome/teams/releng/3.7.4/ 2013/2/7 Sriram Ramkrishna s...@ramkrishna.me: I'm not sure how I missed this thread.. Regarding maintaining jhbuild up to gtk+ - I would actually like to see this up to at gnome-shell. We have a number of people who I have convinced to help volunteer to resolve bugs for GNOME 3.7, but are very frustrated with getting jhbuild to build for them. We really should make it a goal to get an SDK for our volunteers to help fix issues. We are considering doing a jhbuild hackfest once a month for volunteers to learn and understand how to build under jhbuild and grow enough builders to make it self sustaining. But getting a certain set of modules always in buildable state is a great goal and I hope we can do this. sri On Fri, Jan 18, 2013 at 12:39 AM, Jean-Baptiste Lallement jean-baptiste.lallem...@canonical.com wrote: On 01/16/2013 07:39 AM, Martin Pitt wrote: Hello Colin, Hi Martin, Colin, Colin Walters [2013-01-15 15:34 -0500]: On Tue, 2013-01-15 at 11:07 +0100, Martin Pitt wrote: We have experimented with that a bit, by building https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/ Interesting! Looks quite useful. Are you doing anything with respect to the jhbuild sysdeps --install infrastructure or is the system package set maintained manually? Right now in our Juju charm it's a manual list: http://bazaar.launchpad.net/~jibel/charms/quantal/jhbuild/trunk/view/head:/files/jhbuild.config/gnome-core.sysdeps I'm not quite sure why; Jean-Baptiste, did jhbuild sysdeps not work well enough in principle? In Quantal, there was missing dependencies, so I went the straightest way and installed them directly. Now that I have a better understanding how jhbuild works that's something I want to reconsider for Raring and avoid maintaining them in 2 different places. -- Jean-Baptiste IRC: jibel ___ 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 -- Cheers, Alberto Ruiz ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: build.gnome.org
On Wed, 2013-02-06 at 20:36 -0800, Sriram Ramkrishna wrote: OK, what you're saying is that you get all the modules you want to get except the one module you want to hack on. You get that from git, and then it should work. Strictly speaking you only need the dependencies of the programs you want to hack on. This makes sense because it's not likely going to run into dependency problems like you would if you get all your packages from the master packages. The downside though is that you have to do a configure;make;make install for a lot of packages. Unless there is some hack on jhbuild to build from tarballs? The hack you need is to download the module sets from http://ftp.gnome.org/pub/GNOME/teams/releng/3.7.4/ ;-) You might want read: https://live.gnome.org/Smoketesting And eventually, check: http://git.gnome.org/browse/releng/tree/ and https://live.gnome.org/ReleasePlanning/MakingARelease to get an idea how the release team does it. -- Germán Poo-Caamaño http://calcifer.org/ signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
