"Push module to official porteus-2.x repository"

[fanthom]

so far i was the only person who was adding modules to 64bit official repository. some people could say that i was doing it not too frequently or that number of modules submitted by me was too small.
now it's time to make an experiment and let the community to do it as well. here is the deal:

please post download links to modules (hosted on external sites like mediafire, etc) which supposed to be added to official repository.

rules to follow:
- please make sure that your module is not present in Porteus official repository already, or is present but with lower version
- please make sure that your module is working with porteus-2.x line when you boot without 'changes=' cheatcode
- please post a category name where your module supposed to be added
- if your module requires non binary dependencies (python, perl, functional) then please add them as well (more info about non binary deps: http://forum.porteus.org/viewtopic.php?f=53&t=1843)
- please submit xzm only (not txz, deb, rpm, etc)
- module name must come with following format: name-version-arch-build_number.xzm (sample: calibre-0.8.64-x86_64-1gv.xzm)
- module must have valid /var/log/packages/name- version-arch-build_number index file

here is the sample form to fill in when making a request:

Code: Select all

Module Name:  calibre-0.8.64-x86_64-1gv.txz
Module Location:  valid url where module was uploaded
Module Category: office
Module Non-Binary Dependencies (if any):
PyQt,dbus-python,dnspython,pil,python,python-cssutils,python-dateutil,python-lxml,python-mechanize,sip

will see how it goes

thanks

[francois]

1) What I needed was examples of package categories. I did found some example in porteus repo:
http://ponce.cc/porteus/x86_64/modules/

I imagine that you would like us to follow the same classification.

2) What is there to be done if there is no /var/log/packages/''package name'' provided with the package. In my case I am building from source? Is there an easy way to build it?

Answer:
- for package size use command du on any folder to get the size of folder and subfolders (to get the size of the module, I put it in the folder to be evaluated):

Code: Select all

root@porteus:~# du /mnt/sda5/64bit_v2_XFCE/porteus/modules/foomatic-db/
29048	/mnt/sda5/64bit_v2_XFCE/porteus/modules/foomatic-db/

- for the folder list:

Code: Select all

root@porteus:~# cd /mnt/sda5/64bit_v2_XFCE/porteus/modules/foomatic/foomatic-db-20130401/
root@porteus:/mnt/sda5/64bit_v2_XFCE/porteus/modules/foomatic/foomatic-db-20130401# find -type d -exec ls -d1 {} \; | cut -c 3-

xmlschema
db
db/source
db/source/PPD
db/source/PPD/Kyocera
db/source/PPD/Kyocera/es
....

[fanthom]

@francois
1) correct
2) your task is bit harder as you are compiling from sources (in most cases users will be just pushing pre-made slackware packages converted to xzm) and instead of creating /var/log/packages/''package name'' manually you should use 'makepgk' utility. please follow this doc:
http://www.slackwiki.com/Building_A_Package

btw: creating slack-desc is crucial as description from it will be visible in PPM.
btw2: you could also use existing slackbuild and just convert it to foomatic. i'll share my script for this:
http://www.mediafire.com/?s1c5m4buykacmrw

instruction:

Code: Select all

a) unpack my archive to /tmp/work
b) download foomatic-db-engine-4.0.8.tar.gz (and other sources) to /tmp/work
c) enter /tmp/work and run 'sh create-slackbuild'
d) edit /tmp/work/foomatic-db-engine/slack-desc and put correct package description
e) enter /tmp/work/foomatic-db-engine folder and run SlackBuild script to create .txz package (will be saved in /tmp folder)
f) convert to xzm and voila :)

please shout loud if you stuck somewhere.

[KnallKopf]

How build fanthom and brokenman the info file ?

Exist a script that build a correct Porteus (1.0 or later) module from a directory with a slack-desc-file ?

For me i have build a script, but i have no idea if it correct.

