Sorry for asking topinionsince I've read quite a few replies that say that
the best way to upgrade is by using packages and not compiling.
I always use compiling from source and have never had any problem with
that.
Naturally for those things that I'm not sure of I use checkconfig to run
the 'make install' so I easily can remove them if they don't work as I want
them to (this I learned after installing qmail, took forever to remove.

I would like some opinions about this, I guess I wont change but maybe
someone new to this can get some ideas.

Micke

Micke wrote:

> Sorry for asking topinionsince I've read quite a few replies that say that
> the best way to upgrade is by using packages and not compiling.
> I always use compiling from source and have never had any problem with
> that.
> Naturally for those things that I'm not sure of I use checkconfig to run
> the 'make install' so I easily can remove them if they don't work as I
> want them to (this I learned after installing qmail, took forever to
> remove.
>
> I would like some opinions about this, I guess I wont change but maybe
> someone new to this can get some ideas.

I've been getting .tgz files, and untarring them, and they typically
have an install script. I've been told (I'd have to look up by whom,
but it was around these parts) that I could have used checkinstall,
which would create a real Slackware package. Now I hear about checkconfig.

I guess I really need to read this stuff before I start asking n00b
questions about them.

Hmmm .... read what?
---------------------<gpm shot>-----------------------------------
rich@entheos:~$ man -k checkconfig
checkconfig: nothing appropriate
rich@entheos:~$ man -k checkinstall
checkinstall: nothing appropriate
rich@entheos:~$ apropos checkinstall
checkinstall: nothing appropriate
rich@entheos:~$ which checkinstall
which: no checkinstall in
(/usr/local/OpenCASCADE5.1/ros/../3rdparty/Linux/tcltk/bin:/usr/local/OpenCASCADE5.1/ros/Linux/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/opt/www/htdig/bin:/usr/lib/java/bin:/usr/lib/java/jre/bin:/opt/kde/bin:/usr/lib/qt/bin:/usr/share/texmf/bin:.)
rich@entheos:~$ which checkconfig
which: no checkconfig in
(/usr/local/OpenCASCADE5.1/ros/../3rdparty/Linux/tcltk/bin:/usr/local/OpenCASCADE5.1/ros/Linux/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/opt/www/htdig/bin:/usr/lib/java/bin:/usr/lib/java/jre/bin:/opt/kde/bin:/usr/lib/qt/bin:/usr/share/texmf/bin:.)
rich@entheos:~$
---------------------</gpm shot>-----------------------------------

Thanks,
Rich

Rich Grise wrote:

> I've been told (I'd have to look**up*by*whom,
> but it was around these parts) that I could have used checkinstall,
> which would create a real Slackware package

Hi Rich,

You'll find the package for checkinstall in the extra/ directory of your
favorite Slackware mirror or CD.

Jeffrey

Micke wrote:

> I*always*use*compiling*from*source*and*have*never* had*any*problem*with
> that.

> I would like some opinions about this, I guess I wont change but maybe
> someone new to this can get some ideas.

Hi Micke,

I use official packages whenever they are available, because they are also
no problem, and a bit easier and less time-consuming to install. On a
machine with a full slackware install, in fact, they are already there!

For any other software, I generally compile from source, and create a
slackware package before installing with checkinstall. I do this mostly
because I just don't trust 3rd-party packages.

Occasionally, a piece of software will be such a headache to compile that I
will risk a package from elsewhere, but I'm still picky about where I get
it. For example, I installed the tuxracer package from Vector Linux for my
wife. (Works great too, but you'll also need SDL_Mixer if you have a pre-10
version of Slackware.)

I can understand the fun and sense of craft in compiling *everything* from
source, but such a hobby is not how I prefer to spend to my time. Probably
LFS would be better for that than Slackware anyway, but I have heard it
said that once you get LFS just the way you want it, and running perfectly,
you will find that you have a system indistinguishable from Slackware :-)

Jeffrey

Jeffrey Froman wrote:

> Rich Grise wrote:
>
>> I've been told (I'd have to look**up*by*whom,
>> but it was around these parts) that I could have used checkinstall,
>> which would create a real Slackware package
>
> Hi Rich,
>
> You'll find the package for checkinstall in the extra/ directory of your
> favorite Slackware mirror or CD.
>

Thank You.

Cheers!
Rich :-)

Jeffrey Froman wrote:
<snip>
> I can understand the fun and sense of craft in compiling *everything* from
> source, but such a hobby is not how I prefer to spend to my time. Probably
> LFS would be better for that than Slackware anyway, but I have heard it
> said that once you get LFS just the way you want it, and running perfectly,
> you will find that you have a system indistinguishable from Slackware :-)
>
> Jeffrey

Well, there are some exceptions Sometimes a package maker doesn't
insure that all the optional dependencies are met. I would guess that
this might be done to keep the package somewhat modular. I use both LFS
5.1.1/BLFS 5.1 and Slackware 10.0, both of which include Gnome 2.6.1.
Nautilus was designed so that if a directory is changed by some other
process, the change is immediately reflected in Nautilus. This works in
LFS but not in Slackware, at least on my systems. However, I must admit
that I still use Emacs/dired for working on directories

Regards,
Sedge

On 2004-07-25, Rich Grise <null@example.net> wrote:

> which would create a real Slackware package. Now I hear about checkconfig.

I think the OP may have been confused and meant to say checkinstall. As
near as I can tell checkconfig is some sort of code function.

nb

notbob wrote:

> As near as I can tell checkconfig is some sort of code function.
>
> nb

Correct checkinstall it should be, checkconfig is only a function in some
code I'm trying to get working : ) Don't know where my brain goes
sometimes.

It is very interesting to hear how other do their installations, well at
least for me since I'm trying to get ideas how to make things easier.

Thanks all!

Micke

Micke < wrote:

>notbob wrote:
>
>
>
>>As near as I can tell checkconfig is some sort of code function.
>>
>>nb
>>
>>
>
>Correct checkinstall it should be, checkconfig is only a function in some
>code I'm trying to get working : ) Don't know where my brain goes
>sometimes.
>
>It is very interesting to hear how other do their installations, well at
>least for me since I'm trying to get ideas how to make things easier.
>
>Thanks all!
>
>Micke
>
>
>
It rather depends on what mood you get up in the morning. It boils down
to the variety of choices available and your curiosity to try.
The beauty of Linux is that it gives you this kind of "games". Many
times this kind of "wasting time" is more pleasurable than "real games".
But each one to his own.
That's why we meet here.

Have fun.

Stanislaw
Slack user from Ulladulla.

Micke wrote:

> notbob wrote:
>
>> As near as I can tell checkconfig is some sort of code function.
>>
>> nb
>
> Correct checkinstall it should be, checkconfig is only a function in some
> code I'm trying to get working : ) Don't know where my brain goes
> sometimes.
>
> It is very interesting to hear how other do their installations, well at
> least for me since I'm trying to get ideas how to make things easier.

I've only installed a few packages and a couple of third-party apps
from tarballs, and I can't imagine how it could be made easier.

Type 'i' instead of 'install'? ;-)

Cheers!
Rich