On Wed, Jan 20, 2010 at 02:13:49PM +0100, Moritz Wilhelmy wrote: > On Wed, Jan 20, 2010 at 03:11:03PM +0300, anonymous wrote: > > Maybe it is ok too, but I haven't tried it. I suggest Slackware because > > I think that it is what OP asked for: you can build software by hand, > > make package and install with a package manager. You don't have > > to write building script if you don't want to. It is in constrast to > > Arch where you can't create package without PKGBUILD. Of course, you > > can use tar, gzip and other tools, but if format of package is changed > > you will need to rewrite all your scripts dealing with packages. > > > > This sounds interesting. > slackware does not have dependencies, so I don't think it works for me, > but how does package creation on slackware works seems interesting. > Maybe you have some further information about it? >
>From http://www.slackbook.org/html/package-management-making-packages.html: makepkg(8) will package up the current directory into a valid Slackware package. It will search the tree for any symbolic links and add a creation block to the postinstallation script for creating them during the package install. It also warns of any zero-length files in the package tree. To build dwm package you need to do: $ mkdir $builddir $ make install DESTDIR=$builddir $ cd $builddir $ makepkg dwm-1.0-x86-1.txz