Re: TARBALLS DUE: GNOME 2.23.3 Development Release
On Sun, 2008-06-01 at 11:56 +0200, Vincent Untz wrote: Le samedi 31 mai 2008, à 21:04 -0400, Behdad Esfahbod a écrit : On Sat, 2008-05-31 at 18:07 +0300, Lucas Rocha wrote: Once more, a late reminder. This is so cool, isn't it? Actually it's not. Ideally I like to see the reminder go out Wednesday before, so I can schedule some devel hacking before the deadline. Well, the reminder is not to get late development done -- it's to have tarballs done. The reason it's sent on Friday is, I believe, to give a chance to people who might be away on the week-end to plan their work on Monday. I know, but many times it's either: 1) I need to finish some features I started to get them in release-ready status, even for devel releases that are supposed to be snapshots 2) Nothing has been done on the module since last devel release. This sounds bad, but happens with many modules that are mostly in maintenance mode. Pango is a great example of this. There are months that Pango hacking takes a large part of my time, and there are other months when other projects are (like right now). Given that some changes need to be done early in the release cycle, I can push myself to get something done for each devel release. If you need a reminder to get development done before releases, there's the ical file. But I can set up a cron job for you if you want something more annoying that can help you improve your productivity ;-) Ok, I'll try to set up evo to send notifications and I'll see how far that goes. But then where's the ice cream in that? Vincent Cheers, -- behdad http://behdad.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin, 1759 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: TARBALLS DUE: GNOME 2.23.3 Development Release
Hey, 2008/6/1 Behdad Esfahbod [EMAIL PROTECTED]: On Sat, 2008-05-31 at 18:07 +0300, Lucas Rocha wrote: Once more, a late reminder. This is so cool, isn't it? Actually it's not. Ideally I like to see the reminder go out Wednesday before, so I can schedule some devel hacking before the deadline. The This is so cool was supposed to sound ironic. Of course it's not cool. Personally, I think Friday is good day for the reminder (because most of the time I do GNOME hacking on weekends). It would be nice to know what other developers think about this. Depending on the response, this is definitely something to be discussed on release-team. --lucasr ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Changing bookmarks file location
Hi, folks. In previous Vinagre I am storing the bookmarks file at ~/.gnome2. In current version, I would like to move it to ~/.config - g_get_user_config_dir(). What is the best way to do this? Just point to new location and add a note on README for previous users telling them to manually move the file? Any tip? Thanks, -- Jonh Wendell www.bani.com.br ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: TARBALLS DUE: GNOME 2.23.3 Development Release
Le samedi 31 mai 2008, à 21:04 -0400, Behdad Esfahbod a écrit : On Sat, 2008-05-31 at 18:07 +0300, Lucas Rocha wrote: Once more, a late reminder. This is so cool, isn't it? Actually it's not. Ideally I like to see the reminder go out Wednesday before, so I can schedule some devel hacking before the deadline. Well, the reminder is not to get late development done -- it's to have tarballs done. The reason it's sent on Friday is, I believe, to give a chance to people who might be away on the week-end to plan their work on Monday. If you need a reminder to get development done before releases, there's the ical file. But I can set up a cron job for you if you want something more annoying that can help you improve your productivity ;-) Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonh Wendell wrote: | What is the best way to do this? Just point to new location and add a | note on README for previous users telling them to manually move the | file? Couldn't you detect if there's anything in the old place and if so, automatically move it to the new place (as well as notifying the user about the migration)? Just an idea... Cheers, - -- Og B. Maciel [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhC8c4ACgkQUDEm1NXPwgLDnACfaFWFBdSpx7kDKb22Az1RZv5M SgEAoI+FpRp5Dnz+B8ec1sJldl6pfaEI =JE6y -END PGP SIGNATURE- ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
Em Dom, 2008-06-01 às 15:00 -0400, Og Maciel escreveu: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonh Wendell wrote: | What is the best way to do this? Just point to new location and add a | note on README for previous users telling them to manually move the | file? Couldn't you detect if there's anything in the old place and if so, automatically move it to the new place (as well as notifying the user about the migration)? Just an idea... Cheers, - -- Og B. Maciel Hi, Og. Sure I could do that, but it would lead to an overhead every time the program is started... -- Jonh Wendell www.bani.com.br ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
Le dimanche 01 juin 2008 à 10:38 -0300, Jonh Wendell a écrit : Hi, folks. Hello Jonh What is the best way to do this? Just point to new location and add a note on README for previous users telling them to manually move the file? Any tip? Thanks, I'm not sure users are intersted with the location of the bookmarks file (I'm perhaps totally wrong). I would advice to just add few lines to migrate the directory to the former to the new location. Also, adding in the NEWS file the folder has changed and it should be transparent won't hurt. :) Regards ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
On Sun, Jun 1, 2008 at 9:09 PM, Jonh Wendell [EMAIL PROTECTED] wrote: Sure I could do that, but it would lead to an overhead every time the program is started... It could only do the check if configuration is not found in the expected (new) place. -- Patryk Zawadzki PLD Linux Distribution ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
Hi, On Sun, 2008-06-01 at 10:38 -0300, Jonh Wendell wrote: Hi, folks. In previous Vinagre I am storing the bookmarks file at ~/.gnome2. In current version, I would like to move it to ~/.config - g_get_user_config_dir(). What is the best way to do this? Just point to new location and add a note on README for previous users telling them to manually move the file? Any tip? This has been brought up for a number of projects in GNOME [1]. I wonder if we could / should reach some consensus on the best way to do this across all modules? I've been holding off doing this in yelp because I can't think of a good way to go about it. It feels slightly odd adding code to check the old location and doing migration while running the app (even if it is only done once). On the other hand, we could add it to the build process, which would screw anyone building new local copies of modules. Otherwise, we could just add a note to the README (which has it's own problems, unless you add it as a big notice). There are problems with all approaches when running multiple versions of GNOME (i.e. jhbuild sessions). If we unconditionally check and move, someone somewhere (probably me) is going to use their normal user to log into a jhbuild session and break their normal build. Maybe adding code to check while running is the best way. And maybe I'm just rambling on and should be quiet. Don [1] see http://bugzilla.gnome.org/show_bug.cgi?id=522849 for the yelp bug, and http://bugzilla.gnome.org/show_bug.cgi?id=523057 for the tracking bug across the whole of GNOME. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
On Sun, 2008-06-01 at 20:20 +0100, Don Scorgie wrote: This has been brought up for a number of projects in GNOME [1]. I wonder if we could / should reach some consensus on the best way to do this across all modules? I've been holding off doing this in yelp because I can't think of a good way to go about it. I would suggest adding the changes for all the modules to some script which would get run either when you upgrade GNOME, or just once on session start. However, this does have the problem of moving module-specific changes out of the module and into an aggregate area, which may or may not work. Philip signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
On Sun, Jun 1, 2008 at 3:20 PM, Don Scorgie [EMAIL PROTECTED] wrote: This has been brought up for a number of projects in GNOME [1]. I wonder if we could / should reach some consensus on the best way to do this across all modules? I've been holding off doing this in yelp because I can't think of a good way to go about it. Maybe adding code to check while running is the best way. And maybe I'm just rambling on and should be quiet. No, you're making sense to me, at least. We've got a few migration details for Nautilus that we want to tackle before 2.24. It'd be interesting if we could do this in some kind of desktop-wide way, but even if that kind of solution is beyond us, at least we could get a good consensus of the best way to do it before moving forward. However, I disagree that adding code is the way to go here. Not only for the overhead, but for maintenance reasons. Nautilus has taught me that this kind of code tends to stay around way after its expiration date. So we probably should script it, and just use the new locations in the code from then on. I'm just not sure of what the best way to provide said script would be (either dump it in the repo, document it in README-Migration and tell distros to package it for upgrades, or if there's some kind of GNOME-wide way we could/should do this?) I also think that developer's inconvenience isn't that bad, since we will be the first ones to migrate and we have the skill-set to troubleshoot any problems we have along the way. The worry for me is user inconvenience as any change in behavior can be really disruptive. I can't tell you how many times I've already had to explain the new trash location to users. Getting as much of that pain over with as soon as possible is going to be good for everyone. And it'll be better if it all happens at the same time, so that it's easier to explain to people. There's also a mostly empty GnomeGoals page for tracking (at least part of) this progress: http://live.gnome.org/GnomeGoals/XDGConfigFolders -A. Walton Don [1] see http://bugzilla.gnome.org/show_bug.cgi?id=522849 for the yelp bug, and http://bugzilla.gnome.org/show_bug.cgi?id=523057 for the tracking bug across the whole of GNOME. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
2008/6/1 Philip Withnall [EMAIL PROTECTED]: On Sun, 2008-06-01 at 20:20 +0100, Don Scorgie wrote: This has been brought up for a number of projects in GNOME [1]. I wonder if we could / should reach some consensus on the best way to do this across all modules? I've been holding off doing this in yelp because I can't think of a good way to go about it. I would suggest adding the changes for all the modules to some script which would get run either when you upgrade GNOME, or just once on session start. However, this does have the problem of moving module-specific changes out of the module and into an aggregate area, which may or may not work. This will lead to all kind of problems if you don't upgrade all the packages or are just building some stuff from SVN Best solution is my opinion the suggestion of Patryk 1) Check new location for conf file 2) If not found copy from old location to new location (do not move the file because their might be an old version of the app on the machine) 3) Put in the NEWS file that new location is used. This has a couple of advantages. 1) No performance overhead 2) Old apps don't break In the end the old files will just dissappear because users reinstall their OS or just remove the file if they have read the NEWS file People who don't know the reason why migration to ~/.config should read http://live.gnome.org/GnomeGoals/XDGConfigFolders Can this goal be promoted to an official GNOME goal? Jaap ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Changing bookmarks file location
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patryk Zawadzki wrote: | It could only do the check if configuration is not found in the | expected (new) place. What Patryk said. I'm sure you do check if the configuration files exists every time you fire up your up anyway. Cheers, - -- Og B. Maciel [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhDCmIACgkQUDEm1NXPwgJ30ACaA2WDgXfI7wUxzrneXE3Z+lHS 8FUAn2jo7KUeiv1qmxF5IGVPuCOhFJyz =xd4+ -END PGP SIGNATURE- ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
