The Fedora v8 package (chromium has long since abandoned any possibility This means that other than plv8 (which is currently unable to buildĪgainst the current v8 package in Fedora), I do not see any consumers of Simply do security fixes to the master branch, which, combined with theĬode changing violently, makes it very difficult to backport security fixes. Since v8 has no concept of a "stable" release that I can see, they Use that revision, often creating a local fork of v8 from that revision,Īs they are either unwilling or unable to track v8 upstream.Ĥ. Virtually all consumers of v8 (including chromium) take a gitĬheckout (not a specific one, just whatever they decided to code to) and The upstream v8, as they have a history of picking and choosing codeĬhanges (and even applying chromium specific changes locally).ģ. The v8 that is used in chromium is not necessarily compatible with Maintaining any sort of ABI/API consistency between releases.Ģ. The v8 upstream is entirely disinterested in the concept of Is useful software, the following facts are also true:ġ. Since that point, it has become clear that while v8 Optimistic about the possibility of separating the useful components I made the original v8 Fedora package many moons ago, when I was more Please join #fedora-admin in or respond to this email to The additional time is for some further tuning if ![]() To convert UTC to your local time, take a look atįinal migration step for new cvs server. ![]() There will be an outage starting at 01:00 UTC, which will last
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |