Auto. Menu kit for Tiny Core Linux`s SCM app. files.

[sunburnt]

This is scm_kit to make Tiny Core Linux`s SCM files work in Puppy.
Tiny Core has quite a few SCM files of popular apps.
SCM files are mounted but not unioned, so they don`t add union layers,
or take up Save file space like standard legacy app. packages do (.pet ).

# I`ve tried the kit with a number of SCM files and all worked.
My scm_kit needs further testing.
And more testing of SCM file compatibility while running in Puppy Linux.

### To run the menu in rxvt or vterm type: scm_menu-bar.gtk3 &
# Maybe a desktop icon for the menu would be good, or auto. run?

SCM apps. can also be run CLI if a PATH is added in: /etc/profile.local
Like this: [ -e /apps ]&& PATH=$PATH:/apps/bin ; export PATH
I did not include the file as it would overwrite existing profile.local files.

# This is the link to TC`s repository of SCM files:
http://distro.ibiblio.org/tinycorelinux/4.x/x86/scm/

### Put downloaded SCM files on any HD or USB device in a dir.: /scm
# Burned SCM files in /scm on a CD or DVD drive are found also.
----- NOTE: A terrible way to access files, wears out your optical drive.

### I`ll work up a way to copy SCM files to ram, Puppy style...

This is a simple ZIP file, extract it at / , or in a dir. and then move it.
The root dir. in the zip file is /root where all the kit`s files are.

### After installing the kit, manually run: /root/Startup/scm.start
It will start itself at each boot up of your PC.

###########################################################
# I have found inconsistencies in SCM files and some don`t work in Puppy.
# Did not work for me: gnome-mplayer.scm, avidemux.scm ( has no /bin ).
# I`ll talk to Jason W. and see if this and other things can be corrected.

#####>>> New version: scm_kit-2
Shows app. icons on menu "scm_menu-bar.gtk3".
Also has simple menu "9menu", it has no icons. Run file: "scm.9menu".
Does not need /apps/bin in $PATH for menus to work, just for CLI.
Finds /scm dir. on CDs and DVDs and adds SCM files to menus.

[sunburnt]

Here`s a current list of SCM files at: http://distro.ibiblio.org/tinycorelinux/4.x/x86/scm/

• ImageMagick.scm --------- getFlash11.scm ---------- pidgin-minimal-locale.scm
  abiword.scm -------------- gimp2-basic-locale.scm -- pidgin-minimal.scm
  asunder.scm -------------- gimp2-basic.scm --------- python-2.7.scm
  audacious-gtk2.scm ------ git.scm ------------------- python-3.2.scm
  audacious-gtk3.scm ------ gnome-mplayer.scm ----- qmmp.scm
  audacity-1.3-locale.scm - gqview2.scm ------------- qtfm.scm
  audacity-1.3.scm -------- gtk-gnutella-gtk2.scm --- ripperx.scm
  audacity2-locale.scm ---- gtk2-locale.scm --------- rox-filer.scm
  audacity2.scm ----------- gtk2.scm ---------------- seamonkey.scm
  avidemux.scm ------------ gtk3-locale.scm -------- stella.scm
  cdrtools.scm ------------ gtk3.scm ---------------- supertux.scm
  chromium-browser.scm -- icecat.scm -------------- tar-locale.scm
  clamav.scm -------------- l3afpad.scm ------------- tar.scm
  dejavu-fonts-ttf.scm ---- leafpad.scm ------------- thunderbird.scm
  easytag.scm ------------- libreoffice3.5.scm ------ transmission-gtk3.scm
  emelfm2-gtk3.scm ------- lilypond.scm ------------ vlc.scm
  emelfm2.scm ------------- links2.scm -------------- wget.scm
  epdfview.scm ------------ midori-locale.scm ------- wine.scm
  ffmpeg-static-dev.scm --- midori.scm -------------- xarchiver.scm
  ffmpeg-static.scm ------- minefield8.scm ---------- xchat2.scm
  firefox.scm -------------- minefield9.scm ---------- xfe.scm
  flburn.scm --------------- mldonkey.scm ----------- xine-xvesa-i486.scm
  foxit-reader.scm -------- mtpaint.scm ------------- xine-xvesa-i686.scm
  frozen-bubble.scm ------ oo2.scm ---------------- xmms.scm
  geany.scm --------------- openssl.scm ------------ xpdf.scm
  geeqie.scm -------------- opera-11.scm

No HandBrake!!! I gotta have a talk with them...
.

[nooby]

Very interesting. Keep up the good work
I have to test this ASAP but have to run now.

[jpeps]

Hello sunburnt,

I would be far more interested in seeing the specific linux code involved than using packages from another distro. If it makes sense, there's no reason that other packaging formats couldn't be adopted in puppy, particularly if there are advantages to doing so.

[sunburnt]

Hi jpeps; I designed the SqApp package, it`s about the same as SCM files.

