public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Jodok Batlogg <batlogg@solution2u.net>
Cc: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] custom ebuild: AUTOCLEAN unmerges slotted version
Date: 11 Aug 2003 03:14:18 +0200	[thread overview]
Message-ID: <1060564458.11013.61.camel@nosferatu.lan> (raw)
In-Reply-To: <1060564230.11013.59.camel@nosferatu.lan>

[-- Attachment #1: Type: text/plain, Size: 971 bytes --]

On Mon, 2003-08-11 at 03:10, Martin Schlemmer wrote:
> On Mon, 2003-08-11 at 00:55, Jodok Batlogg wrote:
> > hi,
> > 
> > i'm preparing an ebuild for plone1.1 (zope based CMS). I took the existing
> > 1.04-ebuild and added SLOT="1.0" and SLOT="1.1".
> > 
> > the ebuilds work fine, but although i specified two different slots
> > AUTOCLEAN always unmerges the lower version. I have no idea why.
> > 
> > i've attached the two ebuilds. is there sth. obvious i'm missing? i can't
> > find the reason.
> > 
> 
> You need to remerge the old version with the updated SLOT first.
> This will tipically be one of those things that update goes as
> follows:
> 
> 1) add new revision of older version with new SLOT
> 2) wait a few weeks (days?) for it to propagate
> 3) add the new version with diff SLOT
> 

BTW:  why was it never SLOTted ?


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-11  1:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10 22:55 [gentoo-dev] custom ebuild: AUTOCLEAN unmerges slotted version Jodok Batlogg
2003-08-11  1:10 ` Martin Schlemmer
2003-08-11  1:14   ` Martin Schlemmer [this message]
2003-08-11  6:32     ` [gentoo-dev] " Jodok Batlogg
2003-08-11 21:26       ` Martin Schlemmer
2003-08-11  6:36   ` Jodok Batlogg
2003-08-11 21:28     ` Martin Schlemmer

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=1060564458.11013.61.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=batlogg@solution2u.net \
    --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