public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: Newbie to linux and a question
Date: Sat, 15 Dec 2018 14:08:00 +0100	[thread overview]
Message-ID: <1be91b7b-f1f7-7979-5476-393da97e3d87@slint.fr> (raw)
In-Reply-To: <20181215.123343.486.11@[192.168.1.146]>

On 15/12/2018 13:33, Linux for blind general discussion wrote:
> Don't forget source distros like Gentoo or LFS. You can install your own package managers on those (and gentoo has one called portage), but your primary means of building packages is from source code.
> And even if you're not interested in doing that, installing from source has become vastly simplified over the years; your average user need only run:
> ./configure
> make
> sudo make install
> and this will install a program suitable for 99 percent of users' needs.
> I won't touch on building things like apache, mysql and other database managers, or the linux kernel itself I wouldn't recommend a newby tackle those, anyway. But the above commands are good enough for just about any userland package.

I disagree.

Doing this:
1) Often fails for lack of dependencies, not easy for a newbie to solve.
2) That makes hard to uninstall a software.
3) That makes more difficult to remember which software are installed.
4) You won't be warned of a security issue with the installed version.
5) More generally you deprive yourself of all the benefits of the
packages management system that your distribution provide.

Don't get me wrong: as a distribution maintainer and packager I am used
to compile software manually. But after quick tests I always make
packages that can be handled by the package management tools, to ease
users' life. 

If actually there is no pre-built package for your distribution for a
specific software, better learn how to make one yourself, which won't
happen often if you use a distribution like Debian.
Generally your Linux distribution provides tools to help you do that.

Best,
Didier
--
Didier Spaier
Slint distribution http://slint.fr

  reply	other threads:[~ UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
           ` Linux for blind general discussion
             ` Linux for blind general discussion
               ` Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion [this message]
           ` Linux for blind general discussion
             ` Linux for blind general discussion
         ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
           ` Linux for blind general discussion
             ` Linux for blind general discussion
           ` Linux for blind general discussion
           ` Linux for blind general discussion
         ` Linux for blind general discussion

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1be91b7b-f1f7-7979-5476-393da97e3d87@slint.fr \
    --to=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).