| |||||||||||||
Applications and bundled librariesApplications and bundled librariesPosted Mar 17, 2010 20:45 UTC (Wed) by jspaleta (subscriber, #50639)In reply to: Applications and bundled libraries by agl Parent article: Applications and bundled libraries
Are you keeping a detailed accounting of individual patches such that its easy to see which patches have been submitted to upstream and then whether each patch has been rejected/approved?
Can things be engineered such that functionality from rejected/yet-to-be-approved patches to upstream can be disabled cleanly in rebuilds? You've alluded that his is the case for nss can that also be the case for sqlite and others where there is an active upstream?
For libjingle.. if the upstream project is verifiably dead... why doesn't google spin up their libjingle as a separate project for distributors to pull releases from.
-jef
(Log in to post comments)
Applications and bundled libraries Posted Mar 17, 2010 21:38 UTC (Wed) by tzafrir (subscriber, #11501) [Link]
The upstream for libjingle is actually Google.
Applications and bundled libraries Posted Mar 17, 2010 21:41 UTC (Wed) by jspaleta (subscriber, #50639) [Link]
The gods of irony are please. A good omen for the maintainability of chromium. Well played Google... well played.
-jef
Applications and bundled libraries Posted Mar 20, 2010 12:51 UTC (Sat) by man_ls (subscriber, #15091) [Link] It may seem obvious, but I have to ask -- why not revive libjingle and push the patches upstream?
|
|||||||||||||