[Bug 481536] Review Request: enano - Enano CMS, a php-based modular content management system

[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.


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





--- Comment #9 from David Nalley <david at gnsa.us>  2009-05-26 11:47:41 EDT ---
So I talked to a FPC member and the gist of the conversation is: 

These libraries have to go.  In order of preference:

1) Upstream the patches, eg have upstream (enano) commit their changes to the
library project in question. 
2) Fork from upstream. eg, have enano essentially fork the packages and begin
maintaining a fork of each of those libraries (which will then need to be
packaged)
3) Other solution....  I don't know what other solution exists to be honest,
though I imagine that there exists some novel solution. 

Unfortunately a lot of this seems very much out of your hands and in the hands
of upstream. Let me know how I can help you proceed.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.