Hi! Having read the brief discussion here, downloaded the pkgsrc
slackware 9.1 tarball from http://www.netbsd.org and installed it using
default values. An old bsd fan (GNU/Linux supports more hardware, which
it why I use it), I chose Slackware due to the similarities to bsd and
to the excellently documented config files. In spite of all my
tinkering around with little knowledge, I never crashed Slack.

BTW the link at the netbsd site to an article called "Slackware Linux
with pkgsrc Packages" is currently broken. Any tips where one can find
it?

pkgsrc runs very smoothly except for the hiccoughs caused by package
maintainers who don't keep their packages up to date when new versions
of the dependencies, e. g. apel for emacs, are elsewhere fed into the
tree. But a friendly email to the maintainer usually produces the
desired effects within a few days. Not having seen what the xemacsers
are up to for some time, I did

bmake

in the /usr/pkgsrc/editors/xemacs-current

directory and let my SMP machine do some work. Occasionally, e. g. for
perl, using the -B (backwards compatibility) switch as "bmake -B" helped
bmake (netbsd users make) complete compilation that otherwise failed
without this switch. Had to use the -k ("complete") switch to get the
xemacs-packages to finish installation due to the version mismatches
(apel and flim) mentioned above.

There is a big set of tools to optimize the compiler in /etc/make.conf
and to generally keep things tidy and under control.

If a lazy, brain-amputated mere end user like yours truly can use
pkgsrc, it is a piece of cake for the rest of you Slackwareians. ;-)

Greetings,

Lux
--
If you receive this by error, please delete it and inform the sender.
Key fingerprint: 8994 CFDD 9C60 C978 A488 689F 5DCC EFC4 4D36 580D
To Big Brother Echelon from "spook":
Blair colonel domestic disruption heroine Kennedy jihad cracking Cocaine

A. L. Meyers wrote :

> BTW the link at the netbsd site to an article called "Slackware Linux
> with pkgsrc Packages" is currently broken. Any tips where one can find
> it?

Lost links like this can usually be found in Googles cache.
--
Thomas O.

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

In alt.os.linux.slackware, Thomas Overgaard dared to utter,
> Lost links like this can usually be found in Googles cache.

You can also try the Wayback Machine.

--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

On 2004-03-06, Thomas Overgaard <thover@post2.tele.dk> wrote:
>
> A. L. Meyers wrote :
>
>> BTW the link at the netbsd site to an article called "Slackware Linux
>> with pkgsrc Packages" is currently broken. Any tips where one can find
>> it?
>

you mean this..?

http://users.piuha.net/martti/comp/s...slackware.html


-donito

donito <dshuff@NOSPAMhotmail.com> writes:

> On 2004-03-06, Thomas Overgaard <thover@post2.tele.dk> wrote:
> >
> > A. L. Meyers wrote :
> >
> >> BTW the link at the netbsd site to an article called "Slackware Linux
> >> with pkgsrc Packages" is currently broken. Any tips where one can find
> >> it?
> >
>
> you mean this..?
>
> http://users.piuha.net/martti/comp/s...slackware.html

Yes, donito, thank you!

Lux
--
If you receive this by error, please delete it and inform the sender.
Key fingerprint: 8994 CFDD 9C60 C978 A488 689F 5DCC EFC4 4D36 580D
To Big Brother Echelon from "spook":
SDI Khaddafi Mossad Arafat quiche PLO Somalia Treasury genetic Uzi jihad

Alan Hicks wrote :

> You can also try the Wayback Machine.

Didn't even know about this service. I wonder how they managed to keep
this as a secret.
--
Thomas O.

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