On Wed, 11 Aug 2004 05:10:32 GMT, zebee@zip.com.au wrote:


> [...] but I was expecting a bit more about good practice in
> writing and setting configs for example.

man rcs
man cvs


Best regards,

--
DIG (Dmitri I GOULIAEV)
Aahz's law: The best way to get information on usenet is
not to ask a question, but to post the wrong information.

* Zebee Johnstone <zebee@zip.com.au> writes:

> aha! That sounds like it, RPM just uses shell scripts too.

All of the Slackware package tools are shell scripts. If you are
comfortable with shell scripts, you might get the answers you're
seeking by...

$ less /sbin/*pkg



--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Genius - Is the ability to reduce |
| the complicated to the simple |
|----------------------------------<steve@youngs.au.com>---|

Zebee Johnstone <zebee@zip.com.au> writes:

> And all packages are installed in whatever dirs configure thinks is a
> good thing?

I'm sure I have seen these docs cited in this group before


http://www.pathname.com/fhs/

I believe, and hope I'm right!, that on the whole Slackware packages t
this standard.

hth



Glyn
--
RTFM http://www.tldp.org/index.html
GAFC http://slackbook.lizella.net/
STFW http://groups.google.com/groups?hl=e...inux.slackware
GAFL http://www.xemacs.org http://www.gnus.org/

Glyn Millington <wistanswick@linuxmail.org> writes:

> Zebee Johnstone <zebee@zip.com.au> writes:
>
>> And all packages are installed in whatever dirs configure thinks is a
>> good thing?
>
> I'm sure I have seen these docs cited in this group before
>
>
> http://www.pathname.com/fhs/
>
> I believe, and hope I'm right!, that on the whole Slackware packages t
> this standard.

Hmmmm - sorry; I'm not in fact trying to win the prize for least literate
poster, but you would never guess it.

I believe that Slack packages conform to this standard.


The post I had in mind was

Message-ID: <2003-08-20T22-12-40@bubble.markhill.me.uk>


Sorry to follow-up/correct myself.

Glyn
--
RTFM http://www.tldp.org/index.html
GAFC http://slackbook.lizella.net/
STFW http://groups.google.com/groups?hl=e...inux.slackware
GAFL http://www.xemacs.org http://www.gnus.org/

On Tue, 10 Aug 2004 23:13:23 -0400, dom@vbi.vt.edu wrote:

> a) makepkg, good source of examples would be slackware source
> b) checkinstall/slackpkg, they let you automate the creation of packages. in
> 90% or more cases, checkinstall is good enough.

slackpkg is not for building packages; slacktrack can build packages.

--
Stuart Winter
www.interlude.org.uk, www.biscuit.org.uk, www.armedslack.org

Zebee Johnstone wrote:
> In alt.os.linux.slackware on Tue, 10 Aug 2004 22:04:40 -0700
> Jeffrey Froman <jeffrey@I.slack> wrote:
>>
>> I'm confused about some of the other answers you've been getting to this
>> question. It seems to me you are looking for the /var/log/scripts
>> directory, and after reading through a few of the scripts, I don't see any
>> glaring reason why they couldn't include things like hostname checking,
>> conditionals, and crontab entries. They are just bash scripts, after all.
>
> aha! That sounds like it, RPM just uses shell scripts too.
>
> What reads /var/log/scripts and when? Or is that where old /install
> scripts go when finished with?

yes. and after uninstalling a packages, they go to
/var/log/removed_scripts (and the package descriptions to
/var/log/removed_packages).

the doinst.sh scripts can do whatever you want to do upon installing,
including modifying crontab entries and saving existing config
files. (check some of the existing scripts on how this is usually
done. one important aspect of this is of course that the tar ball that is
the package does *not* contain files with identical names to files that
already exist. i.e., if you create a postfix package and you don't want it
to overwrite /etc/postfix/main.cf, the package should contain a file
/etc/postfix/main.cf.new. then doinst.sh can mv the old config file to
/etc/postfix/main.cf.save and mv /etc/postfix/main.cf.new to
/etc/postfix/main.cf.

removepkg does do some checking of the relevan doinst.sh script, and IIUC
removes symlinks created by it. don't know what else it checks and
undoes. check it out and see if you can use it. and if it doesn't provide
all you need, you could consider modifying removepkg to run an uninstall
script.

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

Steve wrote:

> All of the Slackware package tools are shell scripts. If you are
> comfortable with shell scripts, you might get the answers you're
> seeking by...
>
> $ less /sbin/*pkg

Better yet; "/sbin/*pkg*" (Don't forget pkgtool!)

LittleJohn
Madison, AL

Stuart Winter wrote:

> On Tue, 10 Aug 2004 23:13:23 -0400, dom@vbi.vt.edu wrote:
>
>> a) makepkg, good source of examples would be slackware source
>> b) checkinstall/slackpkg, they let you automate the creation of packages.
>> in 90% or more cases, checkinstall is good enough.
>
> slackpkg is not for building packages; slacktrack can build packages.

thanks, i always confuse those two.

Zebee Johnstone wrote:

> In alt.os.linux.slackware on Tue, 10 Aug 2004 22:04:40 -0700
> Jeffrey Froman <jeffrey@I.slack> wrote:
>>
>> I'm confused about some of the other answers you've been getting to this
>> question. It seems to me you are looking for the /var/log/scripts
>> directory, and after reading through a few of the scripts, I don't see
>> any glaring reason why they couldn't include things like hostname
>> checking, conditionals, and crontab entries. They are just bash scripts,
>> after all.
>
> aha! That sounds like it, RPM just uses shell scripts too.
>
> What reads /var/log/scripts and when?

You do! Immediately, if not sooner. ;-)

> Or is that where old /install
> scripts go when finished with?

Damned if I know. You'd have to look at some install scripts, and see
if they save themselves there.

I noticed nobody's mentioned rpm2tgz. It's a script, by Pat Volkerding.
It says, in part:
echo "$0: Converts RPM format to standard GNU tar + GNU zip format."
echo " (view converted packages with \"less\", install and remove"
echo " with \"installpkg\", \"removepkg\", \"pkgtool\", or manually"
echo " with \"tar\")"
echo
echo "Usage: $0 <file.rpm>"

You could run this on some of your RPMs, and look at the output, and
get an idea what a package might look like.

I've only scanned the package docs, but it looked to me that you write
your own install and remove scripts, and can do anything you want to.

But I think you're barking up at least one additional rope here -
you say that you're setting up and configuring multiple machines
from scratch, right? If that's the case, what do you need to create
packages for? Just install everything when you install Slack. Take
a look at Pat's install scripts - I know there's at least one person
around here who knows where to find that setup script - and customize
it.

Slack just plain doesn't have the same package problem other distros
have. That's another one of its advantages. Slack expects its system
admin to know what he or she's doing.

You can write an install script that keeps track of _everything_, and
an uninstall script that puts everything back exactly the way it was
if you want.

But if you make a stable, complete system in the first place, then
there's no need for package management at all.

But if you're writing software to distribute that runs on any system,
then you'd want to make a package out of it.

Hope This Helps!
Rich

* littlejohn <littlejohn@DeleteMe.knology.net> writes:

> Steve wrote:
>> $ less /sbin/*pkg

> Better yet; "/sbin/*pkg*" (Don't forget pkgtool!)

Oh yeah, that one too. Must have forgotten it because I never use
it... too much eye-candy for me. :-P

--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Genius - Is the ability to reduce |
| the complicated to the simple |
|----------------------------------<steve@youngs.au.com>---|