| 1 |
On Thu, Nov 05, 2009 at 09:49:07AM +0100, Thilo Bangert wrote: |
| 2 |
> |
| 3 |
> > Perhaps the pragmatic approach might be wise. |
| 4 |
> > |
| 5 |
> |
| 6 |
> when filing the FEATURES bugs, i (IIRC) tried to remain on the pragmatic |
| 7 |
> side, recognising the sometimes non-existing alternatives. ie. i didnt |
| 8 |
> open bugs for each and every FEATURES usage. |
| 9 |
> |
| 10 |
> the tracker bug is here: |
| 11 |
> http://bugs.gentoo.org/show_bug.cgi?id=174335 |
| 12 |
|
| 13 |
While I appreciate you being pragmatic in your cleanup efforts, you |
| 14 |
miss the point of my post- while FEATURES reliance needed a valid |
| 15 |
reason from a QA standpoint, it was *valid* from a format standpoint |
| 16 |
prior to paludis/PMS (and was the only option in some corner cases |
| 17 |
ebuild wise). |
| 18 |
|
| 19 |
The response these days when it comes to FEATURES is that you cannot |
| 20 |
rely on it's existance ever- this loops back to my point about |
| 21 |
pragmatism. |
| 22 |
|
| 23 |
I understand PMS/paludis wishing to duck the vars existance to make it |
| 24 |
go away, but I don't think it's a tenuable approach- as you yourself |
| 25 |
said above, in trying to do this cleanup you recognized that sometimes |
| 26 |
there was no alternative. |
| 27 |
|
| 28 |
Please understand my point here is QA; not picking a fight. That |
| 29 |
said, paludis doesn't do anything FEATURES wise due to PMS not |
| 30 |
mandating they do so... as you said, certain ebuilds rely on it's |
| 31 |
existance to work. |
| 32 |
|
| 33 |
This means via PMS being incomplete, paludis isn't going to play nice |
| 34 |
in those cases (corner case- if the user defines the var themselves in |
| 35 |
their config, this would address it). |
| 36 |
|
| 37 |
Essentially, you can't use FEATURES but you have to in some cases. |
| 38 |
Doing so however doesn't necessarily play nice w/ paludis due to |
| 39 |
stepping outside of PMS. Classic catch 22. |
| 40 |
|
| 41 |
Rather then letting the problem persist, I'd rather see folk take a |
| 42 |
look at FEATURES/PMS and identify what needs to be pushed in to take |
| 43 |
care of the cases where there is no alternative to 'hasq some-feature |
| 44 |
$FEATURES' rather then us just collectively sticking our heads in the |
| 45 |
sand. |
| 46 |
|
| 47 |
Grok? |
| 48 |
|
| 49 |
Or we can just keep ignoring the problem pretending it's a user config |
| 50 |
issue rather then a format level issue... |
| 51 |
~harring |
Archives