SEO

Hello from the baffled Timelord
I need to create a grouping of packages for another system running
Slackware. Both systems (mine and the target) are running the same, ah,
release number.

To create a package all I do is put the actual directories containing
my programs or kernel modules into temp and then run the makepkg
program and point it there?

Or do I have my steps fouled up someplace?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, gregg dot drwho8 atsign gmail dot com dared to utter,
> Hello from the baffled Timelord
> I need to create a grouping of packages for another system running
> Slackware. Both systems (mine and the target) are running the same, ah,
> release number.
>
> To create a package all I do is put the actual directories containing
> my programs or kernel modules into temp and then run the makepkg
> program and point it there?

I'm not sure exactly what you want. From the sound of things, it seems
that you want to be able to easily install a list of packages, but that
your solution to this is to just create one big package os everything.

Can you please refine your question? If you're asking how to install a
selection of already made packages, look at tag files. If you're
asking how to make packages from software you compile, then makepkg is
part of the solution.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFDXtzmzLTO1iU1uO4RAkQ1AJ9QdLsHgFAYDeiYUKHwm8 BiJN3TXgCgx3AS
TlDhxelv84DGOyHWm9HDjuo=
=tBza
-----END PGP SIGNATURE-----

In article <Ncudnb8uiOx2QcPeRVn-vg@trueband.net>, alan@lizella.netWORK
says...
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>In alt.os.linux.slackware, gregg dot drwho8 atsign gmail dot com dared to utter,
>> Hello from the baffled Timelord
>> I need to create a grouping of packages for another system running
>> Slackware. Both systems (mine and the target) are running the same, ah,
>> release number.
>>
>> To create a package all I do is put the actual directories containing
>> my programs or kernel modules into temp and then run the makepkg
>> program and point it there?
>
>I'm not sure exactly what you want. From the sound of things, it seems
>that you want to be able to easily install a list of packages, but that
>your solution to this is to just create one big package os everything.
>
>Can you please refine your question? If you're asking how to install a
>selection of already made packages, look at tag files. If you're
>asking how to make packages from software you compile, then makepkg is
>part of the solution.
>
>- --
>It is better to hear the rebuke of the wise,
>Than for a man to hear the song of fools.
>Ecclesiastes 7:5

Hello from the less baffled Timelord
You've got it. On this machine, when running Slackware 10.0, I'm in the process of
putting together a collection of programs that will be installed on another machine,
also running the same release. Part of the problem is that I'm not familiar with the
creation process, only the installation process. I suspect that the man pages for
makepkg contain everything I'll need to know.
--
Gregg drwho8 atsign att dot net
"This signature is not here."

The Eighth Doctor wrote:
> In article <Ncudnb8uiOx2QcPeRVn-vg@trueband.net>, alan@lizella.netWORK
> says...
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>In alt.os.linux.slackware, gregg dot drwho8 atsign gmail dot com dared to utter,
>>
>>>Hello from the baffled Timelord
>>>I need to create a grouping of packages for another system running
>>>Slackware. Both systems (mine and the target) are running the same, ah,
>>>release number.
>>>
>>>To create a package all I do is put the actual directories containing
>>>my programs or kernel modules into temp and then run the makepkg
>>>program and point it there?
>>
>>I'm not sure exactly what you want. From the sound of things, it seems
>>that you want to be able to easily install a list of packages, but that
>>your solution to this is to just create one big package os everything.
>>
>>Can you please refine your question? If you're asking how to install a
>>selection of already made packages, look at tag files. If you're
>>asking how to make packages from software you compile, then makepkg is
>>part of the solution.
>>
>>- --
>>It is better to hear the rebuke of the wise,
>>Than for a man to hear the song of fools.
>>Ecclesiastes 7:5
>
>
> Hello from the less baffled Timelord
> You've got it. On this machine, when running Slackware 10.0, I'm in the process of
> putting together a collection of programs that will be installed on another machine,
> also running the same release. Part of the problem is that I'm not familiar with the
> creation process, only the installation process. I suspect that the man pages for
> makepkg contain everything I'll need to know.
> --
> Gregg drwho8 atsign att dot net
> "This signature is not here."
>


