public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dhruba Bandopadhyay" <dhruba@codewordt.co.uk>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] System health and portage diagnostics
Date: Thu, 15 May 2003 23:11:12 +0100 (BST)	[thread overview]
Message-ID: <2620.146.176.60.52.1053036672.squirrel@mail.codewordt.co.uk> (raw)

Hello

Currently, portage has no diagnostic capability as such that could scour
the essential parts of the system and act on anomalies.  Staying on that
thought, frequently, when users have problems with portage they are
resolved by doing the most trivial tasks a fraction of which are given
below.

ldconfig
env-update
source /etc/profile
revdep-rebuild (from gentoolkit)

I wish to propose that all tools that are scattered around the various
packages intended for diagnosing and maintaining system health be
integrated into one and included in portage.  These diagnostics can be
assigned to a command within portage which would not only execute them but
check /etc/make.conf file as well as other essential files for common
syntax errors such as line breaks in CFLAGS and so on.

This proposal is in an attempt to make portage more centralised and self
reliant rather than being reliant upon hacks from gentoolkit which remain
out dated as portage grows.  To me it has always seemed that diagnostic
capability rather than read capability is essential to any system
administration tool as is already present for other mainstream operating
systems and this can go a big way in solving problems before they are
filed as bug reports.

What are your thoughts on the applicability and feasibility of this
matter?  I look forward to hearing from all.

With regards
Dhruba Bandopadhyay

-- 
What if the prophecy is true?  What if tommorrow the war could end?
Isn't that worth fighting for?  Isn't that worth dying for?
    -- Morpheus in 'The Matrix Reloaded' - 23 May 2003



--
gentoo-dev@gentoo.org mailing list


                 reply	other threads:[~2003-05-15 21:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2620.146.176.60.52.1053036672.squirrel@mail.codewordt.co.uk \
    --to=dhruba@codewordt.co.uk \
    --cc=gentoo-dev@gentoo.org \
    /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