[Bug 2366] Review request: mythweb

[RPM Fusion Bugzilla]

https://bugzilla.rpmfusion.org/show_bug.cgi?id=2366

--- Comment #13 from Richard <hobbes1069 at gmail.com> 2012-07-03 20:47:25 CEST ---
(In reply to comment #12)
> (In reply to comment #11)
> > Is there anything stopping this from completing now or are there additional
> > questions or concerns?
> > 
> > See the new "See Also" bug for additional rational.
> 
> I still lack to see any strong rational to do so.
> In others words my previous question still stand:
> - Does MythTV upstream plans to remove the mythweb content from theirs VCS ?

No


> - Is mythweb still part of the upstream release or not ?

Yes, although in a separate repository, as previously mentioned.


> - Do you plan to make a mythweb update that will mismatch with MythTV ?

Not sure what you mean here, but it seemed unnecessary to force people to
update their mythweb packages because of an update in mythtv when there were no
changes in the mythweb repository. 


> In the worst case, you could package a mythweb version that will be
> incompatible with MythTV, because it will be fetched from a different branch.

The development is already disconnected... In either case of globing this into
the mythtv package or releasing separately will not cause *or* prevent this
from occurring.

Mythweb is, as far as I know, not dependent on a particular database schema as
it uses the php bindings to communicate with the backend.

I always check the git log of both prior to pushing an update.


> FYI, you can still tag the sub-package as noarch, this will work from our
> infra.

I was wondering about that. I assume this was not always the case? I noticed a
number of comments Jarod left if the spec saying he wished he could mark them
as noarch but did not say why he couldn't.

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