Rules for build scripts

This section is designed for your 'porteus build scripts' which create Porteus modules for your favorite applications. Scripts should work like the well-known 'SlackBuilds' with minimum user interaction.
Post Reply
User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Rules for build scripts

Post#1 by brokenman » 31 Jan 2011, 21:57

Please make sure you copy buildscript to the module to make further development easier. Also you MUST include either a /var/log/packages/package-name-1.2.3-i486-1 file that contains a name, description, file size, dependencies list and file list ... or ... a porteus package.index file in /var/module-name.index that has the same info in the same order as a slackware package.

The only stipulation is that the 'description' should have no more than 8 lines (for example)

modulename: Please put your module description here and it
modulename: should not be any longer than 8 lines.
modulename: 8 lines is sufficient to write a good description
modulename: and if you don't use all the line make sure you leave
modulename: the rest of the lines in place and untouched like here.
modulename:
modulename:
modulename:

As we have not yet decided on a package manager for porteus i think it is best that we at least start by following a strict guideline for official modules so that package management will be easier in the future.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Hamza
Warlord
Warlord
Posts: 1846
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Rules for build scripts

Post#2 by Hamza » 01 Feb 2011, 07:20

Thanks ! :D
NjVFQzY2Rg==

aus9

Re: Rules for build scripts

Post#3 by aus9 » 28 Oct 2015, 05:28

Hi

I know this is an old post but thought I would query it. There seems to be changes to the number of lines rule?
the full file of AlsaMixer.app-0.1-x86_64-1_slack is example of breach of 8 line rule.
should not be any longer than 8 lines.
Appears to use the 11 line "rule" set for slack-desc
PACKAGE NAME: AlsaMixer.app-0.1-x86_64-1_slack
COMPRESSED PACKAGE SIZE: 28K
UNCOMPRESSED PACKAGE SIZE: 100K
PACKAGE LOCATION: /tmp/usm/AlsaMixer.app-0.1-x86_64-1_slack.txz
PACKAGE DESCRIPTION:
AlsaMixer.app: AlsaMixer.app (dockapp mixer utility)
AlsaMixer.app:
AlsaMixer.app: AlsaMixer.app is a mixer utility for Linux systems with ALSA sound
AlsaMixer.app: driver. It is designed to be docked in Window Maker (and other wms).
AlsaMixer.app: This utility has three volume controllers that can be configured to
AlsaMixer.app: handle any sound source.
AlsaMixer.app: Sound sources can be easily muted and there is also wheel mouse
AlsaMixer.app: support.
AlsaMixer.app:
AlsaMixer.app: Home page: http://www.dockapps.org/file.php/id/253
AlsaMixer.app:
FILE LIST:
./
install/
install/slack-desc
usr/
usr/doc/
usr/doc/AlsaMixer.app-0.1/
usr/doc/AlsaMixer.app-0.1/INSTALL
usr/doc/AlsaMixer.app-0.1/COPYING
usr/doc/AlsaMixer.app-0.1/AlsaMixer.app.SlackBuild
usr/doc/AlsaMixer.app-0.1/README
usr/bin/
usr/bin/AlsaMixer
also
dependencies list
I am not sure if anyone is interested but the smallest bundle XZM I have on 64 bit is for youtube-dl, when I look at the contents of it,
the file list is a bit too large to show here....I can't see any mention of the "bundled" dependencies.

Question if I may?
Is there a template on what the dev team expect for any new builds?

thanks for reading

Post Reply