In the interests of not making this thread a bunch longer, I am just going to answer a number of things here in one place. On 9/7/19 11:44 AM, Victor V. Shkamerda wrote: > I totally agree with that view. Making such decisions without public discussion is not respecting user's freedom of choice. And this list doesn't count as a public discussion. Nobody will know about it outside a very closed circle. If you don't know exact numbers or reasons why people still use that architecture, then rushing to drastic measures just won't have enough rationale and will be viewed as a lack of care. There was a lot of discussion on this list, in fesco tickets in fesco meetings, on phoronix, etc. I'm not sure what you mean by 'respecting users freedom of choice'. We cannot possibly provide all choices that anyone wants or thinks they want. Really it comes down to (in rough order of effectiveness): * Try and convince people doing the work to provide/continue to provide the thing you want, but realize that the people doing the work are under no obligation here, you need to convince them there is some reason they find compelling. * Offer to do some / part / all of the work, but realize here too you need to convince the people doing the work now that it's worth the time / resources to allow you to do the work (although this is a much better 'sell' than just convincing people. It's pretty clear that i686 is dwindling as an arch. It was pretty clear a few years ago when it was demoted to a alternative arch and the x86 sig was setup to try and work on issues that came up. No one really did so, so it's time to take the next steps. > What work should be done? Please, be more specific. Right now I'm > running a i686 userland and it works. If I would be able to build the > whole repository myself I'm pretty sure that most things will still > work. If it won't work I might try to fix it and contribute patches > back. But without that repository I can't even try it in the first place. Lets step back a step here. Why are you running a 32bit userspace? There's not really any advantage (and some disadvantages) to doing so. The koji buildroot repo will continue to be available if you want to copy something, but as far as work to be done to move back to distributing a i686 set of trees? I guess doing the release blocking tests on i686 at Beta and Final might be a good start, but thats a ton of work for one person... is there anyone else you have talked to that wants to do this? kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx