1 |
Enrico Weigelt a écrit : |
2 |
> * Luca Barbato <lu_zero@g.o> schrieb: |
3 |
>> Enrico Weigelt wrote: |
4 |
>>> My suggestion: make those language bindings being separate |
5 |
>>> packages. So, other packages can depend on them directly, |
6 |
>>> instead of the current, build-breaking hack. |
7 |
>>> |
8 |
>>> I'm not advocating gentoo should do this step alone, but |
9 |
>>> instead join in the upstream and solve it there. |
10 |
>> The issue is upstream related, we can workaround it using a way to |
11 |
>> express that requirement (usedeps, checks in pkg_setup, whatever), |
12 |
>> obviously trying to cooperate with upstream in order to get the optional |
13 |
>> bindings build w/out the main program would make our life simpler and |
14 |
>> probably their as well. |
15 |
>> |
16 |
>> Partial builds are quite a problem since they are anything but reliable. |
17 |
> |
18 |
> ACK. These are just hacks to work around upstream's design |
19 |
> problems. For me, working much embedded environments, those |
20 |
> hacks are not an option, since builds MUST be reliable |
21 |
> (the packages MUST work IMMEDIATELY after deployment, since |
22 |
> there is no chance for doing things like revdep-rebuild). |
23 |
> |
24 |
> My vote is: declaring guidelines (or better: constraints) for |
25 |
> clean builds and then working directly within the upstream to |
26 |
> get it on the road. |
27 |
|
28 |
Best example on how to do that is gstreamer. All the plugins come in 3 |
29 |
tarballs but each can be built individually. Really clean. |
30 |
|
31 |
> If the upstream really blocks it, do a |
32 |
> fork / maintain a patchline (like OSS-QM project does). |
33 |
> |
34 |
> I'm already doing so with several packages. |
35 |
|
36 |
I've seen you talk about that project before but I don't feel |
37 |
comfortable going down that road. We want to work with upstream and let |
38 |
them know what our needs are. Maintaining patches is a lot of work and |
39 |
forking is even more work. Even though I'm still a relatively young |
40 |
Gentoo dev (only been here for 1.5 years), I have yet to see upstream |
41 |
projects reject build patches that make our lives easier. |
42 |
|
43 |
Cheers, |
44 |
|
45 |
Rémi |
46 |
-- |
47 |
gentoo-dev@l.g.o mailing list |