TipsAndTricks/EnablingAPackageFeed - Revision history

RossBurton: Replaced content with "This is now covered in the [https://docs.yoctoproject.org/dev-manual/common-tasks.html#using-runtime-package-management documentation]."

2021-06-30T12:07:35Z

Replaced content with "This is now covered in the [https://docs.yoctoproject.org/dev-manual/common-tasks.html#using-runtime-package-management documentation]."

Show changes

Henry Bruce: /* Pyro (2.3) and greater */

2017-10-05T23:57:53Z

Pyro (2.3) and greater

← Older revision		Revision as of 23:57, 5 October 2017
Line 83:		Line 83:

	= Pyro (2.3) and greater =		= Pyro (2.3) and greater =
	~~== Quick and Dirty Feed Serving ==~~
	~~If you don't have a web server already serving up a directory and don't feel like going through the effort to do that you can do the following.~~
	* Assume your feed is /opt/feed
	* apt-get/dnf install python-twistd
	* run twistd on the directory
	~~$ twistd -n web --path /opt/feed -p 5678~~
	* This way you can serve diff feeds on diff ports easily

	== From a Build dir ==		== From a Build dir ==
	=== Easiest Way ===		=== Easiest Way ===

Henry Bruce: /* Create Package Feed */

2017-10-05T23:57:37Z

Create Package Feed

← Older revision		Revision as of 23:57, 5 October 2017
Line 53:		Line 53:
	rsync -r -u --exclude 'x86_64' tmp/deploy/rpm/ /var/www/html/repo		rsync -r -u --exclude 'x86_64' tmp/deploy/rpm/ /var/www/html/repo
	</pre>		</pre>
			* If you don't have a web server already serving up a directory and don't feel like going through the effort to do that you can do the following.
			** Assume your feed is /opt/feed
			** apt-get/dnf install python-twistd
			** run twistd on the directory
			$ twistd -n web --path /opt/feed -p 5678
			* This way you can serve different feeds on different ports

	== Run Package Manager on Target ==		== Run Package Manager on Target ==

Henry Bruce at 23:51, 5 October 2017

2017-10-05T23:51:22Z

← Older revision		Revision as of 23:51, 5 October 2017
Line 1:		Line 1:
			= Morty (2.2) and earlier =
	== Caveat ==		== Caveat ==
	This article is based on work done a few years ago with fido (1.8) and only covers using smart with rpm. Needs some testing and extended to cover using dnf.		This article is based on work done a few years ago with fido (1.8) and only covers using smart with rpm. Needs some testing and extended to cover using dnf.
Line 75:		Line 76:
	$ smart channel --show		$ smart channel --show

			= Pyro (2.3) and greater =
	== Quick and Dirty Feed Serving ==		== Quick and Dirty Feed Serving ==
	If you don't have a web server already serving up a directory and don't feel like going through the effort to do that you can do the following.		If you don't have a web server already serving up a directory and don't feel like going through the effort to do that you can do the following.
Line 83:		Line 85:
	* This way you can serve diff feeds on diff ports easily		* This way you can serve diff feeds on diff ports easily

	~~== Make an RPM Package feed for Pyro and greater releases ==~~		== From a Build dir ==
	=== From a Build dir ===		=== Easiest Way ===
	==== Easiest Way ====
	* Use RPMS		* Use RPMS
	** PACKAGE_CLASSES = "package_rpm" in local.conf		** PACKAGE_CLASSES = "package_rpm" in local.conf
Line 96:		Line 97:
	* Serve up feed		* Serve up feed
	** twistd -n web --path tmp/deploy/rpm -p 5678		** twistd -n web --path tmp/deploy/rpm -p 5678
	==== How to keep a separate feed Dir ====		=== How to keep a separate feed Dir ===
	* Use RPMS		* Use RPMS
	** PACKAGE_CLASSES = "package_rpm" in local.conf		** PACKAGE_CLASSES = "package_rpm" in local.conf
Line 112:		Line 113:
	** twistd -n web --path feedDir -p 5678		** twistd -n web --path feedDir -p 5678

	=== From the Target ===		== From the Target ==
	* make the target aware of the repo you just created.		* make the target aware of the repo you just created.
	** make a dir for repos		** make a dir for repos
