Skip to content
This repository has been archived by the owner on Jan 28, 2020. It is now read-only.

WIP: Split into subpackages #12

Closed
wants to merge 1 commit into from

Conversation

cgwalters
Copy link
Member

  • Some of our hacks (e.g. the systemd coredump bit) are
    maipo-specific
  • We really want to clearly distinguish these things; separate
    -release packages helps, but even better is having different
    version numbers in /etc/os-release.

 - Some of our hacks (e.g. the systemd coredump bit) are
   maipo-specific
 - We really want to clearly distinguish these things; separate
   `-release` packages helps, but even better is having different
   version numbers in `/etc/os-release`.
@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 27, 2018
@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 27, 2018
@cgwalters
Copy link
Member Author

This encodes the 47 for maipo and 48 for ootpa.

@miabbott
Copy link
Member

Will having two spec files cause a problem for rdgo?

%setup -q -n redhat-release-%{base_release_version}

%build
make fs-maipo
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heck, we could collapse this into a single spec and just use the %rhel macro from our buildroot, right?

cgwalters added a commit to cgwalters/os that referenced this pull request Oct 1, 2018
@cgwalters
Copy link
Member Author

Will having two spec files cause a problem for rdgo?

Yep, it'll break it today. I thought of that but had been putting off the problem 😄 - But you're right to call this out now. Maybe the simplest is to use git branches for this, we could split off a maipo branch?

@miabbott
Copy link
Member

miabbott commented Oct 2, 2018

Maybe the simplest is to use git branches for this, we could split off a maipo branch?

or

Heck, we could collapse this into a single spec and just use the %rhel macro from our buildroot, right?

I don't have enough experience with spec files to know if it would be easier to maintain two of them (porting changes between the two) or have a massive one with a bunch of conditionals.

I'd be fine with git branches for now, but defer to others with more expertise.

cgwalters added a commit to cgwalters/os that referenced this pull request Oct 5, 2018
cgwalters added a commit to cgwalters/os that referenced this pull request Oct 10, 2018
@cgwalters
Copy link
Member Author

Obsoleted by #13

@cgwalters cgwalters closed this Oct 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants