Slack packages

[Collins Richey]

On Tue, 1 Apr 2003 17:39:23 -0500
Chris Kassopulo <ckasso at sprynet.com> wrote:

>  > Collins Richey <erichey2 at attbi.com>  wrote:
>  > I have a group of libraries (all go in /usr/lib) that are older
>  > libc/libg++/etc to support things like phoenix nightly binaries.  I
>  > could simply copy the to /usr/lib, but I would prefer to do this as
>  > a standard Slack package.
>  > 
>  > I've tried 'makepkg', but that expects to find a makefile.  Anyone
> care
>  > to help me out with that?
>  > 
>  
> makepkg will do what you want.
> 
> Put everything in /home/collins/package/usr/local/lib, including
> links. cd to package
> Run makepkg phoenix_libs.tgz
> Answer y to both questions
> 
> y to the first question will delete the links and create an install
> script,
> /home/collins/package/install/doinst.sh.  The install script will
> create the
> links when you install the package.  If you answer no the links are
> just copied into the package and no install script is created.
> 
> The install script is the difference between a slackware package and a
> plain
> tarred archive.  /home/collins/package/phoenix_libs.tgz is the
> slackware package.  It is just a tarred file of everything under
> /home/collins/package.
> 
> As root run installpkg phoenix_libs.tgz to install the package.
> Look at /var/log/packages/phoenix_libs to verify.
> As root run removepkg phoenix_libs to remove it.
> 

Very clear instructions, thanks.

One more question.  Does installpkg automatically do an ldconfig after
you install something in /usr/lib or /usr/local/lib?  Or do in need a
postinstall script that does that?

--
Collins - Slack 9.0 EXT3