Down and dirty slackware package.

ewlabonte · 05-22-2010, 10:59 PM

Is there anything inherently bad about making a slackware package this way:

Download the source tarball.
tar zxvf tarball and cd to the source directory

./configure --prefix=HOME$/[packagename]
make
make install
cd HOME$/[packagename]
makepkg HOME$/[packagename].txz
Then
installpkg HOME$/[packagename].txz

I've done it a few times and haven't run int any problems yet.

piratesmack · 05-22-2010, 11:14 PM

You can use "make install DESTDIR=HOME$/[packagename]" instead of "--prefix=HOME$/[packagename]"

That's fine if you're only building the packages for yourself.

If you want to share the packages, use something like

Slackware

Code:

CFLAGS="-O2 -march=i486 -mtune=i686" CXXFLAGS="$CFLAGS" ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-slackware-linux

Slackware64

Code:

CFLAGS="-O2 -fPIC" CXXFLAGS="$CFLAGS" ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=/usr/lib64 --build=x86_64-slackware-linux

ewlabonte · 05-22-2010, 11:22 PM

Cool thanks. Sometimes that's easier than looking around for a Slackbuild script for the package in question.

piratesmack · 05-22-2010, 11:30 PM

You might want to check out src2pkg

Makes building packages from source fast and easy

saulgoode · 05-23-2010, 12:56 AM

If your package contains any shared libraries then they will not be found unless you add $PREFIX/lib to your library path (LD_LIBRARY_PATH).

Personally, I would recommend sticking with a PREFIX of /usr or /usr/local unless you have a special need of unprivileged users to install applications in their HOME directory.

gnashley · 05-23-2010, 02:16 AM

And what about when DESTDIR is not supported by the sources? I'd say use src2pkg for a down (and not dirty) package -of course I would say that...