From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ${PORTDIR}/profiles/package.use
Date: Fri, 21 Oct 2005 08:44:11 +0200 [thread overview]
Message-ID: <20051021064411.GB13083@gentoo.org> (raw)
In-Reply-To: <200510202256.57881.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
On Thu, Oct 20, 2005 at 10:56:57PM -0400, Mike Frysinger wrote:
> On Thursday 20 October 2005 10:49 pm, Dan Meltzer wrote:
> > Why single out this one? ones system will not break irreperbly
> > without a cxx compiler, it'll just cause a another recompile to get it
> > to work after breakage if the person is using -* (which has already
> > been said to be hackish and ill-advised, so doom on them!
>
> it will actually
>
> if you build gcc w/out C++ support that means no libstdc++
>
> no libstdc++ means python on most boxes is now broken
>
> no python means no emerge
>
> how exactly are you going to re-emerge gcc then ? oh, you cant ...
> -mike
It could be handled the same way busybox handles USE=make-symlinks:
simply abort unless the user makes it really clear via an extra variable
that he knows what he's doing. A nocxx flag isn't necessary to protect
users.
: >>> Test phase [not enabled]: sys-apps/busybox-1.01
:
: >>> Install busybox-1.01 into /var/tmp/portage/busybox-1.01/image/ category sys-apps
: * setting USE=make-symlinks and emerging to / is very dangerous.
: * it WILL overwrite lots of system programs like: ls bash awk grep (bug 60805 for full list).
: * If you are creating a binary only and not merging this is probably ok.
: * set env VERY_BRAVE_OR_VERY_DUMB=yes if this is realy what you want.
:
: !!! ERROR: sys-apps/busybox-1.01 failed.
: !!! Function src_install, Line 176, Exitcode 0
: !!! silly options will destroy your system
: !!! If you need support, post the topmost build error, NOT this status message.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-21 6:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 21:47 [gentoo-dev] ${PORTDIR}/profiles/package.use Petteri Räty
2005-10-20 22:00 ` Dan Armak
2005-10-20 22:11 ` Petteri Räty
2005-10-21 1:46 ` Mike Frysinger
2005-10-21 2:03 ` Alec Warner
2005-10-21 2:16 ` Mike Frysinger
2005-10-21 2:19 ` Dave Nebinger
2005-10-21 2:26 ` Mike Frysinger
2005-10-21 2:34 ` Spider (D.m.D. Lj.)
2005-10-21 2:43 ` Mike Frysinger
2005-10-21 2:49 ` Dan Meltzer
2005-10-21 2:56 ` Mike Frysinger
2005-10-21 6:44 ` Harald van Dijk [this message]
2005-10-21 13:10 ` Mike Frysinger
2005-10-21 17:23 ` Michiel de Bruijne
2005-10-21 23:58 ` Mike Frysinger
2005-10-21 11:37 ` [gentoo-dev] ${PORTDIR}/profiles/package.use Duncan
2005-10-21 11:51 ` Ciaran McCreesh
2005-10-23 12:24 ` Re[2]: " Jakub Moc
2005-10-21 17:53 ` Petteri Räty
2005-10-21 2:47 ` [gentoo-dev] ${PORTDIR}/profiles/package.use Alec Warner
2005-10-21 2:55 ` Mike Frysinger
2005-10-21 3:09 ` Dave Nebinger
2005-10-21 3:20 ` Dave Nebinger
2005-10-21 3:43 ` Chris Lee
2005-10-21 9:56 ` Marius Mauch
2005-10-21 11:08 ` Petteri Räty
2005-10-21 14:49 ` Marius Mauch
2005-10-21 15:58 ` Daniel Ostrow
2005-10-21 13:13 ` Mike Frysinger
2005-10-22 9:04 ` Petteri Räty
2005-10-22 9:05 ` Petteri Räty
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=20051021064411.GB13083@gentoo.org \
--to=truedfx@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