If you're installing from source, I would either use DESTDIR to
install to a 'fake' destination directory, build packs (using makepkg)
from that directory, and then copy those packs to some other media
(CD/DVD) or a shared directory from which to install them on the other
box(es). Alternatively, you could use checkinstall to build the
packages if you're not concerned about having proper slack-desc files
in the packages.

However, I may not be seeing the big picture here...

RW

--

http://rlworkman.net

"+Alan Hicks+" <alan@lizella.netWORK> wrote in message
news:Ncudnb8uiOx2QcPeRVn-vg@trueband.net...

pgp trash troll delete

Could you please place your pgp headers and sigs in the X-headers? If you
do not know how to do this you should check out the postings made by Keith
Weller.

Thank you for your consideration.

cordially, as always,

rm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Could you please trim your quotes to only that portion relevant to your
reply? Thanks.

In alt.os.linux.slackware, The Eighth Doctor dared to utter,
> You've got it. On this machine, when running Slackware 10.0, I'm in the process of
> putting together a collection of programs that will be installed on another machine,
> also running the same release. Part of the problem is that I'm not familiar with the
> creation process, only the installation process. I suspect that the man pages for
> makepkg contain everything I'll need to know.

Take a look at the slides from Stuart Winter's presentation at FOSDEM.
They're a good introduction to the topic and are available in
OpenOffice.org format.

<URL:http://www.fosdem.org/download/speakers/slackware.sxi>

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFDX4fjzLTO1iU1uO4RAvIsAKC/DEAouHyanxIz0fq/ugxDYEIc2QCfXDxw
GPEFPLYB6ROqC7AjcKHUnS4=
=v1TB
-----END PGP SIGNATURE-----

The Eighth Doctor wrote:

> Part of the problem is that I'm not familiar with the creation process,
> only the installation process.

If its not part of a learning process then take a look at Checkinstall. When
you use the 'checkinstall' command instead of 'make install' it will build
a Slackware package and then install it. Now you'll have a package you can
move to the other computer and here it can be installed the usual way.

You can find Checkinstall in the /extra tree.
--
Thomas O.

This area is designed to become quite warm during normal operation.

"+Alan Hicks+" <alan@lizella.netWORK> wrote in message
news:feCdnVrjwPd6GsLenZ2dnUVZ_tGdnZ2d@trueband.net ...

pgp trash troll delete

> Could you please trim your quotes to only that portion relevant to your
> reply? Thanks.

No. Could you please buy your pgp trash in the X-headers, where it belongs.
If you don't know how to do it, check the postings made by Keith Diller.
Your inclusion of pgp trash in the content and sig of your message violates
usenet standards of netiquette.

Thank you.

cordially, as always,

rm

In article <10004850.fpK6IP8zHI@news.inet.tele.dk>, thover@post2.tele.dk says...
>
>The Eighth Doctor wrote:
>
>> Part of the problem is that I'm not familiar with the creation process,
>> only the installation process.
>
>If its not part of a learning process then take a look at Checkinstall. When
>you use the 'checkinstall' command instead of 'make install' it will build
>a Slackware package and then install it. Now you'll have a package you can
>move to the other computer and here it can be installed the usual way.
>
>You can find Checkinstall in the /extra tree.
>--
>Thomas O.
>
>This area is designed to become quite warm during normal operation.

Hello from the Eighth Doctor
Both you, Thomas, and of course you Alan make good sense. Thomas I'll take a
look at checkinstall, and naturally Alan I'll look at those slides.

As for you RM, go stuff a grenade in your shorts.
---
Gregg drwho8 atsign att dot net
"This signature sleeps with a loaded baseball bat by its bed."