workstation-ostree-config

#65 Add initial comps-sync script, use it to trim package set
Merged by ausil. Opened by walters.
walters/workstation-ostree-config comps-sync  into  master

Download 65.patch

Two prep patches, then this:

Basically, we end up deleting a lot of indirect dependencies.
However, some leaf packages do drop out. All of these I believe
are right to stop shipping by default with the possible exception
of media-player-info...I'm not sure if that was intentional or
not. Anyways let's start this sync process.

-Installing 1344 packages:
+Installing 1335 packages:
-  bcache-tools-1.0.8-10.fc27.x86_64 (fedora-rawhide)
-  isomd5sum-1:1.2.2-1.fc28.x86_64 (fedora-rawhide)
-  kexec-tools-2.0.16-3.fc28.x86_64 (fedora-rawhide)
-  keybinder3-0.3.2-3.fc27.x86_64 (fedora-rawhide)
-  langtable-0.0.38-2.fc28.noarch (fedora-rawhide)
-  langtable-data-0.0.38-2.fc28.noarch (fedora-rawhide)
-  langtable-python3-0.0.38-2.fc28.noarch (fedora-rawhide)
-  lpsolve-5.5.2.0-16.fc27.x86_64 (fedora-rawhide)
-  media-player-info-23-1.fc28.noarch (fedora-rawhide)

3 new commits added

  • Add initial comps-sync script, use it to trim package set
  • manifest: Explicitly list flatpak at the toplevel
  • Further split workstation-base to have a -pkgs.json base

rebased onto de680ffc2b623705adf066469d0420702bd48c3e

This looks nice. Some questions:

  • are some of the packages that were removed from the package list are just deps that get brought in anyway?
  • I'm not sure I entirely understand the need for the 3rd commit: Further split workstation-base to have a -pkgs.json base. Can you explain that one to me?
  • I can pretty easily write a job that will run in openshift that will watch comps and this repo and make sure the two files are in sync and open an issue when they aren't in sync. I imagine you had a similar (or better) idea for how you wanted to do this. Do you mind sharing?

are some of the packages that were removed from the package list are just deps that get brought in anyway?

That's what I meant by:

Basically, we end up deleting a lot of indirect dependencies.

AIUI, the initial list here was basically generated from rpm -qa on a workstation install a long time ago.

I'm not sure I entirely understand the need for the 3rd commit: Further split workstation-base to have a -pkgs.json base. Can you explain that one to me?

The script now has a --save option to rewrite that file automatically.

I can pretty easily write a job that will run in openshift that will watch comps and this repo and make sure the two files are in sync and open an issue when they aren't in sync. I imagine you had a similar (or better) idea for how you wanted to do this.

I'm not sure we need to do that right away...I had just envisioned running this periodically. I don't have any objections to such a script but...e.g. having static deltas set up would be a lot more impactful IMO...

3 new commits added

  • Add comps-sync script, use it to trim package set
  • manifest: Explicitly list flatpak at the toplevel
  • Further split workstation-base to have a -pkgs.json base

Updated; the script now also prints the inverse; packages in workstation but not in the manifest. However, we need to have some debate about adding anything from there; there's random apps like rhythmbox as well as a bunch of "stuff" likeppp and ghostscript etc.

3 new commits added

  • Add comps-sync script, use it to trim package set
  • manifest: Explicitly list flatpak at the toplevel
  • Further split workstation-base to have a -pkgs.json base

Pull-Request has been merged by ausil
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.