Project

Profile

Help

Issue #1515

closed

pulp comps.xml usage doesn't jibe with fedora policy

Added by semyers about 8 years ago. Updated almost 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Our current comps.xml file[0] creates many package groups. In the strictest sense of a yum repository, our groups usage is probably just fine, but in the broader context of fedora, groups have a more specific meaning[1] that isn't really compatible with how we're currently using them. Specifically, package groups in fedora are distribution-wide, and visible in the fedora installer. Addition of groups to fedora is non-trivial, and requires buy-in from fedora devlopers. As a result, we should consider using alternatives to package groups so we can provide consistent install instructions across distributions while still respecting fedora conventions.

Fedora has very recently[2] added support to rpms for weak dependencies, but at the moment dnf doesn't appear to support them. While these are a good option, ideally any solution to this would be well-supported across all distributions where pulp installations are supported. This probably means using metapackages (packages that only depend on other packages) instead of package groups, and then probably sparingly and only in ways that benefit the average user.

tl;dr we probably shouldn't use groups so much

[0]: https://github.com/pulp/pulp/blob/73f178121522563fd9e8809ea824be409825f13a/comps.xml
[1]: https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups
[2]: https://lists.fedoraproject.org/pipermail/devel/2015-July/212181.html

Actions #1

Updated by bmbouter about 8 years ago

+1 to switching to meta packages for better integration for fedora. We picked comps.xml arbitrarily (I think) instead of using meta packages.

The use case that I believe is important is that once a user has decided to install pulp can install one thing and pulp gets installed.

Actions #2

Updated by mhrivnak about 8 years ago

  • Triaged changed from No to Yes

Added by semyers over 7 years ago

Revision e00a852e | View on GitHub

docs mention the COPR projects, no more groupinstalls

groupinstall change: re #1515 https://pulp.plan.io/issues/1515

copr stuff: re #1993 https://pulp.plan.io/issues/1993

Added by semyers over 7 years ago

Revision e00a852e | View on GitHub

docs mention the COPR projects, no more groupinstalls

groupinstall change: re #1515 https://pulp.plan.io/issues/1515

copr stuff: re #1993 https://pulp.plan.io/issues/1993

Actions #3

Updated by semyers over 7 years ago

Our docs from 2.10 onward no longer reference the comps groups for installing pulp. comps.xml and anything referencing it or the package groups should be fixed to no longer do either of those things.

Actions #4

Updated by bmbouter almost 5 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #5

Updated by bmbouter almost 5 years ago

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

Actions #6

Updated by bmbouter almost 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF