* [gentoo-dev] Practical suggestion on moving kde/gnome packages [not found] ` <997924792.368.4.camel@zoidberg> @ 2001-08-16 11:00 ` Dan Armak 2001-08-16 14:01 ` [gentoo-dev] Re: [desktop] " Dan Armak 0 siblings, 1 reply; 3+ messages in thread From: Dan Armak @ 2001-08-16 11:00 UTC (permalink / raw To: desktop; +Cc: gentoo-dev Hi all, Intro: Hallski and I are searching for a way to implement moving the kde/gnome packages to their new locations, I've got a script to update /var/db/pkg with the new location. We ned a way to get all users to run it. First practical suggestion: Take all ebuilds involved, i.e. kde, gnome, and everyhting that depends on them. Make them run the script before taking any other action, before the DEPEND statements. (The scripts are sourced, right? Everything outside the functions will run first.) Notes: 1. Test on developers first. Run script only if MAINTAINER=yes. 2. Store setting somewhere that the script has already been run, and don't run it again. On the other hand, the script does nothing if you run it a second time (but it takes half a second of processor time), and it's safer to always run it for a time. 3. When will we remove the script from the ebuilds? 4. When we remove the copies of the ebuilds from the old locations? 5. How will this integrate into the job system, in case the system appears before we stop using the script? (That's a philosophical question not a practical one). Hallski, hope you're reading this - I'll try to catch you later on cvs too. -- Dan Armak Gentoo Linux Developer, Desktop Team Matan, Israel ^ permalink raw reply [flat|nested] 3+ messages in thread
* [gentoo-dev] Re: [desktop] Practical suggestion on moving kde/gnome packages 2001-08-16 11:00 ` [gentoo-dev] Practical suggestion on moving kde/gnome packages Dan Armak @ 2001-08-16 14:01 ` Dan Armak 2001-08-16 15:14 ` Dan Armak 0 siblings, 1 reply; 3+ messages in thread From: Dan Armak @ 2001-08-16 14:01 UTC (permalink / raw To: desktop; +Cc: gentoo-dev Additional explanation: above method is the only one that answers to the requirment that the script must run automatically after emerge rsync on every user's computer, because we have no way of telling the user to run it himself. (That's why we wanted a job system in the first place.) The other solution would be to make emerge execute the script when run. This has the benefits of a centralized approach, but the users need to be told to remerge sys-apps/portage, somehow, which is an egg-and-chicken problem. Hope we can solve this soon, -- Dan Armak Gentoo Linux Developer, Desktop Team Matan, Israel ^ permalink raw reply [flat|nested] 3+ messages in thread
* [gentoo-dev] Re: [desktop] Practical suggestion on moving kde/gnome packages 2001-08-16 14:01 ` [gentoo-dev] Re: [desktop] " Dan Armak @ 2001-08-16 15:14 ` Dan Armak 0 siblings, 0 replies; 3+ messages in thread From: Dan Armak @ 2001-08-16 15:14 UTC (permalink / raw To: desktop; +Cc: gentoo-dev Another idea: when the operation launches (in any form), there should be an announcement with a link to explanations on gentoo-dev and on the gentoo.org newspage. -- Dan Armak Gentoo Linux Developer, Desktop Team Matan, Israel ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-08-16 21:13 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <01081515245901.00655@desktop.dan.net> [not found] ` <01081520310503.24777@desktop.dan.net> [not found] ` <997924792.368.4.camel@zoidberg> 2001-08-16 11:00 ` [gentoo-dev] Practical suggestion on moving kde/gnome packages Dan Armak 2001-08-16 14:01 ` [gentoo-dev] Re: [desktop] " Dan Armak 2001-08-16 15:14 ` Dan Armak
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox