public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chad Huneycutt <chadh@gentoo.org>
To: gentoo-dev@gentoo.org
Cc: gentoo-core@gentoo.org
Subject: Re: [gentoo-dev] Release/Stable/Dev
Date: 20 Nov 2002 11:42:44 -0500	[thread overview]
Message-ID: <1037810564.13315.12.camel@rebo> (raw)
In-Reply-To: <200211201633.36330.tdickenson@devmail.geminidataloggers.co.uk>

On Wed, 2002-11-20 at 11:33, Toby Dickenson wrote:
> On Wednesday 20 November 2002 4:21 pm, Chad Huneycutt wrote:
> 
> > Use profiles for this.  The process would go something like this:
> >
> > 1. Install Gentoo on your dev box
> > 2. Tweak until the stability is where you want it (i.e., find stable
> > versions of software, make patches -- and submit them to bugzilla, and
> > place any outside ebuilds in /usr/local/portage or whatever and set
> > PORTAGE_OVERLAY -- or whatever the var is)
> > 3. Once you have the packages from portage like you want them, create a
> > new profile:
> > # cd /usr/portage/profiles
> > # cp -r your_current_profile my_stable_profile
> > # mv my_stable_profile /usr/local/portage/profiles
> > # rm /etc/make.profile
> > # ln -s /usr/local/portage/profiles/my_stable_profile /etc/make.profile
> > # cd /usr/local/portage/profiles/my_stable_profile
> > # echo "all_my_package-revisions" > packages
> >
> > The packages file is well commented, but basically you can use it to
> > "pin" the versions of all your packages (or just the ones that matter).
> > 4. Now you should be able to use that profile directory as
> > /etc/make.profile on all your systems.
> 
> Im sure that wouldnt work. Your profile would refer to your chosen version, 
> but that doesnt help when the ebuild (and other files) for that version is 
> removed from portage.
> 
> I agree with you that this *should* work. That means that old revisions would 
> never be removed from portage.
> 
> But they are, so it doesnt :-(

That is a totally different problem, though, which could easily be
remedied on the user side.  I agree that it is a problem, though.  I
offered a scheme for automating ebuild removal of the portage tree some
time back on -core, but it fell on mostly deaf ears.  I personally
almost never remove old ebuilds unless they are ancient or broken.  We
are certainly aware of this issue, though; the alternative arch devs get
bitten all the time because someone will update an ebuild, mask it on
alternative arches, and then delete the old ebuild, thus leaving no
unmasked versions for the alt arch.

-- 
Chad Huneycutt
chadh@gentoo.org


--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2002-11-20 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20 14:43 [gentoo-dev] Release/Stable/Dev Riyad Kalla
2002-11-20 15:20 ` Mark Constable
2002-11-20 16:00 ` Toby Dickenson
2002-11-20 16:21 ` Chad Huneycutt
2002-11-20 16:33   ` Toby Dickenson
2002-11-20 16:42     ` Chad Huneycutt [this message]

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=1037810564.13315.12.camel@rebo \
    --to=chadh@gentoo.org \
    --cc=gentoo-core@gentoo.org \
    --cc=gentoo-dev@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