[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: I have an Openoffice question for small business.

Le 08.10.2013 16:14, berenger.morel@neutralite.org a écrit :

Le 08.10.2013 14:10, Ezequiel a écrit :

Hi all:

I am Sysadmin at a small business. We have a complete mail-web-vpn
infrastructure and my boss is happy with it. I guess we are a
successful case of open software use in the "real world"

But -of course, there is always an issue- my users keep complaining
about OpenOffice migration to Libre Office. They even complain if I
change OO from 3.2 to 3.3. I believe there were major changes in that 
version.
The question is: Is there any way of freezing OO version indefinetly?
I am currently using oldstable OO but I guess my time is going short. What will happen when they release the new version of debian? I don't 
know what to do...

Thanks in advance for any advices.

Zeke

PD: My native language is not English, I'm sorry for any mistakes in
my writing.


First, I do want to say that you should follow previous advice to try
to convince your users :)

But since you did not ask "how to convince my users to upgrade", here
is what you might want:
Use the /etc/apt/preferences file.

I used it some times ago but can not remember the exact syntax, but
you should be able to quickly find some samples on debian's forums.
Search for apt-pinning (the name of the technique iirc) and you should 
find nice examples in debian's forums. This technique is more often
used to only use some packages from testing/unstable/experimental on
stable, but you should be able to adapt it for your needs easily:
simply give very low priorities to the packages you want.

But you should know that it also means that OO (or LO) dependencies
will also need to be frozen, and this might avoid other other updates, 
in turn. Have fun :)


Sorry for my self reply, but I just thought of that:
Another solution, not the easiest one but which would avoid freezing dependencies, would be download source of OO and compile it ( not on all computers of course, only on yours ) and then distributing the binary through a package. To download source and install libraries needed, you can do something like: aptitude build-dep openoffice ( will install development libraries OO will need ) 
apt-get source openoffice ( will download source code for openoffice )
apt-get source will download an archive with source code, so untar it, and then probably do the old "./configure && make". Next steps is to build a package, but I can not help you on those, however a lot of people here can probably. And the last one is to distribute it. For that, you might want to setup a local repository, add your OO package in it, and add that repo to the sources.list ( or sources.list.d/local_OO.list, if you prefer ) of the desktops. That procedure is more complex than the one with file preferences, but can survive longer without giving you cascading version problems in future.
Reply to: