[Bug 234490] Review Request: VDrift - VDrift is a cross-platform, open source driving/drift racing simulation

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: VDrift - VDrift is a cross-platform, open source driving/drift racing simulation


https://bugzilla.redhat.com/show_bug.cgi?id=234490





------- Additional Comments From j.w.r.degoede at hhs.nl  2008-02-13 03:18 EST -------
(In reply to comment #60)
> Thanks for the information, Chris, and thanks to you and your team for the
> effort between 3-23 and 12-26.  
> 
> Fedora folken, should we bundle bullet into vdrift, or possibly package a
> pristine bullet with a bullet-vdrift subpackage with the vdrift patches applied,
> so that vdrift can BT bullet-vdrift-devel and other packages could BR
bullet-devel?
> 
> Am I crazy, or is this a good idea?

It all depends. Do the patches change ABI / API, are they heading upstream, etc.
I've gone this way before, that is I've packed a bundled patched library
separately before including the patches in the separate build, there this could
be done because the patches we're only bugfixes, so no ABI / API changes (note
that additions are fine, changes are the problem). However since that lib's
upstream was dead, the app including the library was effectively maintaining it
for their own uses and each new release of the application I had todo a new
release of the lib, so I eventually stopped doing this.

So I say since its modified (for good reasons), just use the included version.

Chris (Guirl) have your bullet patches been submitted upstream? Are there any
plans to get them upstream and eventually switch to using a pristine bullet again?


-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.