SliTaz Forum
You are not logged in.
Pages: 1
Hi,
Probably stupid question - but I can't find answer in docs. I made receipt for FSTHost, so what's next ?
How can I add it to official repository ?
Do I need provide you binary packages for all version (cooking,4.0 etc) or receipt file is enough (i.e. you have some build hosts) ?
oh .. one more question. FSTHost will works better with wine-rt - so, is there any chance for add wine-rt patch to wine package ? I can provide receipt file for this.
Offline
Well ?
Offline
Hi, Paweł!
Execuse me for late answer 
Just to confirm. You was read built-in documentation for cookutils? And wrote receipt. And cooked your package well in your local build host? And you was installed your package into clean system, and it works well? Great!
It takes me some days to run from scratch: to read docs, to install build host, to read/write receipts...
SliTaz have several online repos for packages receipt. They all placed in the hg.slitaz.org, and they have names: wok, wok-stable, wok-tiny, wok-undigest. Really, I don't know for what we have so many woks, I think: wok-tiny for tiny-slitaz project; wok (just) for cooking/rolling current SliTaz; wok-stable for latest stable SliTaz release (now 4.0); wok-undigest for what?
Next, only developers have write access to Hg repos. If you want to develop SliTaz (write receipts, change scripts and tools, translate website and docs...) then you need write access to Hg. You need to contact with SliTaz Maintainer Christophe Lincoln (pankso).
But for single commits, anyone can write their patches and peceipts, and share with current developers via mailing list or forum. I mean, you can rename your "receipt" to "receipt.txt" (or compress it using zip or tar.gz) right now, and attach it to this forum topic. (I heard some people has troubles with attachments, so I can mail you, and you'll mail me back your receipt).
Have a nice day!
Offline
Answering your second question.
Paweł, can you confirm that we need to patch regular wine package? Any back-side effects? Or, better to provide separate wine-rt package with realtime patch?
Offline
@Aleksej,
Info taken from http://doc.slitaz.org/en:cookbook:wok that should clarify the idea of having "so many woks":
There is more than one Wok on the Mercurial repositories:
wok-undigest: contributions awaiting testing/bug-fixing for inclusion in the unstable Wok
wok: packages for the unstable, Cooking release
wok-stable: packages for the stable SliTaz release
Initially, any contributions will be committed to the undigest repository. When the package has seen sufficient testing with regards to automatic generation, it can be moved to the Wok.
;-)
Offline
Thanks guys for answers.
Yes, I have working "receipts" and even ready-made packages for FSTHost, Wine-RT and sudo-pam with added /etc/pam.d/sudo file which is necessary. Wine-RT patch is absolutely necessary for Audio threads, and is usefully for some games. After all I think we should separate package like other distros have. In Arch (AUR) wine-rt package is even maintained by patch-autor ;-)
I can made more packages including set_rlimits, rtirq .. and I can maintain this packages for some time. So seems that I need to send e-mail to developers. Actually .. I thought they are already here ;-)
Offline
Stephane, thank you for explaination. Sorry, but it still unclear for me. Better I'll begin new topic and you answer all my questions. Ok?
Paweł, yes, already here. You can address me as a junior developer 
I have not so high skill as others, but I still learn more and more.
Please, attach your receipts here, or mail me: al dot bobylev at gmail dot com.
Stephane, so we should put these receipts to undigest wok?
Offline
Ok. You got it on you email box and here. Small note for this.
fsthost is IMHO ready to upload to reposotory. I compile it in 4.0 only, but if there will be a problem then you can easily ask current maintainer for patch ;-)
wine-rt - I disable all stuff that I don't use .. but probably for general use is good idea to adjust it to "wine" package (i.e. remove CONFIGURE_ARGS redefinition). Please note that it use latest wine (1.5.15), while slitaz 4.0 currently use 1.4 tree.
sudo-pam - added missing file /etc/pam.d/sudo - and additional /etc/security/limits.conf which is normally provided by "pam" package. So, this probably should be changed to some "sed" magic - but I'm not sure is tazpkg always install pam before sudo-pam (IMHO it should). If yes then I can provide some "magic" ;-)
As I said - I can officially maintain this packages and some other ;-)
Offline
Xj, I've put your receipts into undigest. See here cooker logs: http://cook.slitaz.org/undigest/
Follow links under "Activity" header, and see cooking logs.
Too many errors, need to fix I think?
Offline
Thanks. It seems that fsthost compiled (build) ok but there are problems while cook resolving dependencies (I mean all this mkdir errors) - this is probably not releated to recepit (?). So, fsthost build OK and it can be add to repo 
wine-rt (and it dev package) there are some errors related to fonts - I try reproduce it, fix and give you a feedback. Maybe this is because I use development version, can you try change version to 1.4.1 (stable) ?
I check sudo-pam once again - it build ok in 4.0 but maybe not in cook.
Offline
I have answers:
sudo-pam use sudoers from "sudo" package. Actually don't know why there is separate sudoers for slitaz - it have only less comments from default file. I also bump version to 1.8.6p3 (latest stable)
wine-rt - according to topic below - it compile OK. so it is ready, but I also add libjpeg and libpng to dependencies.
http://forum.winehq.org/viewtopic.php?t=2974
Please find improved receipts and push it further.
PS. I can't attach this files, so I send it to you via @.
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]