4 ms·

I just upgraded my main personal desktop from slack 12.1 (lagged behind recently :) to slack 13.1. Though an upgrade from anything older than slack 13.0 is unsu

by wazoox 16y ago

I just upgraded my main personal desktop from slack 12.1 (lagged behind recently :) to slack 13.1. Though an upgrade from anything older than slack 13.0 is unsupported, it worked pretty well :) Now I'll have to upgrade my slack 13.0 work desktop, will be a breeze... By the way installing applications properly from source is very easy now with "makepkg" : simply do ./configure && make && mkdir PKG \ && make install DESTDIR=./PKG && \ cd PKG && sudo makepkg ../myapp-version-arch-rev.txz \ sudo installpkg ../myapp-version-arch-rev.txz

koenigdavidmj 16y ago
Check http://www.src2pkg.net/ http://www.src2pkg.net/ out---you just pass it a tarball and it will figure out how to build it, for most types of packages.
- wollw 16y ago
  Thanks for both of these. I've been making SlackBuild scripts or installing in /usr/local until now.
  - koenigdavidmj 16y ago
    Also, http://www.sbopkg.org/ http://www.sbopkg.org/ takes the drudgery out of using SlackBuild scripts from http://slackbuilds.org/ http://slackbuilds.org/ ; you may wish to check it out.
peterwwillis 16y ago
Just as a reminder, this will create and install your software as owned with your local user/group. This means your /usr/bin/ and other directories will now be writable by your local user and group. You can pass '-c y' to makepkg to make all directories owned by root:root and mode 0755, which may screw with some things that expect group 'bin' or more tight permissions. I prefer to do 'make install DESTDIR=./PKG/ && rm -rf ./PKG/ && sudo make install DESTDIR=./PKG/ && cd PKG && sudo makepkg -c n -l y ....'. This first tests if the Makefile properly supports DESTDIR (assuming the 'make install' will fail if it tried to install a file to a root-owned directory). If it does, it runs the 'make install' as root with the DESTDIR argument, which will create all the files with the expected owners/perms. I put it all in some shell scripts a while back if you're interested: http://psydev.syw4e.info/new/slacktools/ http://psydev.syw4e.info/new/slacktools/

by wazoox 16y ago

koenigdavidmj 16y ago

Check http://www.src2pkg.net/ http://www.src2pkg.net/ out---you just pass it a tarball and it will figure out how to build it, for most types of packages.

wollw 16y ago
Thanks for both of these. I've been making SlackBuild scripts or installing in /usr/local until now.
- koenigdavidmj 16y ago
  Also, http://www.sbopkg.org/ http://www.sbopkg.org/ takes the drudgery out of using SlackBuild scripts from http://slackbuilds.org/ http://slackbuilds.org/ ; you may wish to check it out.

peterwwillis 16y ago

Just as a reminder, this will create and install your software as owned with your local user/group. This means your /usr/bin/ and other directories will now be writable by your local user and group. You can pass '-c y' to makepkg to make all directories owned by root:root and mode 0755, which may screw with some things that expect group 'bin' or more tight permissions. I prefer to do 'make install DESTDIR=./PKG/ && rm -rf ./PKG/ && sudo make install DESTDIR=./PKG/ && cd PKG && sudo makepkg -c n -l y ....'. This first tests if the Makefile properly supports DESTDIR (assuming the 'make install' will fail if it tried to install a file to a root-owned directory). If it does, it runs the 'make install' as root with the DESTDIR argument, which will create all the files with the expected owners/perms. I put it all in some shell scripts a while back if you're interested: http://psydev.syw4e.info/new/slacktools/ http://psydev.syw4e.info/new/slacktools/