You are not logged in.
Pages: 1
Hello im hitting walls 
Let me ask out right here how would you do
if you would create a package from http://deluge-torrent.org/ to get latest version
ive been looking around but i must be stupid i just dont understand how to start
for example i download http://www.archlinux.org/packages/extra/any/deluge/
and it needs this Dependencies:
- desktop-file-utils
- hicolor-icon-theme
- libtorrent-rasterbar>=0.15.0
- python2-chardet
- python2-distribute
- python2-pyopenssl
- pyxdg
- twisted
- xdg-utils
- librsvg (optional) - needed for gtk ui
- pygtk (optional) - needed for gtk ui
- python2-mako (optional) - needed for web ui
- python-notify (optional) - libnotify notifications
so now when i know what dependencies are needed, how do i process this down
to a package for slitaz?
Please treat me as the dumpest linux user ever
Sincerally
Martin Svensson
Hi ztealmax,
I have a question, why do we take time to write detailed documentation ?
The cookutils doc give you step by step instruction to create packages, and say creating package on slitaz is one of the easiet way to package, one file (receipt) with all info and compilation option. Maybe I should stop writing doc and just give comands :-) So let build a package in 5 commads:
# tazpkg -gi tazdev
# tazdev gen-chroot
# tazdev chroot
# cook setup
# cook test
Cook test will create a test package to see if you ok. Then create a new receip for deluge:
# cook new deluge
Edit the receipt in (chroot)/home/slitaz/wok/deluge/receipt and fill up the variables, the try a first build (it will probably fail but give you info on missing deps)
# cook deluge
To uderstand the way receipt and cook work you MUST read some official doc since it is the only way to create official packages:
Cook (also installed on all slitaz release):
http://hg.slitaz.org/cookutils/raw-file/tip/doc/cookutils.en.html
Receipt doc: http://doc.slitaz.org/en:cookbook:receipt
- Christophe
Offline
hehe thanx for the info m8, ill really try rtfm 
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]