Paul de Vrieze <[EMAIL PROTECTED]> wrote:
> On Friday 24 February 2006 15:19, Ciaran McCreesh wrote:
[snip]
> > To avoid this, ensure that your packages use versioned SRC_URI
> > component names, and that the name part is something that's
> > reasonably likely to be unique (e.g. includes the packag
On 2/25/06, Mike Myers <[EMAIL PROTECTED]> wrote:
> What do I use if I just want to re-emerge a single package with the same
> useflags? Like if something broke or if I'm using an overlay? Like, if
> I just wanted to reinstall noatun for instance. Is there a way to do
> that without having to ha
John Myers wrote:
On Saturday 25 February 2006 10:33, Mike Myers wrote:
emerge --newuse kde-meta
use also '--deep'.
Also, consider using 'world' as the target
Also, you don't have to unmerge packages before re-merging them.
What do I use if I just want to re-emerge a single package
On Saturday 25 February 2006 10:33, Mike Myers wrote:
> emerge --newuse kde-meta
use also '--deep'.
Also, consider using 'world' as the target
Also, you don't have to unmerge packages before re-merging them.
--
#
# electronerd, the electronerdian from electronerdia
#
pgpT4o3hhtfsQ.pgp
Descripti
Mike Myers schrieb:
> emerge --newuse kde-meta
"emerge -NDu world" is what you are looking for.
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
signature.asc
Description: OpenPGP digital si
Diego 'Flameeyes' Pettenò wrote:
A part you probably mixed a bit the difference between monolithic and split
packages...
On Saturday 25 February 2006 09:32, Mike Myers wrote:
My question is; Is there any better way to do these kinds of things
yet?
man emerge -> look for --newuse
On Friday 24 February 2006 15:19, Ciaran McCreesh wrote:
> Two ways this one can occur.
>
> Way the first: foo-1.0 has a file in SRC_URI called foo.pdf. Then
> foo-1.1 comes along, and has a different foo.pdf.
>
> Way the second: foo-1.0 has a file called examples-1.0.tar.bz2. bar-1.0
> also has a
Hi,
This is an automatically created email message.
http://gentoo.tamperd.net/stable has just been updated with 14485 ebuilds.
The page shows results from a number of tests that are run against the ebuilds.
The tests are:
* if a version has been masked for 30 days or more.
* if an arch was in KE
Jason Stubbs schrieb:
> Open a bug for this please.
Done: http://bugs.gentoo.org/show_bug.cgi?id=124041
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
signature.asc
Description: OpenPGP di
On Saturday 25 February 2006 18:39, Sebastian Bergmann wrote:
> For a while I am experiencing the following portage annoyance:
>
> After an "emerge sync" (for which the metadata/cache update takes about
> ten seconds), the first call to "emerge -NDuvp world" takes between
> five and ten minute
For a while I am experiencing the following portage annoyance:
After an "emerge sync" (for which the metadata/cache update takes about
ten seconds), the first call to "emerge -NDuvp world" takes between
five and ten minutes
emerge -NDuvp world 321.05s user 77.90s system 94% cpu 7:02.77 to
Mike Myers wrote:
> Hello!
>
> Currently, as you all surely already know, KDE is currently handled with
> metapackages or monolithic packages. The metapackages is very
> convenient for a more complete install of KDE, and the monolithic
> packages are better or a more modular install. However, wi
A part you probably mixed a bit the difference between monolithic and split
packages...
On Saturday 25 February 2006 09:32, Mike Myers wrote:
> My question is; Is there any better way to do these kinds of things
> yet?
man emerge -> look for --newuse
--
Diego "Flameeyes" Pettenò - http://dev.g
Hello!
Currently, as you all surely already know, KDE is currently handled with
metapackages or monolithic packages. The metapackages is very
convenient for a more complete install of KDE, and the monolithic
packages are better or a more modular install. However, with the
metapackages, it s
14 matches
Mail list logo
