Bug 512000
Summary: | rename qca2 -> qca | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rahul Sundaram <sundaram> |
Component: | qca2 | Assignee: | Rex Dieter <rdieter> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | alekcejk, drizt72, gauret, rdieter, smohan, supercyper1, sven |
Target Milestone: | --- | Keywords: | FutureFeature, Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-12-01 15:55:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1164348 | ||
Bug Blocks: | 538278, 709328 |
Description
Rahul Sundaram
2009-07-15 22:06:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I think the consensus it so deprecate qca (v1 for qt3) and rename qca2 (for qt4) to qca for f13. (Probably should've caught this inconsistent naming mess earlier, but better late than never) In the meantime would adding something like Provides: qca2-ossl = %{version}-%{release} to the existing qca-ossl for previous releases help? (In reply to comment #2) > I think the consensus it so deprecate qca (v1 for qt3) and rename qca2 (for > qt4) to qca for f13. > (Probably should've caught this inconsistent naming mess earlier, but better > late than never) It's a good idea, qca is already deprecated in F13. Open a new review for qca and retire qca2 seems reasonable, because qca is migrating to cmake buildsys from qconf/qmake recently. In todays, kde-sig meeting, we considered simply renaming qca2 -> qca to be a simpler way forward. Any comments or objections to that plan? Which source file should we use - qca release tarball or svn snapshot? It seems the release tarball is a bit old and the svn snapshot add cmake support for qca2. That's beyond the scope of renaming, it's up to to you/maintainers. Now, if it were *me*, I'd investigate the snapshot/cmake idea for rawhide as well as pinging upstream wrt plans/schedules for future releases. Hello. Now I am a developer of qca. I am planing to release Qca 2.1.0 within 2 month. This version will merge all plugins in single tarball/package. Also added Qt5 support and removed qconf/qmake build rules. Now it is using only cmake. I guess we let this linger long enough, let's consider it WONTFIX. As for a newer qca release, did that ever happen? Where is it? How can one get it? I want to fix qca-gnupg plugin before. And there is one issue with qca-ossl https://bugzilla.redhat.com/show_bug.cgi?id=1144655. The latest sources you can get always from http://quickgit.kde.org/?p=qca.git New QCA release here https://bugzilla.redhat.com/show_bug.cgi?id=1161767 . Will want updating package in Fedora. Re-opening, we can implement this now, I see old qca was retired, and the major re-work in qca-2.1.0 warrants it I think. qca pkg review, bug #1164348 qca2 retired in rawhide, due to pkg rename bug #1164348 (In reply to Rex Dieter from comment #16) > qca2 retired in rawhide, due to pkg rename bug #1164348 The same should be with qca-cyrus-sasl, qca-pkcs11, qca-ossl and qca-gnupg packages? the plugin/subpkgs were already all named qca-<...>, that's why we wanted to rename things to be consistent. :) I mean that separate plugins packages should be retired. ah yes, you are right in that regard, thanks! |