Tomasz Chmielewski wrote:
Felipe Sanchez wrote:
It can't be done. But it's already done. What does this mean?
Checkinstall *does* create a subdirectory containing all files inside
the package. It's part of the packaging process. The directory,
however, is deleted afterwards.
It is quite possible to modify checkinstall so it can produce just a
tarball of the package with no scripts whatsoever. I don't know how
useful that would be but it is certainly possible. All of the work is
practically done already: Take a look into the Slackware package
creation step and you should be on track.
Now that I think of it, there is a way right now: Run checkinstall
with -d2 and you would get a checkinstall-debug file containing the
temp dir for that run of checkinstall, including the package
subdirectory.
Hi,
That indeed works, but will it work on a system which doesn't have any
tools that support creating rpm, deb or tgz packages?
[I made a quick check - trying to create a slackware package on a
system that doesn't support it - and indeed it works)]
a linux without taz and gzip would not be very helpful...