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



--- Comment #26 from Ibiam Chihurumnaya <[email protected]> ---
(In reply to Benson Muite from comment #25)
> As per guidelines:
> https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/
> this is a blocker.

Could you please point this out for me? I've gone through the guidelines and
can't see where
it says it's a blocker. It does say %{python3_sitearch} is the right place for
compiled C code so I've reverted to that.

> 
> > c) Seeing as this isn't a blocker I don't think it needs to change, the .so
> > files also don't qualify as "Prohibited Code" to me, correct me if I'm 
> > wrong.
> > 
> 
> They are generated in the release process, though having extra unneeded
> files in the source git repositories does waste space.  Ideally, the release
> process would generate a version without library files, which could then be
> used in Fedora.

Yes they're generated in the release process, is the issue that there are
unneeded files in the repo? 
Because if that's the case, I'll just remove them from the source, although
that's handled in the spec file too.

I do agree with you that having extra unneeded files in the source git repo
wastes space, I'll remove them.


-- 
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=2228190

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

-- 
_______________________________________________
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://pagure.io/fedora-infrastructure/new_issue

Reply via email to