public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "gentoo@codewordt.co.uk" <gentoo@codewordt.co.uk>
To: gentoo-dev@gentoo.org
Cc: dhruba@codewordt.co.uk
Subject: [gentoo-dev] Local/per-package use flags absent from UFED
Date: Tue, 22 Jul 2003 21:43:27 +0100	[thread overview]
Message-ID: <20030722204327.GA13816@feathers.codewordt.co.uk> (raw)

Hello

Recently, I've found that certain packages are using use flags specific to that package only but absent from ufed.  Take ntp for example:

$ emerge ntp -vp
Calculating dependencies ...done!
[ebuild  N   ] net-misc/ntp-4.1.1b-r6  -parse-clocks

The '-parse-clocks' use flag was not present in ufed.  I have several more examples that I cannot remember at this time.

This causes the following problems.

* The user is unable to find out the description of the use flag.
* The user may overlook flags not present in ufed resulting in incorrect configuration.
* If this problem is valid then it points towards a problem with ufed.
* Bearing the recent phenomenal explosion in use flags having these extra flags flying around only serves to inflame the problem or information overload.

- Are these per-package use flags which are distinctly different from local use flags?
- If so, is ufed in its current state unable to deal with such flags?
- Is ufed due to undergo any further development to take account of ncurses and per package use flags or is it going to remain static?

I would also like to raise certain fundamental issues about use flags in general but I'll leave that for another thread at another time.

Many thanks.
Dhruba Bandopadhyay.

--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-07-22 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 20:43 gentoo [this message]
2003-07-22 20:54 ` [gentoo-dev] Local/per-package use flags absent from UFED Fred Van Andel
2003-07-22 21:22   ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-

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=20030722204327.GA13816@feathers.codewordt.co.uk \
    --to=gentoo@codewordt.co.uk \
    --cc=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