Re: [gentoo-dev] dummy-sources

[Thomas de Grenier de Latour <degrenier@easyconnect.fr>]

On 24 Jul 2003 09:24:17 -0600
Dave Nellans <dnellans@cs.utah.edu> wrote:

> you explicitly inject some version but as long as you never add it to
> your world file it won't be updated unless required by something that
> depends on it.  And in that case you are going to want to update
> anyways, and you can just inject it again and build your own source
> that satisfies the new dependancies.

If pkgA depends on virtual/foo, and virtual/foo is instanciated by pkgB,
then an "emerge -u pkgA" will try to update pkgB, whether it has been
really emerged  or injected. Hence, if pkgA is a world package, an
"emerge -u world" can build an update of your injected package, and in
the linux-source example, that's not what we want.

Another issue is that the inject of pkgB to instanciate virtual/foo will
only does what we expect if pkgB is the default package associated to
virtual/foo in your profile "virtuals" dictionnary. This is because
ebuilds are not parsed by inject (hence PROVIDE is ignored, and nothing
gets added to your edb/virtuals). For instance, because gentoo-sources
is the default value for virtual/linux-sources, if you inject
vanilla-sources and then emerge something depending on
virtual/linux-sources, gentoo-sources will be emerged.

That's why I was suggesting the possibility to inject virtual packages,
I think it would really be more clear when what the user wants is to
satisfy the dependencies on this virtual packages. 

But dummy ebuilds are also an acceptable (and easier) way to do it. We
can imagine a dummy category for such stub ebuilds, one for each virtual
packages, so that "emerge dummy/linux-sources" would definitly
instanciate virtual/linux-sources, because there would be no updates in
this category.

-- 
TGL.

--
gentoo-dev@gentoo.org mailing list