Line 130:		Line 131:
	</pre>		</pre>

	=== Why Might I Use This? ===		== Why Might I Use This? ==
	This workflow is one where you need to iteratively try out what packages you want on your image. In my case, I was doing a native build of a complex sw repo and needed to make;fail;add dependency somehow;make again; quite a few times. I certainly did not want to wait while bitbake made a new image with my additional dependency and then wait again while dd copied that image to my usb key. This way, I could bitbake dependency, rerun createrepo, dnf install from target. Much much faster.		This workflow is one where you need to iteratively try out what packages you want on your image. In my case, I was doing a native build of a complex sw repo and needed to make;fail;add dependency somehow;make again; quite a few times. I certainly did not want to wait while bitbake made a new image with my additional dependency and then wait again while dd copied that image to my usb key. This way, I could bitbake dependency, rerun createrepo, dnf install from target. Much much faster.


	~~== Further Reading ==~~
	* [http://labix.org/smart/user-guide Smart online user guide]
	* [https://www.fujitsu.com/jp/group/fct/documents/events/2016/A_Smart_Way_to_Manage_Packages_in_Yocto_Project.pdf Fujitsu ELC 2016 Presentation]

	~~== Future Work ==~~
	* httpd
	* feed-stability

Bavery at 01:16, 8 July 2017

2017-07-08T01:16:23Z

← Older revision		Revision as of 01:16, 8 July 2017
Line 95:		Line 95:
	** bitbake package-index		** bitbake package-index
	* Serve up feed		* Serve up feed
	** twistd -n web --path tmp/~~deply~~/rpm -p 5678		** twistd -n web --path tmp/deploy/rpm -p 5678
	==== How to keep a separate feed Dir ====		==== How to keep a separate feed Dir ====
	* Use RPMS		* Use RPMS

Bavery: /* From the Target */

2017-06-27T19:58:10Z

From the Target

← Older revision		Revision as of 19:58, 27 June 2017
Line 116:		Line 116:
	** make a dir for repos		** make a dir for repos
	*** <pre> mkdir -p /etc/yum.repos.d </pre>		*** <pre> mkdir -p /etc/yum.repos.d </pre>
	** add the repo		** add the repo. The file name <strong> must </strong> end in '.repo' for instance mybuild.repo
	<pre>		<pre>
	[myrepo]		[myrepo]

Bavery at 19:48, 27 June 2017

2017-06-27T19:48:39Z

← Older revision		Revision as of 19:48, 27 June 2017
Line 45:		Line 45:
	** Also, if you find you need an additional recipe not included in the image e.g. gawk, you can do bitbake gawk and it's packages will be available too.		** Also, if you find you need an additional recipe not included in the image e.g. gawk, you can do bitbake gawk and it's packages will be available too.
	*** this can be done iteratively		*** this can be done iteratively
	* Update repo package indices ~~(this step can be excluded in later versions of Yocto)~~		* Update repo package indices
	bitbake package-index		bitbake package-index
	* Copy packages to server. This sample script assumes files are served from /var/www/html/repo		* Copy packages to server. This sample script assumes files are served from /var/www/html/repo

Bavery: /* From a Build dir */

2017-06-27T16:49:48Z

From a Build dir

← Older revision		Revision as of 16:49, 27 June 2017
Line 85:		Line 85:
	== Make an RPM Package feed for Pyro and greater releases ==		== Make an RPM Package feed for Pyro and greater releases ==
	=== From a Build dir ===		=== From a Build dir ===
			==== Easiest Way ====
			* Use RPMS
			** PACKAGE_CLASSES = "package_rpm" in local.conf
			* have package tools
			** EXTRA_IMAGE_FEATURES += " package-management " in local.conf
			* build something you want
			** bitbake mdadm
			* update the package indices
			** bitbake package-index
			* Serve up feed
			** twistd -n web --path tmp/deply/rpm -p 5678
			==== How to keep a separate feed Dir ====
	* Use RPMS		* Use RPMS
	** PACKAGE_CLASSES = "package_rpm" in local.conf		** PACKAGE_CLASSES = "package_rpm" in local.conf
Line 99:		Line 111:
	* Serve up feed		* Serve up feed
	** twistd -n web --path feedDir -p 5678		** twistd -n web --path feedDir -p 5678
	* Note this could also be done directly on the tmp/deploy/rpm directory if desired. This would allow you to skip the rsync. You would still have to run the createrepo command on the tmp/deploy/rpm directory after any additions, however.

	=== From the Target ===		=== From the Target ===

Bavery at 20:51, 22 June 2017

2017-06-22T20:51:48Z

← Older revision		Revision as of 20:51, 22 June 2017
Line 99:		Line 99:
	* Serve up feed		* Serve up feed
	** twistd -n web --path feedDir -p 5678		** twistd -n web --path feedDir -p 5678
			* Note this could also be done directly on the tmp/deploy/rpm directory if desired. This would allow you to skip the rsync. You would still have to run the createrepo command on the tmp/deploy/rpm directory after any additions, however.

	=== From the Target ===		=== From the Target ===

Bavery at 20:40, 22 June 2017

2017-06-22T20:40:36Z

← Older revision		Revision as of 20:40, 22 June 2017
Line 117:		Line 117:
	dnf -v install mdadm		dnf -v install mdadm
	</pre>		</pre>

			=== Why Might I Use This? ===
			This workflow is one where you need to iteratively try out what packages you want on your image. In my case, I was doing a native build of a complex sw repo and needed to make;fail;add dependency somehow;make again; quite a few times. I certainly did not want to wait while bitbake made a new image with my additional dependency and then wait again while dd copied that image to my usb key. This way, I could bitbake dependency, rerun createrepo, dnf install from target. Much much faster.