From 4d8609e66ea530708d2a738b22e3ef3cfa50591877b6fbd32818bebed9079bd0 Mon Sep 17 00:00:00 2001 From: Ludwig Nussel Date: Mon, 31 Aug 2020 15:47:21 +0000 Subject: [PATCH] - Add README.packaging for packagers OBS-URL: https://build.opensuse.org/package/show/systemsmanagement:cockpit/cockpit?expand=0&rev=42 --- README.packaging | 40 ++++++++++++++++++++++++++++++++++++++++ cockpit.changes | 5 +++++ 2 files changed, 45 insertions(+) create mode 100644 README.packaging diff --git a/README.packaging b/README.packaging new file mode 100644 index 0000000..d35e71e --- /dev/null +++ b/README.packaging @@ -0,0 +1,40 @@ +The upstream cockpit spec file is rather complex and ugly. It does +contain information we need though, such as the bundled node +modules. Therefore the package reuses the upstream spec file and +applies openSUSE specifics that upstream doesn't accept on top. For +that purpose a git repo tracks the spec file changes: +https://github.com/lnussel/cockpit + +There' an opensuse-$VERSION branch for each release + +For simple fixes it's fine to just submit the spec file by OBS +means, I'll retrofit in git. Don't worry about that. + +For version updates the git workflow really is needed to maintain +mental health though. + +The following workflow is used to update the package to a newer +version: + +- create a branch for the new version based on the old one: + git checkout -b opensuse-$NEW_VERSION opensuse-$OLD_VERSION +- use interactive rebase to amend the commits marked as EDIT THIS: + git rebase -i $NEW_VERSION + * for the very fist commit download the new tarball and extract + the spec file from it. Copy the spec file over + tools/cockpit.spec. That is basically what changed between the + versions wrt spec file. + * the second one adjust the spec file to have $NEW_VERSION. For + whatever reason the upstream spec file alwas has version 0. + * the rest of the changes should just apply. +- copy the spec file back into the OBS checkout and continue with + regular tasks related to updating packages. +- If any further spec file changes were needed, copy the spec back + into the git tree and commit there. Amend and reorder as needed. +- When done, push the git repo. + +Sending fixes upstream: + +if you have any changes that should go upstream, create a new, clean +branch and cherry pick *one* commit into it. Upstream wants pull +requests with only one commit diff --git a/cockpit.changes b/cockpit.changes index 2d2e050..ef7278e 100644 --- a/cockpit.changes +++ b/cockpit.changes @@ -1,3 +1,8 @@ +------------------------------------------------------------------- +Mon Aug 31 15:46:35 UTC 2020 - Ludwig Nussel + +- Add README.packaging for packagers + ------------------------------------------------------------------- Fri Aug 14 12:09:24 UTC 2020 - Ludwig Nussel