public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Variancy?
Date: Sun, 5 Dec 2010 23:49:19 +0100	[thread overview]
Message-ID: <19708.5871.249425.932759@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20101205222116.310262cc@snowcone>

>>>>> On Sun, 5 Dec 2010, Ciaran McCreesh wrote:

>> >>  - Calling pkg_pretend.

> pkg_pretend's sandboxed and isn't supposed to be modifying /, so
> that should be ok.

Then pkg_pretend should be mentioned as a further exception (unless we
decide that the whole section should be removed):

--- ebuild-env-invariancy.tex~
+++ ebuild-env-invariancy.tex
@@ -7,8 +7,8 @@
 \item Variancy is any package manager action that modifies either
     \t{ROOT} or \t{/} in any way that isn't merely a simple addition of
     something that doesn't alter other packages. This includes any
-    non-default call to any \t{pkg} phase function except \t{pkg\_setup},
-    a merge of any package or an unmerge of any package.
+    non-default call to any \t{pkg} phase function except \t{pkg\_pretend}
+    and \t{pkg\_setup}, a merge of any package or an unmerge of any package.
 \item As an exception, changes to \t{DISTDIR} do not count as variancy.
 \item The \t{pkg\_setup} function may be assumed not to introduce variancy.
     Thus, ebuilds must not perform variant actions in this phase.



  reply	other threads:[~2010-12-05 22:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05 21:55 [gentoo-pms] Variancy? Ulrich Mueller
2010-12-05 22:06 ` Ciaran McCreesh
2010-12-05 22:13   ` Ulrich Mueller
2010-12-05 22:21     ` Ciaran McCreesh
2010-12-05 22:49       ` Ulrich Mueller [this message]
2010-12-05 22:53         ` Ciaran McCreesh

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=19708.5871.249425.932759@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-pms@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