Create Packages - Revision history

MymsMan: Add Git usage

2020-03-11T17:19:14Z

Add Git usage

MymsMan: /* Coding your package */ - expand a bit

2020-03-11T13:19:37Z

‎Coding your package: - expand a bit

Ezra pound at 13:40, 28 February 2016

2016-02-28T13:40:07Z

Ezra pound at 13:37, 28 February 2016

2016-02-28T13:37:10Z

MymsMan: add GZIP to required packages

2015-07-29T12:58:45Z

add GZIP to required packages

Ezra pound at 11:21, 4 February 2014

2014-02-04T11:21:30Z

Ezra pound at 17:15, 17 November 2013

2013-11-17T17:15:21Z

Ezra pound at 16:34, 11 November 2012

2012-11-11T16:34:28Z

Adsb: Describe dpkg-deb

2012-05-14T16:58:27Z

Describe dpkg-deb

Adsb: Fix typo

2012-05-14T16:47:58Z

Fix typo

← Older revision		Revision as of 17:19, 11 March 2020
Line 120:		Line 120:

	If you have any packages which you'd like published in the [http://hummypkg.org.uk hummypkg.org.uk] repository, then email them to [mailto:packages@hummypkg.org.uk packages@hummypkg.org.uk].		If you have any packages which you'd like published in the [http://hummypkg.org.uk hummypkg.org.uk] repository, then email them to [mailto:packages@hummypkg.org.uk packages@hummypkg.org.uk].
		+
		+	== Using Git to store and maintain package ==
		+
		+	It is recommended that you use the Git library system to provide version control and to allow for collaborative development with others.
		+
		+	See [[Maintain packages with Git]] for a guide to using Git with Humax packages.
		+	Most of that page also applies to maintaining your own packages but there are also a few differences which are covered here.
		+
		+	As package owner you will be responsible for establishing the principal repository for the package and will work directly with that repository rather than a forked copy and you will also be responsible for merging the branches created by you or others into the master branch once you are satisfied they are working correctly and then removing empty branches.
		+
		+	=== Create a new repository for your package ===
		+
		+	On the Dashboard of the [https://git.hpkg.tv/ Hummy Git website] click to create a New Repository
		+	[[File:New Repository.png\|frame\|centre]]
		+	Provide the Package name, Visibility (Public is best) and Description but ''do not'' select the 'Initialize Repository' option then click on 'Create Repository' buttton
		+	On your local machine switch to the folder for the package and upload it the repository.
		+	<pre>
		+	cd /mod/tmp/my-first-package
		+	git init
		+	git add .
		+	git commit -a -m "first commit"
		+	git remote add origin https://git.hpkg.tv/USERNAME/my-first-package.git
		+	git push -u origin master
		+	</pre>
		+
		+	=== Merge changes into '''master''' branch ===
		+	This can be done locally on your machine for changes you have made or on the web repository for Pull Requestsgo created by you or others
		+	==== Local Merge ====
		+	After completing changes switch to master branch, merge the changes, delete the branch and synchronize with the remote repository
		+	<pre>
		+	git checkout master
		+	git merge branch-name
		+	git branch -d branch-name
		+	git push
		+	</pre>
		+	If the branch had bee pushed to the remote it can be deleted
		+	<pre>
		+	git push origin --delete branch-name
		+	git remote prune origin
		+	</pre>
		+	==== Remote Merge ====
		+	On the Pull Request tab of the [https://git.hpkg.tv/ Hummy Git website] Review the changes are OK and Approve the changes, or Request Changes if required
		+	[[File:Review Pull request.png\|frame\|center]]
		+	Once satisfied click on the "Merge Pull Request" button after which you can click on the "Delete Branch" button
		+	Synchronize your local repository
		+	<pre>
		+	git checkout master
		+	git pull
		+	</pre>

	== Unpacking an existing package ==		== Unpacking an existing package ==

@@ Line 5: / Line 5: @@
 ==Coding your package==
 Most of the customised firmware is written in a language called Jim/TCL, See the Jim Manual [http://jim.tcl.tk/fossil/doc/trunk/Tcl_shipped.html '''HERE'''] with other bits in C/C++ and the Humax runs a Linux operating system.
 == Package Repositories ==

← Older revision		Revision as of 13:40, 28 February 2016
Line 1:		Line 1:
		+	__NOTOC__
	The modified firmware includes a lightweight package management system called opkg ([http://code.google.com/p/opkg/ home page]) which is similar to the Debian package management system (dpkg).		The modified firmware includes a lightweight package management system called opkg ([http://code.google.com/p/opkg/ home page]) which is similar to the Debian package management system (dpkg).

@@ Line 1: / Line 1: @@
 The modified firmware includes a lightweight package management system called opkg ([http://code.google.com/p/opkg/ home page]) which is similar to the Debian package management system (dpkg).
 == Package Repositories ==
 The custom firmware is configured to use the package repository at [http://hummypkg.org.uk/packages.html hummypkg.org.uk] by default.
 == Package Format ==

@@ Line 19: / Line 19: @@
   humax# opkg update
   humax# opkg install pkgtools
 Next create a directory to hold your new package and create a directory within it called CONTROL, which will be used for the package meta-information:

@@ Line 66: / Line 66: @@
 ; Depends : A list of dependencies for this package, optionally with version constraints [http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps see Debian documentation]
 ; Description : A description of the package. Continuation lines must be prefixed by white space.
 The CONTROL directory can also contain other package maintenance scripts such as <tt>preinst</tt>, <tt>postinst</tt>, <tt>prerm</tt> and <tt>postrm</tt>. See [http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html the Debian documentation for more details and examples]. The scripts are called with various arguments during package maintenance operations. Many simple packages do not require any maintenance scripts.
@@ Line 78: / Line 79: @@
 Maintainer: af123
 Description: hello
-^D
+Tags: http://wiki.hummy.tv/wiki/Custom_Firmware_Overview/
 </pre>

@@ Line 107: / Line 107: @@
 == Unpacking an existing package ==
-The <tt>pkgtools</tt> package also contains a utility which can be used to unpack an existing package into a directory structure for editing or just for investigation.
+The <tt>pkgtools</tt> package also contains a utility which can be used to unpack an existing package into a directory structure for editing or just for investigation, NOTE :- you need to install the gzip Custom Firmware package in order to use opkg-unpack
 <pre>

← Older revision		Revision as of 16:58, 14 May 2012
Line 118:		Line 118:
	</pre>		</pre>

		+	If you have a Debian-based Linux machine, opkg packages can be examined and manipulated using the dkpg-deb command.
		+
		+	wget http://hummypkg.org.uk/hdrfoxt2/base/busybox_1.19.3-3_mipsel.opk
		+	dpkg-deb -x busybox_1.19.3-3_mipsel.opk <tmpdir>

	== Packing and Unpacking Bundled Packages ==		== Packing and Unpacking Bundled Packages ==

← Older revision		Revision as of 16:47, 14 May 2012
Line 119:		Line 119:


−	== Packing and ~~Upacking~~ Bundled Packages ==	+	== Packing and Unpacking Bundled Packages ==

	An OPK file contains the executable program /s and all the set-up scripts required for a single Custom Firmware package, However this single package may require other packages to be present in order to work. An OPB file contains the main package and all the peripheral packages require for it to run in a single file, the OPK’s are tarred together to form this file and can be viewed as follows :-		An OPK file contains the executable program /s and all the set-up scripts required for a single Custom Firmware package, However this single package may require other packages to be present in order to work. An OPB file contains the main package and all the peripheral packages require for it to run in a single file, the OPK’s are tarred together to form this file and can be viewed as follows :-