WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: [was Re: tce-update blowing chunks on *.md5.txt -- solved]  (Read 2322 times)

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
[was Re: tce-update blowing chunks on *.md5.txt -- solved]
« on: January 01, 2010, 03:22:03 PM »
tcz "update" script  has a -vd option which views all dependencies and finds anything in the dep list not in the tce dir. Any mismatch will result in boot failure, so it's important to know.    

[removed due to policy]apps/view-deps.png
« Last Edit: January 01, 2010, 03:29:08 PM by jpeters »

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
[was Re: tce-update blowing chunks on *.md5.txt -- solved]
« Reply #1 on: January 01, 2010, 04:02:38 PM »
jpeters, you are crossing the line.

tce-update was not the issue here. The convert script for the new extension format was. The conversion script is a single use script and was posted in the forums. This user did not use it and instead manually started changing extension names.

Even after the title was changed to include Solved you feel you have to discourage users from core Tiny Core functions.

Please keep your scripting solutions in the proper topic area.  I know you refuse to use the base system as designed so you don't know or have anything to contribute but self promotion. It is not productive to discourage users from using the system as intended or designed

You don't need additional extensions to manage extensions, its provided in the base.



 
10+ Years Contributing to Linux Open Source Projects.

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
[was Re: tce-update blowing chunks on *.md5.txt -- solved]
« Reply #2 on: January 01, 2010, 04:32:18 PM »
Users create scripts to add functionality. Nobody gets paid for this. It wasn't too long ago that base didn't even have an update capacity. It's really a shame that you view contributions as some kind of competition.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
[was Re: tce-update blowing chunks on *.md5.txt -- solved]
« Reply #3 on: January 01, 2010, 04:52:31 PM »
It is a shame when you comment on that which you don't use.

Especially true, when the topic was marked "Solved".

There was absolutely no need for your follow up. You are the one who has chosen not to contribute to the betterment of Core, but to do your own thing.

There is really no competition when one needs extensions to manage extensions, its not like utilities have been added to the base in fact just the opposite.

It's fine if you wish to spend your time changing infrastructure to suit your own design, but there is a place for that in Programming and Scripting.

Keep the Core topic areas on topic so that Tiny Core can improve with those who wish to contribute on actual core infrastructure.
10+ Years Contributing to Linux Open Source Projects.

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
[was Re: tce-update blowing chunks on *.md5.txt -- solved]
« Reply #4 on: January 01, 2010, 06:21:13 PM »
Yeah....one of my more outlandish ideas was having a small, core distro, posted on a "wish" thread on DSL that started a lot of comments.  The idea (and implimentation) of an update function using md5 files was really weird, as is loading symlinked groups. Really "out there"....  and thanks for all the usual good cheer. Right....never contributed anything to TinyCore.

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: [was Re: tce-update blowing chunks on *.md5.txt -- solved]
« Reply #5 on: January 03, 2010, 05:14:19 PM »
[Split and locking as this no longer serves any real purpose]


Just to indulge those who are interested in the info:

Actually, the first (public) posts and implementation for updating are here: http://forum.tinycorelinux.net/index.php?topic=703.0 (not sure what the other group stuff refers to)

A "core-like" distro was floating around for a while.  These root ideas were drawn out even before I got to know the team at that time, in reference to DSL.  Implementation was mostly private before it became what is now known as TC.