From: Dan Armak <danarmak@gentoo.org>
To: desktop@cvs.gentoo.org
Cc: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] Practical suggestion on moving kde/gnome packages
Date: Thu Aug 16 11:00:02 2001 [thread overview]
Message-ID: <01081620004401.00653@desktop.dan.net> (raw)
In-Reply-To: <997924792.368.4.camel@zoidberg>
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
next parent reply other threads:[~2001-08-16 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Dan Armak [this message]
2001-08-16 14:01 ` [gentoo-dev] Re: [desktop] Practical suggestion on moving kde/gnome packages Dan Armak
2001-08-16 15:14 ` Dan Armak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01081620004401.00653@desktop.dan.net \
--to=danarmak@gentoo.org \
--cc=desktop@cvs.gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox