public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Brian Harring <ferringb@gmail.com>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pkg_pretend USE validation and VALID_USE alternative
Date: Thu, 1 Apr 2010 12:50:22 +0100	[thread overview]
Message-ID: <20100401125022.5976d240@snowcone> (raw)
In-Reply-To: <20100401113836.GN11663@hrair>

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

On Thu, 1 Apr 2010 04:38:36 -0700
Brian Harring <ferringb@gmail.com> wrote:
> > But if the kernel sources symlink is changed by installing new
> > kernel sources, there won't be a valid .config in the new directory
> > anyway.
> 
> Oddly enough, I actually have an ebuild that directly contradicts 
> that- used for managing my sources w/in kvms.

Your own personal ebuilds are an exception that don't apply to
everyone else. For ebuilds using kernel-2.eclass with USE=symlink, a
missing .config is exactly what happens.

> > Thus, pkg_pretend doesn't introduce any new breakage.
> 
> Regardless of my own usage, ironically you just inadvertantly pointed 
> out a whole class of false negatives pkg_pretend has.
> 
> Specifically, 
> 
> 1) starting w/ a configured kernel at /usr/src/linux
> 2) merging a version of aufs2 requiring new kernel sources
> 3) emerge runs pkg_pretend.  aufs2 does it's checks w/in pkg_pretend, 
> sees the old configured kernel and thinks things are fine
> 4) new kernel sources get merged.  /usr/src/linux is no lnger a 
> configured kernel.
> 5) aufs2 blows up during its build due to an unconfigured 
> kernel.
> 
> Since I'm in the mood for a Scooby Doo quote, "wraut-wroh".

This isn't a breakage that's introduced by pkg_pretend. It's a breakage
that's already there.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-04-01 11:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  9:20 [gentoo-dev] pkg_pretend USE validation and VALID_USE alternative Brian Harring
2010-03-31  9:48 ` [gentoo-dev] Re: [gentoo-council] " Ulrich Mueller
2010-03-31 10:46   ` Brian Harring
2010-03-31 11:04     ` [gentoo-dev] " Ulrich Mueller
2010-03-31 11:11       ` Brian Harring
2010-03-31 15:38       ` "Paweł Hajdan, Jr."
2010-03-31 11:18     ` [gentoo-dev] Re: [gentoo-council] " Piotr Jaroszyński
2010-04-01 20:44     ` Róbert Čerňanský
2010-04-01 21:51       ` Zac Medico
     [not found] ` <201003312316.23806.ali_bush@gentoo.org>
2010-03-31 10:57   ` Brian Harring
2010-03-31 17:49 ` [gentoo-dev] " Alex Alexander
2010-03-31 19:46   ` Brian Harring
2010-03-31 19:56     ` Ciaran McCreesh
2010-04-01  7:31       ` Brian Harring
2010-04-01  7:41         ` Ciaran McCreesh
2010-04-01  7:56           ` Brian Harring
2010-04-01 10:10             ` Gilles Dartiguelongue
2010-04-01 10:18               ` Brian Harring
2010-04-01 10:42                 ` Gilles Dartiguelongue
2010-04-01 10:59                   ` Brian Harring
2010-04-01 11:23                     ` Ciaran McCreesh
2010-04-01 11:38                       ` Brian Harring
2010-04-01 11:50                         ` Ciaran McCreesh [this message]
2010-04-01 10:49             ` Ciaran McCreesh
2010-04-01 11:18               ` Brian Harring
2010-04-01 11:44                 ` Ciaran McCreesh
2010-04-01 17:04                 ` David Leverton
2010-04-01 18:39                   ` Dror Levin
2010-04-01 18:55                     ` Ciaran McCreesh
2010-04-02 22:36                     ` David Leverton

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=20100401125022.5976d240@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=ferringb@gmail.com \
    --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