[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: let's play a game: what does dnf not support?

On 01/14/2015 09:50 AM, David Shea wrote:
On 01/13/2015 05:01 PM, Adam Williamson wrote:
On Fri, 2015-01-09 at 17:37 -0500, David Shea wrote:
Now that dnf is the default, you may have noticed, hey, there's some
stuff missing! Let's figure out what all is missing. Here's what
I've found so far:

environment selection is weird and busted (there's a patch on the
list) can't use "harddrive" in kickstart
repo files written with --install are missing most of that but do
have proxy (URL only) and cost
no %packages --multilib (I think clumens is working on or maybe
already finished that)
no lang --addsupport (waiting on dnf-langpacks to support having a
config file)
mirrorEnabled always returns true which seems pretty minor after all
of that stuff

Should we collect all these things somewhere? What other things have
Something in the stack needs to handle comps' 'display_order' for
environment groups, but nothing does:


this is why you get 'Cloud Server' as the default selected group in
current Rawhide installs.

I threw it at libcomps, jluza threw it at dnf (jsilhan), and there (so
far) the blame game rests. It should really be a release blocker
(probably Beta, possibly Alpha) but I need to get a criterion revision
finished first.

Is display_order accessible via libcomps? Because that's probably something that anaconda should use when generating the display. We used to do that, but quit doing that in new UI.

But with ordering comps environments, there's another question: why not just put it in the right order in the first place? It's not you like can change display_order per-product.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]