Custom package example: Difference between revisions
Line 12: | Line 12: | ||
== Sources == | == Sources == | ||
* | * <sourcecode>http://www.example.com/sourcecode-1.0.tar.xz</sourcecode> | ||
* | * <sourcecode>http://www.example.com/alt/sourcecode-1.0.tar.xz</sourcecode> | ||
* | * <sourcecode>http://www.example.com/patch/sourcecode-1.0_fix.patch</sourcecode> | ||
<md5>9244091002a9d52e91fca0b1f3818ab9 sourcecode-1.0.tar.xz | <md5>9244091002a9d52e91fca0b1f3818ab9 sourcecode-1.0.tar.xz | ||
d41d8cd98f00b204e9800998ecf8427e sourcecode-1.0_fix.patch</md5> | d41d8cd98f00b204e9800998ecf8427e sourcecode-1.0_fix.patch</md5> | ||
== Dependencies == | == Dependencies == |
Revision as of 13:36, 1 February 2012
This page is a rough draft, do not rely on it
This is a sample layout which you must use if you are contributing a custom script. Note that this layout is roughly the same as used in BLFS, however because the page will be imported in LFScript through ScriptFactory it is important that you follow the style set here exactly.
If your software does not use the Pre-installation, Post-installation or DESTDIR sections, you can leave them out. All other sections are mandatory.
If for any reason, your page causes problems with ScriptFactory, it will not be included in LFScript.
Finally, be sure to adapt and include the next line at the top of your page:
LFScript can find this software under the name my-software
.
Sources
- http://www.example.com/sourcecode-1.0.tar.xz
- http://www.example.com/alt/sourcecode-1.0.tar.xz
- http://www.example.com/patch/sourcecode-1.0_fix.patch
MD5 Checksums:
9244091002a9d52e91fca0b1f3818ab9 sourcecode-1.0.tar.xz d41d8cd98f00b204e9800998ecf8427e sourcecode-1.0_fix.patch
Dependencies
- [[NetworkManager]]
- libpng
Make the displayed name of dependencies the scriptname for it, nothing more, nothing less. So not "NetworkManager", but network-manager
. If the dependency is listed on this Wiki, you should link to it.
Do not list optional dependencies.
Pre-installation
If your software requires any pre-installation (like adding special users or groups), you must specify it here.
useradd -m sampleUser
Installation
If the software must be patched, explain here why.
<compile>patch -Np1 < ../sourcecode-1.0_fix.patch</compile>
Compile the software:
<compile>./configure --prefix=/usr && make</compile>
Then, as the root user:
<install>make install</install>
Note that the code block above does not have a DESTDIR=${FAKEROOT}
directive. ScriptFactory will add these automatically if a pre
block has class="asRoot"
.
Packaging note
The source code of this package does not support the standard use of DESTDIR. In stead it uses
prefix=
Post-installation
This section must contain commands which will modify the software after it has been installed, or modify files installed by a different package. It should also contain those commands that configure the package for use on that specific machine.
Note: Post-installation of this software should be performed after all other software has been installed.
For example:
update-desktop-database
If you add class="delayPostinst"
to any code block in this section, all post-installation commands will be delayed until all software has been installed.