Re: Windows Installer translation
At 14:01 23/02/2020 +0100, Peter Kovacs wrote: We are discussing from time to time, that it might be worth to remove the packaging to the exe completely. To my knowledge in the past we did create an exe because you could not doubleclick msi files. But Microsoft had fixed this for quite some time and there is no real reason to keep the exe packaging. So any objections? I'm no expert, but my understanding is that the .msi file is a database, required just as much during removal of any product as during installation. My impression is that products such as Microsoft Office quietly salt away a copy of the .msi file (or as much as is needed) and Windows uses this when the product is removed. Failing that, Windows remembers where the .msi file was during installation and seeks it out, asking for it if necessary. And all this applies when removal is effected by installing a later version, doesn't it? Now the user may have thought (or even been told) that, once the product is installed, the downloaded files are no longer needed and may have deleted them. This used to result in a steady stream of requests to the Users list, asking how the new version can be installed when the process stalls at this point. Indeed, as recently as ten days ago, a user trying to install a current version reported to the Users list "Every time I try I get a message to insert the Open Office.org 3.2 disk". He must have installed the older version from a CD - which he may well no longer have. Will distributing .msi files result in the same problem to occur again? Or is OpenOffice now prepared similarly to salt away the necessary parts of the installation database? If not, what was (and is) the cause of the problem, please? Brian Barker - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Windows Installer translation
Hi Andrea, Am 23.02.20 um 22:59 schrieb Andrea Pescetti: > Peter Kovacs wrote: >> To my knowledge in the past we did create an exe because you could >> not doubleclick msi files. >> But Microsoft had fixed this for quite some time and there is no real >> reason to keep the exe packaging. >> So any objections? > > No objections at all on my side, provided we continue to offer the > same user experience to Windows users who start the installation. > > As discussed at FOSDEM, this has the additional advantage that, if one > wants to sign binaries and installation files, there is one less file > to sign. That said, I am the only one from our project with access to the Code Signing Service (Jims account is still pending). But I see that you have an inactive account. Would you still be interested? Regards, Matthias > Of course, as usual someone has to do the work and time is scarce... > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Windows Installer translation
Hi Peter, all > On February 23, 2020 1:01 PM Peter Kovacs wrote: > > > We are discussing from time to time, that it might be worth to remove the > packaging to the exe completely. > > To my knowledge in the past we did create an exe because you could not > doubleclick msi files. > But Microsoft had fixed this for quite some time and there is no real reason > to keep the exe packaging. > > So any objections? None at all! This would solve the confusing message on the installer, the messy temporary folder on desktop and the msi files are more secure than exe files, plus it would require signing only one less binary per language (as Andrea mentioned) If voting is needed, +1 Kind regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Windows Installer translation
Peter Kovacs wrote: To my knowledge in the past we did create an exe because you could not doubleclick msi files. But Microsoft had fixed this for quite some time and there is no real reason to keep the exe packaging. So any objections? No objections at all on my side, provided we continue to offer the same user experience to Windows users who start the installation. As discussed at FOSDEM, this has the additional advantage that, if one wants to sign binaries and installation files, there is one less file to sign. Of course, as usual someone has to do the work and time is scarce... Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Windows Installer translation
We are discussing from time to time, that it might be worth to remove the packaging to the exe completely. To my knowledge in the past we did create an exe because you could not doubleclick msi files. But Microsoft had fixed this for quite some time and there is no real reason to keep the exe packaging. So any objections? All the best Peter Am 23. Februar 2020 12:55:10 MEZ schrieb Pedro Lino : >Hi Matthias > >Thank you for the fast answer! > >> See: >> https://bz.apache.org/ooo/show_bug.cgi?id=127628 >> >> I am pretty sure I wrote with you about that longer ago... > >I'm well aware of that bug. I commented on it in 2018... >Ideally this should be fixed first but since I'm not a developer, I can >only help with what I can do. > >> What you probably see in the first part of the installation are now >> strings from NSIS. > >There are mistakes/inconsistencies also in the AOO specific texts. > >> Of course you can try to correct this at the NSIS project. [1] > >I downloaded the source and yes, there is plenty of translation work >there too... > >> But normally you should not see them at all, because they are >replaced >> with the strings from Pootle. > >Can we mark that bug as a blocker for 4.2? Does anyone currently >working on AOO have the time/skills to fix this? > >> I would rather vote for fixing this old bug! ;-) > >+1 > >Kind regards, >Pedro > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Windows Installer translation
Hi Pedro, Am 23.02.20 um 12:55 schrieb Pedro Lino: > Hi Matthias > > Thank you for the fast answer! > >> See: >> https://bz.apache.org/ooo/show_bug.cgi?id=127628 >> >> I am pretty sure I wrote with you about that longer ago... > I'm well aware of that bug. I commented on it in 2018... > Ideally this should be fixed first but since I'm not a developer, I can only > help with what I can do. I am also no developer ;-) But I tried to look into it and if I could do it it would have been fixed long ago. > >> What you probably see in the first part of the installation are now >> strings from NSIS. > There are mistakes/inconsistencies also in the AOO specific texts. Then fix it in Pootle? All texts should be there. If not, please point me to the missing parts. > >> Of course you can try to correct this at the NSIS project. [1] > I downloaded the source and yes, there is plenty of translation work there > too... > >> But normally you should not see them at all, because they are replaced >> with the strings from Pootle. > Can we mark that bug as a blocker for 4.2? Does anyone currently working on > AOO have the time/skills to fix this? Everyone can ask for release blocker flag in Bugzilla. But this is no serious bug and we obviously have no developer to fix it. > >> I would rather vote for fixing this old bug! ;-) > +1 Why don't you put your vote in Bugzilla? ;-) Regards, Matthias > > Kind regards, > Pedro > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Windows Installer translation
Hi Matthias Thank you for the fast answer! > See: > https://bz.apache.org/ooo/show_bug.cgi?id=127628 > > I am pretty sure I wrote with you about that longer ago... I'm well aware of that bug. I commented on it in 2018... Ideally this should be fixed first but since I'm not a developer, I can only help with what I can do. > What you probably see in the first part of the installation are now > strings from NSIS. There are mistakes/inconsistencies also in the AOO specific texts. > Of course you can try to correct this at the NSIS project. [1] I downloaded the source and yes, there is plenty of translation work there too... > But normally you should not see them at all, because they are replaced > with the strings from Pootle. Can we mark that bug as a blocker for 4.2? Does anyone currently working on AOO have the time/skills to fix this? > I would rather vote for fixing this old bug! ;-) +1 Kind regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Configuration
Hi, Am 23.02.20 um 10:14 schrieb Maram Abbas: > I am using cygwin 2.9 No, you don't. 2.9 is just the version of your Cygwin setup.exe. According to your log you are using Cygwin 3.1.2: "CYGWIN_NT-6.1 moram-PC 3.1.2(0.340/5/3) 2019-12-21 15:25 x86_64 Cygwin" Apparently you are using Cygwin in 64-bit. > Building aoo 4.1.7 You can *not* build AOO 4.1.x with Cygwin64, you need Cygwin32 for that. See: https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10 Above page is also mentioned in my build configuration: https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ReadMe.txt Regards, Matthias > And I have the same problem even when I write all configurations > بتاريخ ٢٢/٠٢/٢٠٢٠ ١١:٢٢ ص، كتب "Maram Abbas" : > >> Hello >> I am trying to build aoo in windows 7 >> I followed the instructions mentioned >> But I have problem at the configure >> I think it is with the dmake url >> >> $ ./configure --with-dmake-url=" >> https://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2 >> " >> checking whether configure is up-to-date... yes >> >> * * >> * Apache OpenOffice build configuration. * >> >> * * >> * The configure process checks your platform to see whether * >> * you can build Apache OpenOffice on it. * >> * This process checks all pre-requisites and generates a file* >> * containing the necessary environment variables.* >> * Source this file after configure has ended successfully. * >> * * >> * Warnings that are generated during the configure process * >> * must be taken into account since it can be a reason for* >> * an unsuccessful build of Apache OpenOffice.* >> * * >> >> >> >> * * >> >> * Checking the platform pre-requisites. * >> * * >> >> >> checking for grep that handles long lines and -e... /usr/bin/grep >> checking for egrep... /usr/bin/grep -E >> checking for gawk... no >> checking for mawk... no >> checking for nawk... no >> checking for awk... awk >> checking for awk... /usr/bin/awk >> checking for sed... /usr/bin/sed >> checking for solenv environment... default >> checking for custom pack.lst... no >> checking build system type... x86_64-pc-cygwin >> checking host system type... x86_64-pc-cygwin >> checking target system type... x86_64-pc-cygwin >> cygwin >> checking Cygwin version... 3.1.2(0.340/5/3) >> head: cannot open '/etc/*-release' for reading: No such file or directory >> CYGWIN_NT-6.1 moram-PC 3.1.2(0.340/5/3) 2019-12-21 15:25 x86_64 Cygwin >> checking for pkg-config... /usr/bin/pkg-config >> checking pkg-config is at least version 0.9.0... yes >> checking whether to enable crashdump feature... no >> checking whether to use the standard non-optimizing compiler... no >> checking whether to build/use the Windows 64bit shell extensions... no >> checking whether to build 64 bit OpenOffice on 64 bit Windows... no >> checking whether to turn warnings to errors... no >> checking whether to do a debug build... no >> checking whether to build with additional debug utilities... no, full >> product build >> checking whether to include symbols into final build... no >> checking whether to strip the solver or not yes >> checking whether to enable category B components... no: disabled modules >> nss, hunspell, hyphen, saxon, rhino, graphite, coinmp >> checking whether to enable the Online Update support... yes >> checking whether to enable unit tests... yes >> checking whether to enable native CUPS support... no >> checking whether to enable fontconfig support... no >> checking whether to use DirectX... yes >> checking whether to use ActiveX... yes >> checking whether to use ATL... yes >> checking whether to use RPATH in shared libraries... yes >> checking whether to use dicts from external paths... no >> ./configure: line 6433: test: too many arguments >> ok >> checking for cygwin gcc/g++... found >> checking for bash... /usr/bin/bash >> checking gcc home... /usr >> checking whether to enable pch feature... no >> checking for GNU make... make >> checking the GNU make version... make 4.2.1 >> 3+: >> checking for dmake... configure: no system or user-provided dmake found >> dmake will be downloaded
Re: Configuration
Maram Abbas wrote: checking for dmake... configure: no system or user-provided dmake found dmake will be downloaded and compiled in bootstrap checking for GNU or compatible BSD tar... configure: error: not found. install GNU tar. You need to have tar available. The error is not related to dmake this time. On Windows, tar is part of your Cygwin packages. I recommend that you subscribe to the mailing list if you haven't already, or you might miss answers: https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Configuration
I am using cygwin 2.9 Building aoo 4.1.7 And I have the same problem even when I write all configurations بتاريخ ٢٢/٠٢/٢٠٢٠ ١١:٢٢ ص، كتب "Maram Abbas" : > Hello > I am trying to build aoo in windows 7 > I followed the instructions mentioned > But I have problem at the configure > I think it is with the dmake url > > $ ./configure --with-dmake-url=" > https://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2 > " > checking whether configure is up-to-date... yes > > * * > * Apache OpenOffice build configuration. * > > * * > * The configure process checks your platform to see whether * > * you can build Apache OpenOffice on it. * > * This process checks all pre-requisites and generates a file* > * containing the necessary environment variables.* > * Source this file after configure has ended successfully. * > * * > * Warnings that are generated during the configure process * > * must be taken into account since it can be a reason for* > * an unsuccessful build of Apache OpenOffice.* > * * > > > > * * > > * Checking the platform pre-requisites. * > * * > > > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for gawk... no > checking for mawk... no > checking for nawk... no > checking for awk... awk > checking for awk... /usr/bin/awk > checking for sed... /usr/bin/sed > checking for solenv environment... default > checking for custom pack.lst... no > checking build system type... x86_64-pc-cygwin > checking host system type... x86_64-pc-cygwin > checking target system type... x86_64-pc-cygwin > cygwin > checking Cygwin version... 3.1.2(0.340/5/3) > head: cannot open '/etc/*-release' for reading: No such file or directory > CYGWIN_NT-6.1 moram-PC 3.1.2(0.340/5/3) 2019-12-21 15:25 x86_64 Cygwin > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking whether to enable crashdump feature... no > checking whether to use the standard non-optimizing compiler... no > checking whether to build/use the Windows 64bit shell extensions... no > checking whether to build 64 bit OpenOffice on 64 bit Windows... no > checking whether to turn warnings to errors... no > checking whether to do a debug build... no > checking whether to build with additional debug utilities... no, full > product build > checking whether to include symbols into final build... no > checking whether to strip the solver or not yes > checking whether to enable category B components... no: disabled modules > nss, hunspell, hyphen, saxon, rhino, graphite, coinmp > checking whether to enable the Online Update support... yes > checking whether to enable unit tests... yes > checking whether to enable native CUPS support... no > checking whether to enable fontconfig support... no > checking whether to use DirectX... yes > checking whether to use ActiveX... yes > checking whether to use ATL... yes > checking whether to use RPATH in shared libraries... yes > checking whether to use dicts from external paths... no > ./configure: line 6433: test: too many arguments > ok > checking for cygwin gcc/g++... found > checking for bash... /usr/bin/bash > checking gcc home... /usr > checking whether to enable pch feature... no > checking for GNU make... make > checking the GNU make version... make 4.2.1 > 3+: > checking for dmake... configure: no system or user-provided dmake found > dmake will be downloaded and compiled in bootstrap > checking for GNU or compatible BSD tar... > configure: error: not found. install GNU tar. > > Any help knowing what am I missing hear >
