

meet together better said both used together and staying separate
to compliment each others special qualities
this isnt an official union but its a way linux works together as a team
by forming useful programs together in strange ways
sbopkg gets the sources and organizes them
src2pkg builds the packages as an option ( the default slackbuild can be used too )
slackbuilds still can be used or src2pkg
they get chosen in the menu so full function of sbopkg still works flip_conf switches the build tool
on the fly no manual edits needed

2,733 build scripts GUI driven auto package maker
1. dependency bison is needed for src2pkg http://bigbass-porteus.googlecode.com/f ... i486-2.txz
UPDATED src2pkg
2.install src2pkg http://distro.ibiblio.org/pub/linux/dis ... arch-2.txz open a terminal then src2pkg --setup that compiles it for you
Code: Select all
src2pkg --setup
3 dependency gpg http://bigbass-porteus.googlecode.com/f ... i486-1.txz for sbopkg
4. install sbopkg http://bigbass-porteus.googlecode.com/f ... 7_PORT.txz open terminal
Code: Select all
sbopkg
5. this is a GUI to configure src2pkg automatically pre set for Porteus use ( I wrote this one so you can get started quickly ) http://bigbass-porteus.googlecode.com/f ... 7_PORT.txz run this once in menu Development gui_src2pkg_conf and select ok
the reason why I added src2pkg to sbopkg is you can have better control if you want to edit the
the sources and rebuild and this will allow you to control of every step of the package build

when all works fine the modules are made by the module team
Joe