1 |
On 09/23/2013 05:48 AM, Michał Górny wrote: |
2 |
> Dnia 2013-09-22, o godz. 17:17:53 |
3 |
> ""Paweł Hajdan, Jr."" <phajdan.jr@g.o> napisał(a): |
4 |
> |
5 |
>> I'd like maintainers of all packages depending on dev-lang/v8 to make |
6 |
>> their packages use bundled v8 copy instead (I can file bugs for that, |
7 |
>> let's discuss here whether it should be done). |
8 |
>> |
9 |
>> For now V8 upstream gives no guarantees about API/ABI stability and |
10 |
>> actually breaks it very often |
11 |
>> (<http://upstream-tracker.org/versions/v8.html>). Having a shared |
12 |
>> library so closely tied to packages (which results in frustrating |
13 |
>> blockers, since v8 is updated often and chromium is synchronized with |
14 |
>> that) is not really much different from everyone bundling the library. |
15 |
>> I'd like that to improve, but for now it's time for a pragmatic solution |
16 |
>> to this IMHO. |
17 |
> |
18 |
> If this trend continues, I think we should work on some technical way |
19 |
> of tracking bundled libraries, e.g. for security issues. Like ebuilds |
20 |
> listing the corresponding Gentoo packages, like: |
21 |
> |
22 |
> QA_BUNDLES="dev-foo/bar-1.2.3" |
23 |
> |
24 |
|
25 |
One idea is to make a new bundled-lib category for virtual packages and |
26 |
then make virtual package for each library that is bundled. |