https://bugs.documentfoundation.org/show_bug.cgi?id=172590
Alberto Dietze <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |NOTABUG --- Comment #6 from Alberto Dietze <[email protected]> --- (In reply to Xisco Faulí from comment #5) > This is pretty much a duplicated of bug 169747. > As explained in > https://bugs.documentfoundation.org/show_bug.cgi?id=169747#c3, we could > setup a nightly bot with almalinux 8 to ensure it doesn't break there but > TDF is not going to offer two variants for the release builds. > > *** This bug has been marked as a duplicate of bug 169747 *** Hello Xisco; apologize myself, maybe my text wasn't clear enough, or I haven't fully understood the proposed "solution", but this is not a real duplicate of the mentioned issue. That was a bug report, this is an open request to TDF dev team to make a change in the official build process to include in the *only one main official release* (without doubling the release), the flag command to allow to run *official builds* on machine with CPU that doesnt support the x86-64-vX flags. As already said, this isn't a blocking point or a problem/incompatibility with other software to maintain as of today, but just a simple flag to do not discriminate users based on their machine, allowing them the freedom to use the main official version of LO, adopting the latest secure version of LO, without the lock-in situation of learning how to compile it from scratch, the need of a dedicated hardware to compile it. TDF should provide as much compatibility as possible without discrimination or raising barriers to adopt it's software. For the moment, and respecting your point of view, I have just updated in NOTABUG, and leaving RESOLVED, but I kindly wait a clarification in the "solution" proposed, just to be sure about the presence of possible misunderstandings, because till today, I haven't read about the reintroducing of that flag option. Thanks in advance. -- You are receiving this mail because: You are the assignee for the bug.
