Self Contained Mountable... applicaton extensions. SCM

For discussions about programming, programming questions/advice, and projects that don't really have anything to do with Puppy.
Post Reply
Message
Author
nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

Self Contained Mountable... applicaton extensions. SCM

#1 Post by nooby »

Jason at TinyCore has come up with this thing.
Would be cool if the Puppy Developers commented
on if it could be implemented to Puppy of if SFS is
the same thing only under another name?

RobertS tells about it here
http://forum.tinycorelinux.net/index.ph ... l#msg67363

and Jason himself tells about the basics of SCM here
http://forum.tinycorelinux.net/index.ph ... l#msg67393
and read this one too or the whole thread.
http://forum.tinycorelinux.net/index.ph ... l#msg67403
the scm is just a simple putting back into practice
the compressed mountable image - .uci - that Robert
pioneered many years ago which I am personally getting
once again hooked on.
I like that it can be a safe playground where we can go
ahead and use gtk3, python3, other new things, etc,
without having to wait on a migration in the tcz area.

Don't get me wrong, I plan to maintain my tcz extensions,
and the tcz area remains of utmost importance as it is our
'system', whereas the scm's are self contained and
basically affect nothing else outside themselves.
I'm a noob so I have no idea what they talk about but
it sounds interesting so would be cool to get different views on it.

Is it like SFS and if it differs how does it differs? :)
I use Google Search on Puppy Forum
not an ideal solution though

jpeps
Posts: 3179
Joined: Sat 31 May 2008, 19:00

#2 Post by jpeps »

Just create a pet where everything installs into it's own directory, with links to system directories. It looks way to cumbersome to me. I think a far better approach is just to make sure that core systems files aren't getting overwritten. I think we already have built in protections.




Jason's directions for building leafpad (typos left in)
"When building an scm, you do not need to use a DESTDIR variable, just use the ./configure flag "--prefix=/apps/l3afpad"
Code: [Select]

export LDFLAGS="-L/apps/l3afpad/lib -L/apps/gtk3/lib"
export CPPFLAGS="-I/apps/l3afpad/include -I/apps/gtk3/include"
export PATH="/apps/l3afpad/bin:/apps/gtk3/bin:$PATH"
export PKG_CONFIG_PATH="/apps/l3afpad/lib/pkgconfig:/apps/gtk3/lib/pkgconfig:$PKG_CONFIG_PATH"

User avatar
sunburnt
Posts: 5090
Joined: Wed 08 Jun 2005, 23:11
Location: Arizona, U.S.A.

#3 Post by sunburnt »

This is the manner in which you make "non-unioned" Squash files.
I suggested this awhile back at the Tiny Core Linux forum to simplify T.C.
I suggested it here years ago to simplify Puppy Linux also.

So a Squash app. package is ready to use like an SFS, no install or removal.

One of the better things about SFS files, they don`t "over-write".

User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#4 Post by technosaurus »

Rox apps ... Amigo has a whole collection of them.

Keep in mind there are various dependencies on having things in certain places ... Fonts, icon sets... Do we really want to distribute all of these kinds of things in multiple packages?
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

#5 Post by amigo »

Somewhere here I have a thing which someone came up with, where packages are created like ROX AppDir, except the AppRun script is replaced with a small binary which mounts the rest of the content which is contained in an ISO image. Great idea which never cuaght on in a big way. The concept of AppDirs is really nice -especially for things which use non-standard paths. They fit perfectly within the usage of /opt. The manner of making them available and workable is a different matter -I mean union-mounting them, or simply installing them and creating links, etc.

To me there is nothing wrong with the concept of sfs. The problem as implemented by Puppians is the idea that all depedendencies should be included. This goes against the basic principles of system sanity and manageability as it means that system libs get overwritten (or over-mounted as the case may be), and that things get unnecessarily duplicated, and that updates (from the developers standpoint) are more difficult.

AppDirs for *applications* (not libraries) are a great way to achieve easy modularity without having to use package management. The method of making them easily and flexibly available is another matter.

jpeps
Posts: 3179
Joined: Sat 31 May 2008, 19:00

#6 Post by jpeps »

I like the idea of loading only what's needed, which varies depending on what's already loaded. Petcheck does that. The rest is theoretical. The user doesn't see any difference that I'm aware of.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#7 Post by nooby »

I'm a poor reader. Doesn't Core almost always get a fresh
version so one are dependent on the repo to be available
online or offline.

Sure one can most likely place a lot of files on the HD
and load off line?
I use Google Search on Puppy Forum
not an ideal solution though

Post Reply