1 |
On Mon, 24 Sep 2012 14:53:27 -0300 |
2 |
Alexis Ballier <aballier@g.o> wrote: |
3 |
|
4 |
> On Mon, 24 Sep 2012 19:32:14 +0200 |
5 |
> Michał Górny <mgorny@g.o> wrote: |
6 |
> |
7 |
> > On Mon, 24 Sep 2012 12:17:58 -0300 |
8 |
> > Alexis Ballier <aballier@g.o> wrote: |
9 |
> > |
10 |
> > > On Sun, 23 Sep 2012 18:31:25 +0200 |
11 |
> > > Michał Górny <mgorny@g.o> wrote: |
12 |
> > > |
13 |
> > > > On Sun, 23 Sep 2012 12:47:44 -0300 |
14 |
> > > > Alexis Ballier <aballier@g.o> wrote: |
15 |
> > > > |
16 |
> > > > > On Sun, 23 Sep 2012 09:21:20 +0200 |
17 |
> > > > > Michał Górny <mgorny@g.o> wrote: |
18 |
> > > > > |
19 |
> > > > > > On Sat, 22 Sep 2012 21:46:02 -0300 |
20 |
> > > > > > Alexis Ballier <aballier@g.o> wrote: |
21 |
> > > > > > |
22 |
> > > > > > > On Sat, 22 Sep 2012 23:24:46 +0200 |
23 |
> > > > > > > Michał Górny <mgorny@g.o> wrote: |
24 |
> > > > > > > |
25 |
> > > > > > > > It is a simple eclass using autotools out-of-source |
26 |
> > > > > > > > builds to build packages for multiple ABIs when multilib |
27 |
> > > > > > > > is supported. |
28 |
> > > > > > > > |
29 |
> > > > > > > |
30 |
> > > > > > > to some extent, can't you do the same by unpacking twice to |
31 |
> > > > > > > different $S and calling src_prepare/compile/install |
32 |
> > > > > > > instead of their autotools-utils counterpart with tweaked |
33 |
> > > > > > > $S so that it works with almost every ebuild ? |
34 |
> > > > > > |
35 |
> > > > > > That would make this solution inefficient. |
36 |
> > > > > |
37 |
> > > > > Why ? |
38 |
> > > > |
39 |
> > > > Because it introduces unnecessarily copying files around. |
40 |
> > > |
41 |
> > > cp -l ? I can live with that. |
42 |
> > |
43 |
> > Can you guarantee that the build system won't modify any file |
44 |
> > in the source tree? |
45 |
> |
46 |
> You can add it as a requirement. Your eclass implicitly requires it |
47 |
> anyway. |
48 |
> |
49 |
> > So it's back to optimized solution vs bad, universal solution. |
50 |
> |
51 |
> or rather writing multilib support for every package vs. using what |
52 |
> ebuilds already offer you: a common API for building every package. |
53 |
|
54 |
Ebuilds don't offer me anything if I have to rewrite phase functions |
55 |
anyway... |
56 |
|
57 |
-- |
58 |
Best regards, |
59 |
Michał Górny |