| Summary: | adding hal to profiles/${ARCH}/use.defaults | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
| Component: | [OLD] Unspecified | Assignee: | Project Gentopia <gentopia> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | CC: | gnome |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Petteri Räty (RETIRED)
2005-03-25 10:44:46 UTC
cups and samba are set in the default profile. use flags _never_ get enabled by installing ebuilds. that's your job. Try emerge samba. And emerge -C samba. The samba use flag is turned on when you have samba installed. There is the profiles/base/use.defaults for file this job. (In reply to comment #3) > There is the profiles/base/use.defaults for file this job. And exactly this feature needs to be buried, since it makes installations indeterministic and supersedes the administratrs decision what he wants to have installed. The idea is fundamentally broken. Well maybe this should be stated as comments in the file? Unless there is some plan to get rid of profiles/base/use.defaults, you really have no buisness closing this bug as invalid since you don't maintain hal. There are plenty of use flags that offer this feature already and I think its valid that hal be considerd for it. Most new gnome/kde(and a growing number of other apps) users don't get advertised hal features despite having it installed only to find out that they had to set yet another use flag. Looking at your first comment, it seems you may be unfamiliar with use.defaults anyways. This doesn't supersede any admin decisions since setting -hal in make.conf or package.use will override use.defaults. (sorry if this came or as cranky or bitter, its early here...I mean no harm.) (In reply to comment #6) > Looking at your first > comment, it seems you may be unfamiliar with use.defaults anyways. This doesn't > supersede any admin decisions since setting -hal in make.conf or package.use > will override use.defaults. (sorry if this came or as cranky or bitter, its > early here...I mean no harm.) That's not the point. Having to set -* and then the flags you want in make.conf is simply the wrong approach. Really, I have seen mmore than one or two threads where people don't understand where the one or the other use flag comes from they have never defined. Yes, we have to tell users how to deal with use flags, but use flags should not be added automatically. ARCH teams, please consider adding "hal" to USE flag defaults since as per discussions on my rants on the mailing list about extra USE flags came to say that we aim to make the defaults the most desktop friendly for our users. HAL is very much needed for default friendly desktops nowdays. (In reply to comment #8) > ARCH teams, please consider adding "hal" to USE flag defaults since as per > discussions on my rants on the mailing list about extra USE flags came to say > that we aim to make the defaults the most desktop friendly for our users. HAL > is very much needed for default friendly desktops nowdays. > Eh!? It was already decided that use.defaults will be dropped afaik. ignoring the fact that we are dropping use.defaults, an arch-specific use.defaults is completely useless there should be only 1 use.defaults file |