Prev: Iptables problem on Xen
Next: java plug-in Permission denied. Fine as root.
From: Henrik Carlqvist on 15 Mar 2007 17:12
"zlin50" <zlin50(a)gmx.de> wrote:
> @Christopher: I also think, that it's rather a checkinstall than a
> slackware(system) topic. But .... having an unstable(?) binary in a
> stable distribution is a problem of the distribution - in the end.
> And that would be surprising/bothering for me!

I sent a suggestion to Pat that he should revert to 1.5.3 but got the
following reply:

-8<----------------------------------------------------------
> As checkinstall is in /extra I suppose that there will be no patch for
> Slackware 11, but once you spin off a new Slackware current it might be a
> good idea to revert to version 1.5.3 of checkinstall.

I'd actually recommend that people learn how to use slacktrack instead,
which is based on the same file tracking code but was written especially
for Slackware (well, ARMedslack, but same difference ;-). I'm not
likely to revert checkinstall as that won't help to get any issues
addressed -- anyone who wants to can use the checkinstall package from
Slackware 10.2.
-8<----------------------------------------------------------

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

From: Stuart Winter on 15 Mar 2007 17:49
On Thu, 15 Mar 2007 22:12:55 +0100, Henrik.Carlqvist(a)deadspam.com wrote:

> I'd actually recommend that people learn how to use slacktrack instead,
> which is based on the same file tracking code but was written especially
> for Slackware (well, ARMedslack, but same difference ;-). I'm not
> likely to revert checkinstall as that won't help to get any issues
> addressed -- anyone who wants to can use the checkinstall package from
> Slackware 10.2.

Yeah I agree ;-)
http://www.slackware.com/~mozes/

slacktrack actually does use installwatch from the latest version of
CheckInstall (with a patch for something or other), but we use
altertrack (included with slacktrack) to build non-clean packages.

For emacs specifically,
ftp://ftp.armedslack.org/armedslack/armedslack-current/source/e
That's more or less how I build it for ARMedslack - using slacktrack.

From: Christopher Pinon on 16 Mar 2007 04:50
Thanks, Henrik, Stuart, for the tip about slacktrack, which I hadn't
known about, though it does look like it requires more expertise to use
than checkinstall! :-)

About checkinstall, I suppose that you're right about checkinstall-1.5.3
being generally preferable to checkinstall-1.6.0, although I do like the
fact that the latter has an option for _not_ installing the package
built. When I used to use checkinstall-1.5.3 on earlier versions of
Slackware, I realized one day that I had _two_ copies of man pages
everywhere, compressed versions and non-compressed versions. Moreover,
the non-compressed versions would remain even after uninstalling the
packages in question. Clearly, the non-compressed versions of the man
pages were installed by checkinstall-1.5.3 before it made the package in
which the man pages were compressed, and then it installed the package.
The work-around is to turn off 'compression of man pages' with
checkinstall-1.5.3, but this isn't a very elegant solution, given that
one of the nice features of checkinstall is that it _can_ compress the
man pages for you.

What I really need to do is to sit down and learn how to make my own
Slackware packages, but I've successfully avoided this so far! :-)

Christopher
From: Stuart Winter on 17 Mar 2007 07:03
On 16 Mar 2007 08:50:25 GMT, pinon(a)droog.sdf-eu.org wrote:

> Thanks, Henrik, Stuart, for the tip about slacktrack, which I hadn't
> known about, though it does look like it requires more expertise to use
> than checkinstall! :-)

There are more options intended to help make Slackware compatible
packages :-) The main options you ought to use are switched
on by the -Q operator.

Look inside slackware-current/source/n/bitchx
There is bitchx.build

It's usually a good idea to remove the package first, but consult
slacktrack's FAQ about this. In this case I am removing it because
bitchx.build tries to re-gzip a man page already on the system.

# removepkg bitchx

Then as root, invoke slacktrack (you can probably use 'fakeroot'
to simulate root, but not all builds like it, but you can also
use slacktrack in conjunction with fakeroot so that it only calls
fakeroot when setting perms & ownerships -- this is documented too).

slacktrack -Qp bitchx-1.1-i486-3.tgz ./bitchx.build

And then
less /tmp/bitchx-1.1-i486-3.tgz

There's your package!

The bitchx.build script is fairly simple and a good example
of how to use slacktrack.

Enjoy! :)
From: zlin50 on 18 Mar 2007 13:04
I tried checkinstall 1.5.3 (compiled from source) and it worked for
me, as well. So I'll stay with 1.5.3 in 11.0

Thanks to everybody for your support!

First  |  Prev  | 
Pages: 1 2
Prev: Iptables problem on Xen
Next: java plug-in Permission denied. Fine as root.