From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] Add an entry in images sub-menu for ipk repository building
Date: Tue, 15 Jan 2013 17:47:08 +0100 [thread overview]
Message-ID: <1358268430-2431-2-git-send-email-jezz@sysmic.org> (raw)
In-Reply-To: <1358268430-2431-1-git-send-email-jezz@sysmic.org>
Just add necessary infrastructure.
Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
---
fs/Config.in | 1 +
fs/ipk/Config.in | 13 +++++++++++++
fs/ipk/ipk.mk | 22 ++++++++++++++++++++++
3 files changed, 36 insertions(+)
create mode 100644 fs/ipk/Config.in
create mode 100644 fs/ipk/ipk.mk
diff --git a/fs/Config.in b/fs/Config.in
index da4c5ff..7689cc2 100644
--- a/fs/Config.in
+++ b/fs/Config.in
@@ -11,5 +11,6 @@ source "fs/romfs/Config.in"
source "fs/squashfs/Config.in"
source "fs/tar/Config.in"
source "fs/ubifs/Config.in"
+source "fs/ipk/Config.in"
endmenu
diff --git a/fs/ipk/Config.in b/fs/ipk/Config.in
new file mode 100644
index 0000000..b42c9ab
--- /dev/null
+++ b/fs/ipk/Config.in
@@ -0,0 +1,13 @@
+config BR2_TARGET_ROOTFS_IPK_REPO
+ bool "Ipk repository with packages"
+ default y
+ help
+ Create a repository compatible with opkg/dpkg tools.
+
+ Each selected packages is splitted in 4 parts:
+ - main package with debug symbols stripped off
+ - debug symbols
+ - development files
+ - documentation files
+ - locales
+
diff --git a/fs/ipk/ipk.mk b/fs/ipk/ipk.mk
new file mode 100644
index 0000000..8b8d6f2
--- /dev/null
+++ b/fs/ipk/ipk.mk
@@ -0,0 +1,22 @@
+#############################################################
+#
+# Generate a repository for opkg
+#
+#############################################################
+
+define ROOTFS_IPK_REPO_CMD
+ mkdir -p $(BINARIES_DIR)/ipk_repository; \
+ ( cd $(BINARIES_DIR)/ipk_repository && dpkg-scanpackages . ) > $(BINARIES_DIR)/ipk_repository/Packages; \
+ gzip < $(BINARIES_DIR)/ipk_repository/Packages > $(BINARIES_DIR)/ipk_repository/Packages.gz; \
+ echo "Archive: unstable" >> $(BINARIES_DIR)/ipk_repository/Release; \
+ echo "Origin: Buildroot" >> $(BINARIES_DIR)/ipk_repository/Release; \
+ echo "Label: Buildroot autogenerated repository" >> $(BINARIES_DIR)/ipk_repository/Release; \
+ echo "Architecture: $(ARCH)" >> $(BINARIES_DIR)/ipk_repository/Release; \
+ echo "Your repository is ready."; \
+ echo "If you use opkg, add this line to your /etc/opkg/buildroot.conf:"; \
+ echo " src/gz buildroot file://$(BINARIES_DIR)/ipk_repository"; \
+ echo "If you use apt, add this one to /etc/apt/sources.list.d/buildroot.list:"; \
+ echo " deb file://$(BINARIES_DIR)/ipk_repository .";
+endef
+
+$(eval $(call ROOTFS_TARGET,ipk_repo))
--
1.7.9.5
next prev parent reply other threads:[~2013-01-15 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 16:47 [Buildroot] [PATCH v0] Add support for automated building of Opkg repository Jérôme Pouiller
2013-01-15 16:47 ` Jérôme Pouiller [this message]
2013-01-15 16:47 ` [Buildroot] [PATCH 2/3] Add main scripts for opkg repository building Jérôme Pouiller
2013-01-15 16:47 ` [Buildroot] [PATCH 3/3] Add parsing of Config.in in ipk-post.sh Jérôme Pouiller
2013-01-17 10:23 ` [Buildroot] [PATCH v0] Add support for automated building of Opkg repository Jérôme Pouiller
2013-01-17 12:54 ` Thomas Petazzoni
2013-01-17 14:39 ` Jérôme Pouiller
2013-02-13 21:43 ` Carsten Schoenert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1358268430-2431-2-git-send-email-jezz@sysmic.org \
--to=jezz@sysmic.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox