openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus <marcus.m...@wtnet.de>
Subject Re: Wrong distro detected?
Date Sun, 14 Oct 2018 15:32:34 GMT
Am 10.09.2018 um 23:52 schrieb Marcus:
> Am 10.09.2018 um 23:29 schrieb Matthias Seidel:
>> Am 10.09.2018 um 23:19 schrieb Marcus:
>>> Am 10.09.2018 um 23:10 schrieb Matthias Seidel:
>>>> Am 10.09.2018 um 22:32 schrieb Marcus:
>>>>> Am 06.09.2018 um 22:06 schrieb Marcus:
>>>>>> Am 06.09.2018 um 17:37 schrieb Matthias Seidel:
>>>>>>> Am 05.09.2018 um 21:37 schrieb Marcus:
>>>>>>>> Am 02.09.2018 um 23:20 schrieb Pedro Lino:
>>>>>>>>>> On September 2, 2018 at 9:42 PM Rory O'Farrell <ofarrwrk@iol.ie>
>>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> It may be useful to know that the terminal command
>>>>>>>>>> inxi -S
>>>>>>>>>>
>>>>>>>>>> will display the distro name. I am sure there are
other
>>>>>>>>>> commands to
>>>>>>>>>> do so of which I am not aware.
>>>>>>>>>
>>>>>>>>> inxi is not included in Debian or Ubuntu. lsb_release
-a works
>>>>>>>>> But the browser is not allowed to run terminal commands
for 
>>>>>>>>> obvious
>>>>>>>>> reasons ;)
>>>>>>>>>> I have not yet (not looked very hard) found any command
that will
>>>>>>>>>> disclose if the distro needs RPM or DEB files
>>>>>>>>>
>>>>>>>>> We would have to create a table with such correspondence.
But the
>>>>>>>>> problem remains: there is no way to get information on
the Distro
>>>>>>>>> (except for Ubuntu's Firefox)
>>>>>>>>>
>>>>>>>>> The only solution seems to be Andrea's suggestion about
adding
>>>>>>>>> information when Linux is detected (this already happens
when
>>>>>>>>> Android
>>>>>>>>> is detected so the mechanism is already there)
>>>>>>>>
>>>>>>>> just an additional info instead of a (mandatory) choise is
indeed
>>>>>>>> worth to think twice. I'll do it on the weekend and play
a bit with
>>>>>>>> the download scripting.
>>>>>>>
>>>>>>> When you are at it... ;-)
>>>>>>>
>>>>>>> Did you have a chance to look at the needed changes for the updated
>>>>>>> Release Policy?
>>>>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127530
>>>>>>
>>>>>> yes, I know.
>>>>>>
>>>>>> However, this is more complex as we have a dependency with versions:
>>>>>>
>>>>>> If version == 4.1.5 or older,
>>>>>> then offer a link with the MD5 file.
>>>>>>
>>>>>> If version == 4.1.6 or newer,
>>>>>> then do not offer a link .
>>>>>>
>>>>>> I've to check how and where to insert this version check.
>>>>>>
>>>>>> But let's see ;-)
>>>>>>
>>>>>> Thanks for the hint.
>>>>>
>>>>> OK, also this is ready for testing. Let's wait for the CMS.
>>>>
>>>> Great!
>>>> How do you handle SHA? I understand that we should offer SHA512?
>>>
>>> SHA256 is unchanged and shown as before.
>>>
>>> Is the SHA512 hash data meanwhile integrated into the build process?
>>> As long as it is not I cannot add this to the download site. But if
>>> so, it's very easy to add it.
>>
>> Generating hash data is done manually after the build process, but we
>> have a scripts for it:
>> https://svn.apache.org/repos/asf/openoffice/devtools/release-scripts/
> 
> great, then the download scripting is awaiting the new hash data.

after the CMS is working again, I've now committed (but not yet 
published !) my changes to ask for feeback:

1) For versions until 4.1.5 (our current one) links for MD5 hash values 
are still offered but no longer for newer versions.

2) When Linux is choosen as platform, a new link "RPM vs. DEB = What to 
choose?" is offered. When hovering with the mouse a text is shown in 
which Linux distributions RPM and DEB packages are used.

Especially for topic #2, does it hit the spot?

Thanks

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message