WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: compiletc on persistent local  (Read 3789 times)

Offline mikshaw

  • Sr. Member
  • ****
  • Posts: 368
compiletc on persistent local
« on: December 12, 2008, 04:26:03 PM »
I think it was compiletc which someone had mentioned might be a little flakey if added to a persistent /usr/local.
Maybe it was the X dev package?

In any case, I'm wondering if it's safe to add these packages to local...maybe I'm just being overly cautious.  I have most of the other dev packages already in local, but when I compile I reboot into a clean system + the devs.  Is this recomended, or am I okay just extracting what I need into local so I can compile whatever I want whenever I want without rebooting?

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: compiletc on persistent local
« Reply #1 on: December 12, 2008, 04:32:01 PM »
I think it was mentioned that compiling compiletc's tools to /usr/local might be.  Most of the stuff is _not_ under /usr/local, so using tclocal wouldn't really do much.

In general, dev files should be fine.

Offline mikshaw

  • Sr. Member
  • ****
  • Posts: 368
Re: compiletc on persistent local
« Reply #2 on: December 12, 2008, 06:20:30 PM »
So would it be safe enough if compiletc.tce was extracted into a TC remaster?  Is there anything installed from it into /usr.local?  If so that would probably be trouble.
What about Xorg and its devs?  I think that's all /usr/local? If so I can put that all in my persistent /usr/local

In a situation like that I would have no need to reboot into a vanilla TC unless I was testing extensions.

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: compiletc on persistent local
« Reply #3 on: December 12, 2008, 07:16:25 PM »
(1) It should have the same effect as loading it as an extension.  (2) A way to tell with a .tce: tar ztvf package.tce
(3) 2 still applies, although this should be useful http://forum.tinycorelinux.net/index.php?topic=152.msg942#msg942
The .info might have something too, although I guess it isn't that clear in these 2 cases.

Offline mikshaw

  • Sr. Member
  • ****
  • Posts: 368
Re: compiletc on persistent local
« Reply #4 on: December 13, 2008, 02:31:54 AM »
Quote
(2) A way to tell with a .tce: tar ztvf package.tce
I have the tcz version at the moment.  I had already downloaded a pile of tcz packages thinking it would be an easy way  to expand the system without using extra ram.  It was only after seeing how much longer boot time had become that I decided to go with tclocal.  I'm guessing the contents of /tmp/tcloop/* will be the same as the contents of a tce file of the same name.

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: compiletc on persistent local
« Reply #5 on: December 13, 2008, 11:21:16 AM »
Not all of the contents are the same if there is a user.tar.gz.  The extra step of listing the contents on that should give you the all of the files.

Offline mikshaw

  • Sr. Member
  • ****
  • Posts: 368
Re: compiletc on persistent local
« Reply #6 on: December 13, 2008, 03:28:15 PM »
Thanks. I'll probably end up downloading my tcz packages in tce format, but in the meantime I'll look into how the tcz works.