This is another static QT app, isn't it?_________________Classic Puppy quotes
-
root: n. the superuser or administrator account that has complete control over everything in the machine. Running as root is a taonga of Puppy Linux users.

Sorry to get off topic, but since you're making so many static packages, I'd like to ask:

Quote:

the advantages are reduced to no needing to install QT4 libraries

What other advantages would there be otherwise? Static packages eliminate the user's ability to try to run a program against incompatible libraries, but what else is there?

I think static packages are madness unless the user is only going to have one program which uses the library (so for very common dependencies like QT4 they will almost always be madness).

There are many disadvantages:
- all packages need to be updated if a bug in the static library is fixed
- larger downloads
- more hard disk space required
- more memory required, because you can run many programs using the same shared library, and it is only loaded into memory once*, but if you run many programs using the same static library then it is loaded into memory again for every single program (also note that when a upxed program is run, it is uncompressed to be loaded into memory), so if a user runs a number of these static QT apps then they will consume a significant amount of memory - not in the spirit of Puppy IMNSHO.

* Note that programs like top do not take this into account, so they report the memory usage of each program as including that of all shared libraries - so the actual physical memory usage will be less than the sum of that reported for all apps by top._________________Classic Puppy quotes
-
root: n. the superuser or administrator account that has complete control over everything in the machine. Running as root is a taonga of Puppy Linux users.

BTW, I presume you're familiar with the QT apps in this old thread?_________________Classic Puppy quotes
-
root: n. the superuser or administrator account that has complete control over everything in the machine. Running as root is a taonga of Puppy Linux users.

Joined: 11 Dec 2007Posts: 1433Location: somewhere at the end of rainbow...

Posted: Sat 06 Aug 2011, 06:52 Post subject:

yes I seen

the main purpose of making STATIC QT packages is giving ability to users of Puppy 2.14, 3.01, 4.3.x series, to use (if they need or want) to use packages otherwise not available for their puppy version, without needing to install additional QT4 libs or not available in their series or potentially dangerous for system (if they already have QT3)

QT STATIC are the *extrema ratio* for user, when he runs happily a good old puppy version but he need to use a program built on latest QT4 libs

let do an example: I run since 2007 Puppy 3.01, but when I need strictly a program built on latest QT4 libs, I start Lucid Puppy, compile STATICALLY and then, if it has no other relevant dependencies, I can use the program built statically in my good old Puppy 3.01 without fear to break system installing latest QT4 libs (if available), or crying because I can't build latest QT4 (that need a gcc newer than gcc contained in Puppy 3.01-4.3.1)

I also figured to insert a postinstall script in static qt packages, to ask in a x(gx) message window, if user want to move qt static executable outside puppy save, but then I preferred to not include; anyone can move outside puppy save if wants

all this because Puppy, we know, is different from Ubuntu that abandon users of old versions, while old puppies can be better than newer in many cases and in many hardwares and are worthy to support_________________replace .co.cc with .info to get access to stuff I posted in forum
dropbox 2GB freeOpenOffice for Puppy Linux

But surely if you've managed to compile a recent QT4 with static libs that work in an old Puppy, the dynamic libs would also work in it?_________________Classic Puppy quotes
-
root: n. the superuser or administrator account that has complete control over everything in the machine. Running as root is a taonga of Puppy Linux users.

Joined: 11 Dec 2007Posts: 1433Location: somewhere at the end of rainbow...

Posted: Sat 06 Aug 2011, 07:12 Post subject:

disciple wrote:

But surely if you've managed to compile a recent QT4 with static libs that work in an old Puppy, the dynamic libs would also work in it?

I remember that some time ago, when I tried to build latest QT4 libs on Puppy 4.3.1, I got an error message about gcc (too old)

since I'm planning to build newer QT4 just released in Lucid Puppy I'll try again compiling both statically and shared version to see compatibility in Puppy 4.3.1, of QT4 libs built in Lucid_________________replace .co.cc with .info to get access to stuff I posted in forum
dropbox 2GB freeOpenOffice for Puppy Linux

They probably aren't worse. But I thought the point of portablelinuxapps was that people could use them on any distro when they they don't have the permissions to install software in the normal way... which shouldn't be an issue here in "root forever" land._________________Classic Puppy quotes
-
root: n. the superuser or administrator account that has complete control over everything in the machine. Running as root is a taonga of Puppy Linux users.

The prettiest graphics tool available in Puppy, and not so expensive in MBs
Is that always true that fotowall can be used only with Lucid Puppies ? (2014)
Fotowall 1.0 Lucid 52 from Lucid package repository.
try it with Dpup exprimoGo and Try it

Fotowall.jpg

Description

Nice.

Filesize

93.53 KB

Viewed

27 Time(s)

Last edited by Pelo on Thu 11 Aug 2016, 12:50; edited 3 times in total

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum