LeithR wrote:I'm downloading LO6.1.4.pet from links in puppus dogfellow's thread { LibreOffice + language packs (latest version: 6.1.4)}. Where should I unpack it to? Or will it unpack itself correctly?
I don't know the dogfellow's thread (that you did not link in your message) but your question is as far absurd, really, that
*.pet's
as well as
*.sfs's
are both package to
unpack and link itself correctly changing if necessary the adequat pointers!
BUT
they don't always operate in each Puppy version!
in the
other precedent thread from you, I did explicitelly give to you the links to the adequat depositories for Slacko (Slacko was YOUR initial requirement!) for the very small Slacko 5.3.3!
you can't mix the versions totally free BECAUSE OF THE DEPENDENCIES!!!
if a supplementary (you don't really need LO / OO in Puppy: Abiword, gnumeric etc, the Gnome Office, are built in!!!) package don't work, try to invoque it in the terminal and the terminal will explain you what the system miss to start the application, generally one ... a lot of depoendencies (you can add those missing libraries if you find them as binaries), or, oh terror, an other C library base (nothing to do there: you have to change to an other Puppy version if you want to start THAT VERSION of your supplementary application, so a fresh LibreOffice etc... ; in that case is your Puppy to OLD for that version of the NEW application; it can also happen with new releases of high performance browsers like Seamonkey, Firefox etc.).
Note: if you will start an app in the terminal, you need to know the correct name of the binary or link to the binary in /usr/bin or /bin or /usr/local/bin ! Invoquing
WILL (probably) NOT WORK because the right short name of the binary (*1 is probably
depending of the *.pet or *.sfs (reason of my claim before, you don't indicate the source of your package clearly)...
in this case, you see, instead of an error message with the missed dependencies only the empty return message as following:
(*1 how to find those right short names? For CLI app's look in /bin or /usr/bin. For graphic applications, search the graphic app in /usr/share/applications, open the *.desktop file and search for the line including
"exec" or look in ~/.jwmrc build after loading the *.pet / *.sfs in the adequate line in the menu at the end of the line!