1 |
On 4 July 2012 02:16, Michał Górny <mgorny@g.o> wrote: |
2 |
> a) || ( a b ) should be || ( b a ), to actually state what perl does, |
3 |
|
4 |
I don't really see how that would help much, if anything, I get the |
5 |
impression that would |
6 |
|
7 |
1) needlessly install "b" even when it could be satisfied by a instead |
8 |
( ie: before both a & b are installed ) |
9 |
2) be more inclined to keep a than it currently does |
10 |
3) Probably not help in the situation I had above with |
11 |
|
12 |
=perl-core/Module-Metadata-1.0.6 ( stable , 1.0.9 is masked by ~ still ) |
13 |
=virtual/perl-Module-Metadata-1.0.9 ( --autounmasked from ~ ) |
14 |
=dev-lang/perl-5.16.0 ( --autounmasked from ~ ) |
15 |
|
16 |
|
17 |
As after installing perl-5.16.0, the || ( ) is again satisfied, |
18 |
rending the system somewhat broken, but having to wait for --depclean |
19 |
before it comes right. |
20 |
|
21 |
But I'm possibly wrong somewhere, I may have fundamentally |
22 |
misunderstood how || ( ) works. |
23 |
|
24 |
On 4 July 2012 02:16, Michał Górny <mgorny@g.o> wrote: |
25 |
> b) perl should be modified to work like our deps specify. |
26 |
|
27 |
That's probably the most difficult task of all, I think you'd have to |
28 |
shred modules out of perl and hand package them into perl-core/ |
29 |
packages for that, and then never install them as part of perl, |
30 |
despite the fact some of perl won't even build without some of those |
31 |
modules in its tree ( so you have to remove them during install ), and |
32 |
thats the start of all sorts of fun bootstrapping things I wont touch |
33 |
dipped head-to-toe in antiseptic. |
34 |
|
35 |
|
36 |
|
37 |
|
38 |
-- |
39 |
Kent |
40 |
|
41 |
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, |
42 |
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" |
43 |
|
44 |
http://kent-fredric.fox.geek.nz |