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

Daniel BerrangĂ© <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]



--- Comment #5 from Daniel BerrangĂ© <[email protected]> ---
The package naming approach feels a bit off. Essentially this is just shipping
two applications.

The simplified package file list:

%files -n python3-cvmutils
%{_bindir}/cvm-encrypt-image

%files -n cvmutils-reseal
%{_bindir}/cvm-reseal


Most notably there is no public importable module providing a library API.

Thus I think this falls entirely under the "Application naming" guideline:

 
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_application_naming


IOW, I don't think we need to be using 'python3-' name prefix in any output
package name.

I'd say it is probably ok to use 'cvm-encrypt-image' and 'cvm-reseal' as the
output package names, ie a 100% match for the single binary each one ships.

Is there a need for these two small scripts to be in separate RPMs though ?  If
not a single output package could be merely called "cvmutils".


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2483948

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202483948%23c5

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to