Hi,

I am just installing a current slack. Hereby I discovered a weird
thing:

Now I will give an example from the A series:
In the tagfile under the "a" directory bzip2 is tagged "ADD" but in the

setup program in the menue where I can
individually choose packages(I chhosed "expert" mode)
bzip2 is not tagged "REQUIRED" as it should be because an "ADD"
should show in setup "REQUIRED", or not!?

Also cpio: "ADD" in the tagfile , no tag in setup.

Also findutils, floppy, gawk and many, many packages more.


Why is this so? Can someone explain it, please?

I am using an iso of slack-current from slackware.no from the 18th Sep;
just if you need this
info to answer my question.


Thanks and kudos for the great work for this great distro.

On 19 Sep 2006 13:29:50 -0700, rpg_kernel@yahoo.de wrote:

> Now I will give an example from the A series:
> In the tagfile under the "a" directory bzip2 is tagged "ADD" but in the
> setup program in the menue where I can
> individually choose packages(I chhosed "expert" mode)
> bzip2 is not tagged "REQUIRED" as it should be because an "ADD"
> should show in setup "REQUIRED", or not!?

Tagfiles contain a definite list of packages that should be
installed.
Tagfiles you see in slackware/*/ are used in "newbie" and "full"
installation modes (ie. without prompting user for decisions).
'expert' mode uses slackware/*/maketag script to create tagfiles,
'menu' mode uses slackware/*/maketag.ez for that. Those two scripts
contain initial list of packages marked as "to install" (note the
"on" and "off" after every package short description).
You can tell the installer to use your own tagfiles, using
"custom" or "tagpath" installation mode.

Hope this little explanation clears thing for you.

I also hope it's correct. In case it isn't -- please someone
corrects me.

Cheers,

--
I do not approve anything that tampers with natural ignorance.
Ignorance is like a delicate exotic fruit; touch it and the bloom
is gone.

> Hope this little explanation clears thing for you.

Yeah, thanks. Your explanation cleared it up.

> I also hope it's correct. In case it isn't -- please someone
> corrects me.

I just looked into the directories and into the maketag files:
Your explanation must be correct because you can read there the
settings I saw in the setup program under the expert mode.

Maybe a proposal for the devs of Slack (for the next revision):
Put the tagfiles and maketag scripts under a special directory.
Because maybe there are also others
who "don't see" these tiny files in middle of hundreds of packages in
the
directories.
Under special config dirs the "semantics" of the files would be more
clear
(at least I think).