It does the following:
- Strip all files.
strip -s -v $(find "$DESTDIR")
- Make the info file by using ldd.
Try ldd on all files if this true then add it to the OFFERED list.
Add the result to the REQUIRED list.
Removal linux-vdso from the list (i have no idea why but on the it does not exist in the official module)
- Copy a slack-desc file to "$DESTDIR/install"
- Test if a file exist double on the "$DESTDIR" and system-root and delete them interactiv.
- Change the mode of all directorys to 0755
- Build a txz by using:
makepkg -l y -p -c n slackwaremod.txz
- Build a Porteus module by using txz2xzm

Should i pimp (debugging and better description) my script ? So it can be added to the porteus-scripts.

[fanthom]

@KnallKopf
please do not worry about tracking deps with 'ldd'. we have a script for that which also pulls non binary deps and makes custom tweaks.

all what i need is a properly made slackware package converted to standard xzm. nothing extra.

thanks.

[KnallKopf]

Where can find it ? Or can you publish it ?
This will be great !

[francois]

Code: Select all

d) edit /tmp/work/foomatic-db-engine/slack-desc and put correct package description

It is difficult to have the slack-desc file, FILE list before performing SlackBuild. Should I omit the FILE list?

So I have to run SlackBuild first to create foomatic-db-engine-4.0.12-x86_64-1ftm.txz.

Code: Select all

e) enter /tmp/work/foomatic-db-engine folder and run SlackBuild script to create .txz package (will be saved in /tmp folder)

And then uncompressing it, I get two folders /install and /user, there is no /var/log/package/foomatic-filters.

[fanthom]

@KnallKopf
not sure if i should publish it as people have difficulties with creating modules properly. giving them this tool may cause additional troubles: incorrect deps pulled to the modules.
i rather prefer to look after deps myself before pushing modules to the repo.

please send me PM and i'll forward to you everything what i have (script + extra deps database + custom fixes database).

@francois

It is difficult to have the slack-desc file, FILE list before performing SlackBuild.

not sure if i understand. all what you need to do is to put description, something like here:

Code: Select all

|-----handy-ruler------------------------------------------------------|
foomatic-db-engine: foomatic-db-engine
foomatic-db-engine:
foomatic-db-engine: Foomatic's database engine generates PPD files from the data in
foomatic-db-engine: Foomatic's XML database.
foomatic-db-engine: It also contains scripts to directly generate print queues and
foomatic-db-engine: handle jobs.
foomatic-db-engine:
foomatic-db-engine: http://www.linuxprinting.org/foomatic.html
foomatic-db-engine:
foomatic-db-engine:
foomatic-db-engine:

And then uncompressing it, I get two folders /install and /user, there is no /var/log/package/foomatic-filters.

it will be created once you run txz2xzm (description, file list, package size, etc will be added automatically).

[francois]

I get it now. Your script but also the makepgk procedure, were both useful to get the job done. I am testing my modules always fresh and will be posting them just after. From what I understand the request form treated by your care should do the rest of the job to push the modules into PPM repo.

Thanks a lot.

[francois]

Is this measure could be good for the 32bit repository?

[fanthom]

@francois
yes. running slackbuild on 32bit porteus will produce 32bit package. tweaks not needed - should work ootb.

[KnallKopf]

@ fanthom
I think you should do it, because the decision if the module came into the
repository or not, is yours.

I prefer to build my own scripts, but i need only a description
what the script exactly do.

And later i need the code snippets with the info-file-building.
But i am not yet so far, and will ask you again for the code snippets.

[francois]

@francois
yes. running slackbuild on 32bit porteus will produce 32bit package. tweaks not needed - should work ootb.

Thus you mean that I have to do the same job as I have done for foomatic-db 64bit but with 32bit packages and present them on the 32bit edition section. Is this it?

[francois]

Code: Select all

Module Name:  foomatic-db-4.0-20130414-x86_64-1fl.xzm
Module Location:  http://www.mediafire.com/?oe3zi22n7sa81dq
Module Category: hardware
Module Non-Binary Dependencies (if any): foomatic-filters,foomatic-db-engine

[francois]

Code: Select all

Module Name: foomatic-db-nonfree-4.0-20130414-x86_64-1fl.xzm
Module Location:  http://www.mediafire.com/?8aw73do70av2jih
Module Category: hardware
Module Non-Binary Dependencies (if any): foomatic-db, foomatic-filters,foomatic-db-engine