From: Dave Nellans <dnellans@cs.utah.edu>
To: Georgi Georgiev <chutz-dated-1060403692.d79fb4587a07@gg3.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] dummy-sources
Date: 25 Jul 2003 23:39:26 -0600 [thread overview]
Message-ID: <1059197965.32662.29.camel@malfus> (raw)
In-Reply-To: <20030726043448.GA1910%chutz@gg3.net>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
ok, that makes more sense now.
what happened to the suggested solution a few emails ago that in this
case the user should just create their own dummy-sources ebuild of
sufficiently high version and keep it in their local overlay tree?
while this is a legitimate grip of the portage system because it is not
convienent to do this, portage "does" have what i see as a solution, its
just not as convenient as one might want it.
so the question is should portage change to make this easier as per
suggested below. i vote no because if we make a "dummy-XXX" then one
could argue that every package should have a dummy-* build for it. in
the long run i'm sure some user will write the dummy-* build for most
packagse in portage and that would significantly grow (everyone agree?)
the size of the tree as a solution that is for convenience.
dave
On Fri, 2003-07-25 at 22:34, Georgi Georgiev wrote:
> On 25/07/2003 at 21:26:31(-0600), Dave Nellans used 1.4K just to say:
> > I agree with brad, I proposed the emerge inject solution was how this
> > problem was intended to be dealt with but couldn't quite make sense of
> > the reason this didn't work from the thread.
> >
> > could someone possibly clearly give the arguement against injecting
> > again for us slow people?
>
> The problems as I get them, are:
>
> - Injecting the sources, would work, but it would require reinjecting every
> newer version, or else an "emerge -u" would upgrade the version for us, when
> for example upgrading a package that depends on the sources.
>
> - Injecting a sufficiently big, non-existing version would not work, because an
> emerge -u (even -U) would downgrade the version to the highest available,
> i.e. it would install a version.
>
> It seems that having a dummy-sources whose version does not change would solve
> this problem.
--
Dave Nellans
http://lucy.wox.org/~dnellans/
dnellans@cs.utah.edu
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-26 5:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 14:43 [gentoo-dev] dummy-sources Florian Huber
2003-07-24 14:59 ` Dave Nellans
2003-07-24 15:13 ` Thomas de Grenier de Latour
2003-07-24 15:24 ` Dave Nellans
2003-07-25 0:08 ` Thomas de Grenier de Latour
2003-07-24 15:15 ` Florian Huber
2003-07-24 15:37 ` Georgi Georgiev
2003-07-26 2:01 ` Mike Frysinger
2003-07-26 2:22 ` Brad Laue
2003-07-26 3:26 ` Dave Nellans
2003-07-26 4:34 ` Georgi Georgiev
2003-07-26 5:39 ` Dave Nellans [this message]
2003-07-26 6:20 ` Seemant Kulleen
2003-07-26 7:46 ` Jason A. Mobarak
2003-07-26 8:18 ` Thomas de Grenier de Latour
2003-07-27 14:55 ` Jay Pfeifer
2003-07-25 0:29 ` George Shapovalov
2003-07-26 8:22 ` Bartosch Pixa
2003-07-27 17:01 ` Florian Huber
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=1059197965.32662.29.camel@malfus \
--to=dnellans@cs.utah.edu \
--cc=chutz-dated-1060403692.d79fb4587a07@gg3.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