### Improvements of SqApp files:
# I put the main app. exec. scripts and icons in the Squash file`s root.
SCM files have them in /bin and /share/pixmaps.
Having all the needed files in the Squash file`s root just makes it simpler.
# Also SqApp files are setup to auto. mount when run, and unmount at exit.
This reduces the number of mounts that the O.S. has to handle.
# The SqApp apps. have their config. files replaced with links to: /usr/etc
App. config. files are copied from: /(SqApp MntPt)/conf to: /usr/etc
All of an apps. config. files are named (App.Name)_(Config.File).
This makes them easy to find and remove by their prefix (App.Name).
Upon removing the SqApp file, first all it`s config. files are deleted.

"Mount but do not union" Squash files were done in ChoicePup years ago.
Any union file system has duplicate file ( lib.) problems, and others...

The method of build is as follows:
The source files are setup normally and are configured like this:

Code: Select all

configure --prefix ( SqApp Mount Pt.)

This sets the path that the app. is compiled to, and it`s also the path
that the app. expects to find it`s dependencies at.
Then "make" and "make install" are run normally.
Then make a Squash file from the prefix dir. with special run files in it.

Static compiling makes any app. package more robust.
The more that`s in the package, the more Linux distros it`ll work with.
That`s why all the SCM files I`ve tried in Puppy worked. Lots in them.
I suggested that Puppy be made with most very common libs. in it.
At least have a few "devx like" add-on files, media libs. (gstreamer), etc.
And any not so common ones are compiled into the app. packages.

I have a statistical analysis of lib. package usage, it`s rather interesting.
Few lib. packages are very common, most are small and seldom used.

[jpeps]

Looks like you need an exec script for every app that includes PATH & LD_LIBRARY_PATH. So basically just a mounted static squash file. I can see why TC would be attracted to that, given such a minimal base (although they don't seem to be including libs already in base).

My preference is to keep everything in standard locations, and simply add or delete from the package to fit (for that I use petcheck).

[sunburnt]

jpeps; Looked at some SCM files and some do set PATH and LD_LIB_PATH.

The only "holes" compared to SFS files is the conifg. files need to be copied.
And for CLI, the app`s. exec. files are in /apps/bin which needs to be in $PATH
Compared to legacy .tar.gz and .pet files, file tracking isn`t needed at all.
The file`s names are prefixed with the app`s. name, so they`re easy to find.

[RSH]

I was able to load a .scm application (audacious) and to run it from inside the mounted directory.

But your menu application fails.

Code: Select all

./scm_menu-bar.gtk3: line 23: /apps/scm.mnu: no such file or directory
  <menuitem icon="">
    <label></label>
    <action>/apps/bin/ &</action>
  </menuitem>

-------------------
(program exited with code: 0)
Press return to continue

** ERROR **: gtkdialog: Error in line 11, near token '</label>: syntax error

aborting...
'

Did i something wrong? How do i use this?

EDIT:

Code: Select all

/apps/bin/$F.hook &		# run exec. hook file

This file is also missing in the .zip file. Gives error message: no file/directory. File: scm.load

[sunburnt]

RHS; These files: scm.mnu and the app`s. exec. files are made by the scm.setup file.
It searches all the partitions for /scm/*.scm files and makes the needed files.

As my post says, run the scm.setup file after installing the kit.
The scm.setup file goes into the dir.: /root/Startup and is run at each boot-up.

# ToDo:
I need to make a "refresh" to re-search the /scm dirs. for files after changes.
And I need to code a way to copy the SCM files to ram and run them there.

[RSH]

I don't get your scm-menu to work.

However, i did make some work on your scm.load script to load the scm files with right-click action and/or GUI (file-selector). Works fine.

But i found, that there is only support for 3 (three) Mountpoints. Is that right?

If, than it's not really usable for me and for what i am planning to do (currently working on).

[sunburnt]

RHS; I assume you ran the scm.setup file? It won`t work without it.
I assume you put your SCM files in a /mnt/(Drive-MntPt)/scm dir.?
And Linux should support dozens of mounts, maybe your loops are limited.
Puppy use to support only 8 loop devices, but I think Barry raised it.

NOTE: Puppy has 11 loop devices, and uses 3 with the devx file, leaving 8.
I`ll make a function in scm.setup to make more loop devices, perhaps 30.