WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: SCM Basics  (Read 14999 times)

Offline jls_legalize

  • Hero Member
  • *****
  • Posts: 1370
    • Core17
Re: SCM Basics
« Reply #90 on: July 24, 2012, 12:03:20 PM »
Code: [Select]
export LD_LIBRARY_PATH="/apps/gtk3/lib"
export XDG_DATA_DIRS=/apps/gtk3/share
cannot this two variables be setted by gtk3 itself so we can avoid to make wrappers?


legalize them                                     ThisIsNotlYnuCsfrOmscR-Etch

Online gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 3350
Re: SCM Basics
« Reply #91 on: July 24, 2012, 12:11:02 PM »
That would break the isolation between SCMs.

Offline jls_legalize

  • Hero Member
  • *****
  • Posts: 1370
    • Core17
Re: SCM Basics
« Reply #92 on: July 24, 2012, 01:02:12 PM »
could you make an example?
legalize them                                     ThisIsNotlYnuCsfrOmscR-Etch

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7082
Re: SCM Basics
« Reply #93 on: July 24, 2012, 03:48:02 PM »
LD_LIBRARY_PATH and XDG_DATA_DIRS is used by the app that is looking for the libs, so nothing can be done from within gtk3.scm that will allow other scm's to find it's libs.   

Offline jls_legalize

  • Hero Member
  • *****
  • Posts: 1370
    • Core17
Re: SCM Basics
« Reply #94 on: July 24, 2012, 04:01:37 PM »
cannot this variables be exported  globally by gtk3.scm?
legalize them                                     ThisIsNotlYnuCsfrOmscR-Etch

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7082
Re: SCM Basics
« Reply #95 on: July 24, 2012, 04:45:52 PM »
I believe I remember with the previous distribution ld.so.conf had the library paths of self contained apps added to it so they would be recognized. 

But one of the goals of the scm is not to interfere with the system, or be interfered with by other extensions by means of using the libs and binaries contained in the scm itself, or the target scm like gtk3.  Which means using wrappers for some binaries.  It can be a pain, but it should make for few if any conflicts between extensions.

Offline cast-fish

  • Hero Member
  • *****
  • Posts: 608
Re: SCM Basics
« Reply #96 on: July 25, 2012, 10:53:50 AM »
Hello

that is sounding so ridiculously complex.....


i know from my own experience of win32  that "software conflicts" is a continual ongoing
problem 24 seven when using the OS and APPS   "dll..."   "hell....."     (lots and lots and lots
of the architecture simply does not work right)

You can barely ever have 3 or 4 apps before typical problems arise.....not sure about the

newer multi tasking chips, but perhaps it's even worse with them....?

anyhow,

Tinycore is totally different isn't it.  Light years away

Vince.






aus9

  • Guest
Re: SCM Basics
« Reply #97 on: April 02, 2013, 09:11:49 PM »
Hi

I can't find a howto in the wiki, if this is the main howto, any chance you can make this a sticky at page one?

ALSO you may wish to make this post a sticky?  allowed dependencies

http://forum.tinycorelinux.net/index.php/topic,12681.0.html

I am thinking of having a go at making a scm but at the moment this is the only post I can find that might be useful.

It seems to me, that those with low spec machines would prefer an SCM to unload to free up RAM. Is that the main use?

Feel free to correct me as I am often wrong, drunk or misguided.

cheers
« Last Edit: April 02, 2013, 09:14:45 PM by aus9 »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7082
Re: SCM Basics
« Reply #98 on: April 03, 2013, 01:09:20 AM »
Hi aus9,

I stickied this topic.  Allowed deps are as of present gtk2, python, perl and things like that.  There was a discussion on making every scm completely self contained relying on nothing else, though that is a huge overhead in the amount of effort to create each package. 

I think the main use of the scm is the fact it is simpler and less breakable than the standard setup.

But with TC 5.x around the corner, I have been spending time in other areas besides scm.  Sending in scm extensions is always welcome of course, but my own activity has been paused. 

aus9

  • Guest
Re: SCM Basics
« Reply #99 on: April 03, 2013, 03:04:56 AM »
thanks for the sticky

net issues
http://www.tinycorelinux.net/4.x/x86/scm/  for me borks into just a text listing while
http://distro.ibiblio.org/tinycorelinux/4.x/x86/scm/  behaves like I expect it too.

any chance you can fix?


Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7082
Re: SCM Basics
« Reply #100 on: April 03, 2013, 05:10:12 AM »
I believe the viewing of a list is the expected behavior for the tinycorelinux.net scm and tcz repo pages.  The pages are not really intended to be used for downloading anyway.


Thanks.

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4210
Re: SCM Basics
« Reply #101 on: April 03, 2013, 06:06:24 AM »

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3836
Re: SCM Basics
« Reply #102 on: April 03, 2013, 08:32:57 AM »
Unless I am missing something, this intentional behavior has as side effect putting an obstacle in access to source of scm's and tcz's.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4210
Re: SCM Basics
« Reply #103 on: April 03, 2013, 10:50:03 AM »
Hi tinypoodle
Quote
side effect putting an obstacle in access to source of scm's and tcz's.
Yes, but it's only a minor obstacle. Just add
Code: [Select]
src/to the end of the url.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3836
Re: SCM Basics
« Reply #104 on: April 03, 2013, 11:10:19 AM »
Agreed on a practical level, and that prevents load from listing of extensions.

Just that it might be considered optimal if access to source is not made more difficult than necessary.
Latter could possibly be achieved by moving the /src dirs out of being subdirs of /tcz and /scm or by directly linking to them.
« Last Edit: April 03, 2013, 11:31:44 AM by tinypoodle »
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)