On Mon, 12 Nov 2007 13:26:46 +0100
Marijn Schouten (hkBst) [EMAIL PROTECTED] wrote:
What exactly is the difference between this valid situation and the
previous invalid one?
It's basically down to whether pkg_setup has to be run with the same
system state as pkg_preinst / pkg_postinst. If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
On Fri, 9 Nov 2007 22:40:08 +
Ciaran McCreesh [EMAIL PROTECTED] wrote:
Is the following set sufficient? Is the following set the least
restrictive correct solution?
... to explain the implications of these...
Say
On Monday 12 of November 2007 13:26:46 Marijn Schouten (hkBst) wrote:
What exactly is the difference between this valid situation and the
previous invalid one?
between | | are things that can be done in parallel.
invalid:
a_pkg_setup b_pkg_setup a_build b_build | a_merge | b_merge
valid:
On Mon, Nov 12, 2007 at 01:26:46PM +0100, Marijn Schouten (hkBst) wrote:
Ciaran McCreesh wrote:
On Fri, 9 Nov 2007 22:40:08 +
Ciaran McCreesh [EMAIL PROTECTED] wrote:
Is the following set sufficient? Is the following set the least
restrictive correct solution?
... to explain the
On Fri, 9 Nov 2007 22:40:08 +
Ciaran McCreesh [EMAIL PROTECTED] wrote:
Is the following set sufficient? Is the following set the least
restrictive correct solution?
... to explain the implications of these...
Say we have packages a, b and c, and none of them have any
dependencies. One
What specifically are the phase invariancy and exclusivity requirements
for ebuilds? Currently PMS doesn't have anything to say about this;
clearly it needs to, since existing ebuilds fairly obviously do have
invariancy and exclusivity requirements.
Note that we're only discussing package manager
