Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

On 10/08/2013 01:48 PM, Jay Lozier wrote:
On Tue, 2013-10-08 at 13:22 -0700, Girvin Herr wrote:
I am coming late to this thread, but this talk of a "single-button"
install scares me.  I take the downloaded Linux binary LO package and
re-package it into a Slackware Linux installation package.  I use a
script I created to do this and all I have to do when a new LO release
comes out is to change the version and run the script.  Out comes a
Slackware package, ready for installation.  I surely hope that any
effort going to a single-point installer for LO, which would probably
break my process, will not be the only way to install LO in the future,
and the current installation scheme will still be an option.
Girvin Herr

What I have seen with Linux "one-click" installers is they actually
invoke the distro software installer. This requires user confirmation
before the install occurs (password entry). So it is as secure as any
other package installation. The "one-click" installers are normally
distro (distro family) specific.

Currently I have two versions of LO installed, one from the repository
and a downloaded version.

Yes, Slackware calls its install system "pkgtools", which includes the "installpkg", "removepkg", and "upgradepkg" command line tools. My concern is that the LO developers will create their own installer, which could make it tough for me to repackage the LO distributions, depending on how they implement it. Of course, I could always compile the source code, but that can be another can of worms and it takes a lot longer to compile LO than to just repackage the already compiled binary. I am not sure what your definition of "distro" is in your reply above. It could mean the LO distro or the Linux distro, in my case Slackware.

I do not like using supplied package installers. The only one I know of and do use is the Adobe Acrobat Reader installer. Every time I use it, I shudder because I do not know exactly what is going on in there. Computer security is a high priority with me and I generally do not install such programs unless I have no choice, such as with AR. Generally, such package installers need to be run as root and that is a no-no with me. Luckily, so far, AR's installer has been just an extractor and does not need to be run as root, so I can run it in user mode, repackage the extracted binary into a Slackware package and then install that as root. So far, I have been lucky there. It is a matter of who do I trust.
Take care.
Girvin Herr

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.