From: smitty on

I tried out makepkg today but the package I am building has no DESTDIR in
the Makefile. I tried installing to a temp directory and then made the
package but after installation the directories had the wrong system paths
in them. They had the paths to the temp directory where the package was
built. Is there a set of instructions somewhere that tells in DETAIL how
to use make pkg?

Thanks
From: Henrik Carlqvist on
smitty(a)home.com wrote:
> I tried out makepkg today but the package I am building has no DESTDIR in
> the Makefile. I tried installing to a temp directory and then made the
> package but after installation the directories had the wrong system paths
> in them. They had the paths to the temp directory where the package was
> built. Is there a set of instructions somewhere that tells in DETAIL how
> to use make pkg?

As makepkg assumes that the contents of the directory tree below current
directory is exactly what you want in the package it can't be used to
install software which doesn't behave well.

For ill-behaving software there is a program called checkinstall that is
able to create packages by tracking what happens when you do "make
install" or any other command to install software. Unfortunately
checkinstall has had some problems with the 1.6 versions. In my experience
version 1.5.3 was far more reliable. However, I haven't tried checkinstall
version 1.6.2 which was released only about a month ago.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: Sylvain Robitaille on
smitty(a)home.com wrote:

> I tried out makepkg today but the package I am building has no DESTDIR
> in the Makefile. ...

For those packages I've built with a similar problem, I simply have
added a DESTDIR to the Makefile, and gotten on with it ...

The best source to learn how to use makepkg, in my opinion, is the
collection of *.SlackBuild scripts that ship with the distribution,
combined with those at the various SlackBuild repositories often
mentioned in this newsgroup ...

--
----------------------------------------------------------------------
Sylvain Robitaille syl(a)encs.concordia.ca

Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
From: smitty on
On Fri, 22 Jan 2010 20:11:58 +0100, Henrik Carlqvist wrote:

> smitty(a)home.com wrote:
>> I tried out makepkg today but the package I am building has no DESTDIR
>> in the Makefile. I tried installing to a temp directory and then made
>> the package but after installation the directories had the wrong system
>> paths in them. They had the paths to the temp directory where the
>> package was built. Is there a set of instructions somewhere that tells
>> in DETAIL how to use make pkg?
>
> As makepkg assumes that the contents of the directory tree below current
> directory is exactly what you want in the package it can't be used to
> install software which doesn't behave well.
>
> For ill-behaving software there is a program called checkinstall that is
> able to create packages by tracking what happens when you do "make
> install" or any other command to install software. Unfortunately
> checkinstall has had some problems with the 1.6 versions. In my
> experience version 1.5.3 was far more reliable. However, I haven't tried
> checkinstall version 1.6.2 which was released only about a month ago.
>
> regards Henrik

It doesn't work on my system.. Any better than 1.6.
I won't make the package, that's why I'm checking out makepkg.
From: root on
smitty(a)home.com <smitty(a)home.com> wrote:
> On Fri, 22 Jan 2010 20:11:58 +0100, Henrik Carlqvist wrote:
>
>> smitty(a)home.com wrote:
>>> I tried out makepkg today but the package I am building has no DESTDIR
>>> in the Makefile. I tried installing to a temp directory and then made
>>> the package but after installation the directories had the wrong system
>>> paths in them. They had the paths to the temp directory where the
>>> package was built. Is there a set of instructions somewhere that tells
>>> in DETAIL how to use make pkg?
>>
>> As makepkg assumes that the contents of the directory tree below current
>> directory is exactly what you want in the package it can't be used to
>> install software which doesn't behave well.
>>
>> For ill-behaving software there is a program called checkinstall that is
>> able to create packages by tracking what happens when you do "make
>> install" or any other command to install software. Unfortunately
>> checkinstall has had some problems with the 1.6 versions. In my
>> experience version 1.5.3 was far more reliable. However, I haven't tried
>> checkinstall version 1.6.2 which was released only about a month ago.
>>
>> regards Henrik
>
> It doesn't work on my system.. Any better than 1.6.
> I won't make the package, that's why I'm checking out makepkg.

I seem to recall that I had trouble with checkinstall and the
version of tar that came with Slackware at the time. I reverted
to the older tar and checkinstall worked again.
 |  Next  |  Last
Pages: 1 2
Prev: Okular plugin for epub
Next: Alternative to keepassx