From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] merging two packages - upgrade path?
Date: Thu, 5 Jun 2008 15:02:31 +0200 [thread overview]
Message-ID: <20080605150231.5494e2ef.genone@gentoo.org> (raw)
In-Reply-To: <18503.53638.884328.573602@a1ihome1.kph.uni-mainz.de>
On Thu, 5 Jun 2008 13:44:06 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>> On Thu, 5 Jun 2008, Matthias Schwarzott wrote:
>
> >> With #1 the user will get a message about the blockers immediately.
> >> With #2 his emerge (maybe of many packages) will needlessly die
> >> when it reaches your package.
>
> > With #1 user will get no message, as neither the user nor the
> > package manager know of the merged package that should be emerged.
>
> So nothing depends on it that would pull in the new package? Now I see
> what your problem is. ;-)
>
> Isn't it possible to package.move -server or -client to the new
> package?
Assuming you're talking about "global updates" commands: Don't use it
for this kind of use case. The "move" command just renames a package in
vdb, and using it for anything that goes beyond a simple relocation in
the tree _will_ result in problems later on (we've been there already).
Marius
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-05 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 10:06 [gentoo-dev] merging two packages - upgrade path? Matthias Schwarzott
2008-06-05 10:41 ` Ulrich Mueller
2008-06-05 11:02 ` Arun Raghavan
2008-06-05 11:13 ` Matthias Schwarzott
2008-06-05 11:36 ` Rémi Cardona
2008-06-07 11:40 ` Matthias Schwarzott
2008-06-05 11:44 ` Ulrich Mueller
2008-06-05 13:02 ` Marius Mauch [this message]
2008-06-09 20:40 ` Enrico Weigelt
2008-06-09 20:51 ` Matthias Schwarzott
2008-06-09 21:22 ` Enrico Weigelt
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=20080605150231.5494e2ef.genone@gentoo.org \
--to=genone@gentoo.org \
--cc=gentoo-dev@lists.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