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: jeta - Horde SSH Java Applet https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221004 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] OtherBugsDependingO|163776 |163778 nThis| | ------- Additional Comments From [EMAIL PROTECTED] 2007-01-28 02:14 EST ------- I promise not to take so long with this one. First off, the release should be "0.1.rc2%{?dist}"; you can append ".1" once the package is in the repo and you need to tweak a non-development branch without rebuilding any of the newer branches. About registry.php, what stops us from just shipping the horde package with jeta enabled in registry.php? I don't think it's worth it to try and change it; that can get rather complicated and it's best to avoid that kind of thing unless it's really trivial to do, and even then it's still usually better to just leave it up to the admin. I guess the fundamental question is why upstream doesn't enable jeta by default. I suppose it's because it hasn't been released yet. Or do things break if "status" is set to "active" when the application isn't installed? -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list [email protected] http://www.redhat.com/mailman/listinfo/fedora-package-review
