From e0b093b8b5f93440ad6f63e7b4d5bd8bc9ad5bb3 Mon Sep 17 00:00:00 2001
From: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
Date: Mon, 27 Jul 2020 14:09:07 +0530
Subject: [PATCH] Add step about d/apertis/component file
This file is used throughout our Apertis packaging repositories by all
packages. It specifies which repository component a package is part of
Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
---
content/guides/apertis_packaging_guide.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/content/guides/apertis_packaging_guide.md b/content/guides/apertis_packaging_guide.md
index 785de83c6..f081435e6 100644
--- a/content/guides/apertis_packaging_guide.md
+++ b/content/guides/apertis_packaging_guide.md
@@ -209,6 +209,11 @@ This is the process to import a new package from Debian to Apertis:
* don't use `import-debian-package` on existing repositories, it does not
attempt to merge `apertis/*` branches and instead it re-sets them to new
branches based on the freshly imported Debian package
+* Add a `debian/apertis/component` file reflecting the repository component it is part of (for instance, `target`)
+ * check out the apertis repository: `git checkout apertis/v2021dev0`
+ * add the component file: `echo target > debian/apertis/component`
+ * add the component file to git: `git add debian/apertis/component`
+ * commit the file: `git commit -m "Add d/apertis/component file pointing to target" debian/apertis/component`
* create an empty project on GitLab under the `pkg/*` namespaces (for instance, `pkg/target/hello`)
* configure the origin remote on your local git: `git remote add origin git@gitlab.apertis.org:pkg/target/hello`
* push your local git contents to the newly created GitLab project: `git push --all --follow-tags origin`
--
GitLab