How to compile packages for slacky.eu?
Moderatore: Staff
Regole del forum
1) Citare in modo preciso il nome del pacchetto.
2) Specificare se discussione/suggerimento o richiesta d'aiuto.
3) Leggere attentamente le risposte ricevute
4) Scrivere i messaggi con il colore di default, evitare altri colori.
5) Scrivere in Italiano o in Inglese, se possibile grammaticalmente corretto, evitate stili di scrittura poco chiari, quindi nessuna abbreviazione tipo telegramma o scrittura stile SMS o CHAT.
6) Appena registrati è consigliato presentarsi nel forum dedicato.
La non osservanza delle regole porta a provvedimenti di vari tipo da parte dello staff, in particolare la non osservanza della regola 5 porta alla cancellazione del post e alla segnalazione dell'utente. In caso di recidività l'utente rischia il ban temporaneo.
1) Citare in modo preciso il nome del pacchetto.
2) Specificare se discussione/suggerimento o richiesta d'aiuto.
3) Leggere attentamente le risposte ricevute
4) Scrivere i messaggi con il colore di default, evitare altri colori.
5) Scrivere in Italiano o in Inglese, se possibile grammaticalmente corretto, evitate stili di scrittura poco chiari, quindi nessuna abbreviazione tipo telegramma o scrittura stile SMS o CHAT.
6) Appena registrati è consigliato presentarsi nel forum dedicato.
La non osservanza delle regole porta a provvedimenti di vari tipo da parte dello staff, in particolare la non osservanza della regola 5 porta alla cancellazione del post e alla segnalazione dell'utente. In caso di recidività l'utente rischia il ban temporaneo.
-
- Linux 0.x
- Messaggi: 4
- Iscritto il: gio 16 gen 2014, 18:05
- Nome Cognome: ico
- Slackware: 13.0 to 14.1
- Kernel: 3.0 and up
- Desktop: blackbox
How to compile packages for slacky.eu?
Hi all,
I am the admin of slacky.eu mirror slack.isper.sk. Lately I found out that the number of packages in newer repositories is decreasing... So I decided I want to invest some labor and CPU cycles into improving this situation. So the questions:
How can I help? How to compile more packages? How to submit them to slacky.eu repository? Is there a way to automate this? Is there some cookbook for this?
Thank you
ico
I am the admin of slacky.eu mirror slack.isper.sk. Lately I found out that the number of packages in newer repositories is decreasing... So I decided I want to invest some labor and CPU cycles into improving this situation. So the questions:
How can I help? How to compile more packages? How to submit them to slacky.eu repository? Is there a way to automate this? Is there some cookbook for this?
Thank you
ico
- Blallo
- Packager
- Messaggi: 3302
- Iscritto il: ven 12 ott 2007, 11:37
- Nome Cognome: Savino Liguori
- Slackware: 14.2 / 12.2
- Kernel: 4.4.14-smp
- Desktop: DWM
- Località: Torino / Torremaggiore (FG)
- Contatta:
Re: How to compile packages for slacky.eu?
Hi!
Fist of all, welcome to the Slacky.eu community!
One thing before i describe you everything: please write an introduction here: viewforum.php?f=53
Ok, let's start.
These are our guidelines: unfortunately for you, they are in italian. http://www.slacky.eu/slacky/Linee_guida ... kware_14.1
I'm going to try to explain you
1) You MUST use a full and clean install Slackware. A chrooted Slackware installation works fine too.
(Here a script that can automate the process. http://www.slacky.eu/slacky/Slackware_C ... utoBuilder)
A x64 Slackware host can be used for both x86 and x64 Slackware chroot installations.
2) This is the standard template: you have to delete all unnecessary commented lines, except the licence at the head of the script. http://www.slacky.eu/wikislack/upload/4 ... emplate.sh
In our guidelines you can find templates for cmake and other types of compilation, they are easy to find.
3) You must install requiredbuilder, that create automatically the slack-required file (used by our tool, slackyd, for dependencies checking). You can find it in our repository.
4) The doinst.sh file, that is the post-install script, is optional. If you require it, this is the template. http://www.slacky.eu/wikislack/upload/3 ... i.template
5) The slack-desc file (that is MANDATORY) can be found on Slackbuilds.org, on previous versions inside our repository or you can use this bash script to automate this. http://www.slacky.eu/slacky/Crea_file_slack-desc
Most of the cases, you have only to edit the first part of the script:
- Name of package
- Number version
- Build version: if there is a previous version, even on an older repository (ex: 13.3 or 14.0 repository) and same version number you have to increase.
If version number is different, reset it to "1".
- Tag: don't touch it, on Slacky.eu we use "sl".
- Architecture: x86_64 if target is a x64 package.
- Source url
- Tarball and directory name: if tarball have a non-standard name, write it. If not, leave it blank.
Example: standard template is name-version.tar.(bz2,gz,xz). If is different, type on it a name for the tarball (usually we retype standard name: $PKGNAME-$VERSION.tar.(bz2.gz.xz) )
Same speech for the DIR variable, that is about main directory inside the tarball.
- Documents: if there are some additional documents, write their name here.
- Other files: same as documents, but if they are other files (like additional patches)
I think you know how to launch a SlackBuild compilation.
The directory tree must be like this, after a compilation:
DON'T keep the source tarball, except if it is not downloadable anywhere.
When all is done, package the directory tree inside a tarball and send it to our admin, Loris: slacky@slacky.it
Ok, i think that's all.
Excuse me for my bad english and enjoy our packager' section and our forum
Fist of all, welcome to the Slacky.eu community!
One thing before i describe you everything: please write an introduction here: viewforum.php?f=53
Ok, let's start.
These are our guidelines: unfortunately for you, they are in italian. http://www.slacky.eu/slacky/Linee_guida ... kware_14.1
I'm going to try to explain you
1) You MUST use a full and clean install Slackware. A chrooted Slackware installation works fine too.
(Here a script that can automate the process. http://www.slacky.eu/slacky/Slackware_C ... utoBuilder)
A x64 Slackware host can be used for both x86 and x64 Slackware chroot installations.
2) This is the standard template: you have to delete all unnecessary commented lines, except the licence at the head of the script. http://www.slacky.eu/wikislack/upload/4 ... emplate.sh
In our guidelines you can find templates for cmake and other types of compilation, they are easy to find.
3) You must install requiredbuilder, that create automatically the slack-required file (used by our tool, slackyd, for dependencies checking). You can find it in our repository.
4) The doinst.sh file, that is the post-install script, is optional. If you require it, this is the template. http://www.slacky.eu/wikislack/upload/3 ... i.template
5) The slack-desc file (that is MANDATORY) can be found on Slackbuilds.org, on previous versions inside our repository or you can use this bash script to automate this. http://www.slacky.eu/slacky/Crea_file_slack-desc
Most of the cases, you have only to edit the first part of the script:
- Name of package
Codice: Seleziona tutto
PKGNAME=appname
Codice: Seleziona tutto
VERSION=${VERSION:-1.4.1}
If version number is different, reset it to "1".
Codice: Seleziona tutto
BUILD=${BUILD:-1}
Codice: Seleziona tutto
TAG=${TAG:-sl}
Codice: Seleziona tutto
ARCH=${ARCH:-i486}
Codice: Seleziona tutto
SOURCE="http://downloads.sourceforge.net/project/......./${PKGNAME}-${VERSION}/${PKGNAME}-${VERSION}.tar.gz"
Example: standard template is name-version.tar.(bz2,gz,xz). If is different, type on it a name for the tarball (usually we retype standard name: $PKGNAME-$VERSION.tar.(bz2.gz.xz) )
Same speech for the DIR variable, that is about main directory inside the tarball.
Codice: Seleziona tutto
TAR=
Codice: Seleziona tutto
DIR=
Codice: Seleziona tutto
DOCS="AUTHORS COPYING INSTALL TODO TROUBLESHOOTING docs/ ..."
Codice: Seleziona tutto
SLKFILES=""
The directory tree must be like this, after a compilation:
Codice: Seleziona tutto
name
-version
--package.txz
--src
---name.SlackBuild (don't forget the upper case)
---slack-desc
---slack-required
---doinst.sh (optional)
---patches (optional)
When all is done, package the directory tree inside a tarball and send it to our admin, Loris: slacky@slacky.it
Ok, i think that's all.
Excuse me for my bad english and enjoy our packager' section and our forum
Github: https://github.com/8lall0
- ZeroUno
- Staff
- Messaggi: 5441
- Iscritto il: ven 2 giu 2006, 14:52
- Nome Cognome: Matteo Rossini
- Slackware: current
- Kernel: slack-current
- Desktop: ktown-latest
- Distribuzione: 01000000-current
- Località: Roma / Castelli
- Contatta:
Re: How to compile packages for slacky.eu?
iconvnik, you are welcome in the slacky community.
First, thanks for the mirror.
Yes, the number of packages is decreasing becouse the number of packager is decreasing, so you are very welcome.
First, thanks for the mirror.
Yes, the number of packages is decreasing becouse the number of packager is decreasing, so you are very welcome.
Packages finder: slakfinder.org | Slackpkg+, per aggiungere repository a slackpkg
Codice: Seleziona tutto
1011010 1100101 1110010 1101111 - 0100000 - 1010101 1101110 1101111
-
- Packager
- Messaggi: 363
- Iscritto il: lun 14 set 2009, 18:55
- Slackware: 15.0 multilib
- Desktop: plasma 5
- Contatta:
Re: How to compile packages for slacky.eu?
Anche io sarei disponibile ben volentieri. Se può andar bene datemi un cenno
- Blallo
- Packager
- Messaggi: 3302
- Iscritto il: ven 12 ott 2007, 11:37
- Nome Cognome: Savino Liguori
- Slackware: 14.2 / 12.2
- Kernel: 4.4.14-smp
- Desktop: DWM
- Località: Torino / Torremaggiore (FG)
- Contatta:
Re: How to compile packages for slacky.eu?
Manda un MP a Loris e chiedi di entrare nei packagers
Github: https://github.com/8lall0
-
- Linux 0.x
- Messaggi: 4
- Iscritto il: gio 16 gen 2014, 18:05
- Nome Cognome: ico
- Slackware: 13.0 to 14.1
- Kernel: 3.0 and up
- Desktop: blackbox
Re: How to compile packages for slacky.eu?
Hello,
I read everything you wrote and also translated original italian version. I created chrooted Slackware to experiment (and modified slackware_chroot_autobuilder to install non-interactively, will upload it). Now I have few questions:
Thanks
ico
I read everything you wrote and also translated original italian version. I created chrooted Slackware to experiment (and modified slackware_chroot_autobuilder to install non-interactively, will upload it). Now I have few questions:
- In this document there is mentioned script requirebuilder. The link isn't working. Do you have any other source of that script? I googled something but wanted some "official" version.
- I understand what you wrote, also slackbuilds.org's system of package management, I'm using it quite often. I just don't understand fully the steps needed to resolve all dependencies. If I wanted I can imagine to fetch package by package from slackbuilds.org and compile everything by myself. I just don't know whether the result would be acceptable for slacky.eu repository.
- As I mentioned, I want to compile LibreOffice. My first idea is to fetch that package source from 13.37 repository, since that is the last repo where it appeared. Is there some straightforward way to update dependency list? Or some program to tell me which dependencies are available, which are not of required version and which are missing completely?
Thanks
ico
- Blallo
- Packager
- Messaggi: 3302
- Iscritto il: ven 12 ott 2007, 11:37
- Nome Cognome: Savino Liguori
- Slackware: 14.2 / 12.2
- Kernel: 4.4.14-smp
- Desktop: DWM
- Località: Torino / Torremaggiore (FG)
- Contatta:
Re: How to compile packages for slacky.eu?
- Requiredbuilder:
x86: (we miss it, but if you want to compile it... http://repository.slacky.eu/slackware64 ... .16.5/src/ )
x64: http://repository.slacky.eu/slackware64 ... 64-4sl.txz
- To solve dependencies we use *also* Slackbuilds.org list of deps. But everything is managed by the slack-required file that requiredbuilder creates automatically.
- LibreOffice... we have the Libreoffice-autobuilder made by submax. http://submax.altervista.org/index.php? ... tilang.php
We prefer it because of less usage of *our* band.
x86: (we miss it, but if you want to compile it... http://repository.slacky.eu/slackware64 ... .16.5/src/ )
x64: http://repository.slacky.eu/slackware64 ... 64-4sl.txz
- To solve dependencies we use *also* Slackbuilds.org list of deps. But everything is managed by the slack-required file that requiredbuilder creates automatically.
- LibreOffice... we have the Libreoffice-autobuilder made by submax. http://submax.altervista.org/index.php? ... tilang.php
We prefer it because of less usage of *our* band.
Github: https://github.com/8lall0
-
- Linux 0.x
- Messaggi: 4
- Iscritto il: gio 16 gen 2014, 18:05
- Nome Cognome: ico
- Slackware: 13.0 to 14.1
- Kernel: 3.0 and up
- Desktop: blackbox
Re: How to compile packages for slacky.eu?
Let's first try my 1st outcome: copy-cat chroot autobuilder. This is original (thanks fot that!), you should use that, not my buggy rewrite... The only meaningfull reason for using my version is non-interactive usage. Just run that script with correct set of params to get working chroot environment.
Some examples:
Install really basic system from locally mounted CD:
Install full system from net, Slovak KDE localisation:
..as above but download patches from another server:
ico
Some examples:
Install really basic system from locally mounted CD:
Codice: Seleziona tutto
scab-noint \
-c /data/slacky.eu/chroot2/ \
-s /mnt/cdrom/slackware64/ \
-m a,ap,l,n
Codice: Seleziona tutto
scab-noint \
-c /data/slacky.eu/chroot2/ \
-s http://ftp.linux.cz/pub/linux/slackware/slackware64-14.1/slackware64/ \
-m FULL -p RELATIVE -l sk
Codice: Seleziona tutto
scab-noint \
-c /data/slacky.eu/chroot2/ \
-s http://ftp.linux.cz/pub/linux/slackware/slackware64-14.1/slackware64/ \
-m FULL -l sk \
-p http://slackware.at/data/slackware64-14.1/patches/