Tiny Core Linux

Tiny Core Extensions => TCE Bugs => Topic started by: bmarkus on October 09, 2009, 10:23:06 AM

Title: Extensions incompatible with 2.4
Post by: bmarkus on October 09, 2009, 10:23:06 AM
According to .list files following extensions contain user.tar.gz therefore incompatible with 2.4

chimera2
cpufreq
laptop-mode-tools
minefield
nano
pppd
smartmontools
xdm
zfs-fuse
Title: Re: Extensions incompatible with 2.4
Post by: Jason W on October 09, 2009, 10:43:26 AM
Thanks.  I believe nano has been fixed, but I am sure there are others out there.  after seeing the latest this morning I had actually planned when I get home today to update my mirror and script the finding of user.tar.gz and replace with startup scripts.  Hopefully in the next day or so there will be no more user.tar.gz.
Title: Re: Extensions incompatible with 2.4
Post by: bmarkus on October 09, 2009, 10:45:51 AM
List is based on .list files downloaded with ftp just before the post so it is fresh.

I think it is up to the extension creators to make their extensions up to date.
Title: Re: Extensions incompatible with 2.4
Post by: Jason W on October 09, 2009, 11:31:27 AM
I personally never listed user.tar.gz in my file lists but rather it's contents to reflect what gets installed into the system.  But I see some have it in there, and that is fine.  I plan to mount and then find or ls the user.tar.gz in case it was not listed in the list file.

I agree that it is always the best case for extension submitters to be the one to maintain their extensions.   I will look over the extensions that contain user.tar.gz and try to contact their owners if their owner is either a team member or active contributor before I resort to unilateral action.  But if I receive no response I must ensure the integrity of the repo as TC 2.4 is very soon to release.

Title: Re: Extensions incompatible with 2.4
Post by: robc on October 09, 2009, 12:15:08 PM
These are the extensions that I have left to update that have user.tar.gz files:
php5
php5-cgi-pear
mupen64plus

I was hoping php 5.3.1 would be out before tc deprecated the user.tar.gz but it doesn't look like that will happen. I can update the tcz to fix it in the mean time.

Edit: removed sword and ntop from list, I must have already fixed them.
Title: Re: Extensions incompatible with 2.4
Post by: Jason W on October 09, 2009, 12:36:44 PM
Thanks Rob.

What I will do is post a complete list here base on mount - find - grep of user.tar.gz.  Then their owners can update them.  Any few that may be left after that can then be dealt with.
Title: Re: Extensions incompatible with 2.4
Post by: Lee on October 09, 2009, 06:19:10 PM
gtm5 is still only available as a .tce.  I'll make a .tcz out of it this weekend, I promise.  Is anyone else using this?

And maybe I'll do the same with zile and actually submit it, too.  I've been using it for a long time and don't remember why I didn't submit it - it was some little thing, not a show stopper.

Title: Re: Extensions incompatible with 2.4
Post by: Juanito on October 10, 2009, 02:34:28 AM
smartmontools and cpufreq updated - laptop-mode-tools pulled, this needs more work.
Title: Re: Extensions incompatible with 2.4
Post by: Jason W on October 10, 2009, 03:31:02 AM
Here is the full list based on mounting and searching for user.tar.gz:

bashburn.tcz
bluez-gnome.tczl
bonecho-gtk2.tcz
gs.tczl
pci-utils.tczl
php5-cgi.tczl
pppd.tczl
xdm.tczl
zfs-fuse.tcz

bashburn, bonecho, are mine and I will fix them tomorrow.
Title: Re: Extensions incompatible with 2.4
Post by: Juanito on October 10, 2009, 03:57:04 AM
gs.tczl no longer exists and was replaced by gs.tcz a few days ago. Similarly, pci-utils was updated about a week back.

..using old data maybe?

I'll fix bluez-gnome.

Edit: bluez-gnome fixed, but I need to look at this some more as it contains libs that now exist as separate extensions, but which didn't exist at the time I made this extension.
Title: Re: Extensions incompatible with 2.4
Post by: curaga on October 10, 2009, 04:27:03 AM
pppd fixed.
Title: Re: Extensions incompatible with 2.4
Post by: Jason W on October 10, 2009, 06:10:08 AM
My rsync mirror does not delete extensions that no longer exist in repo.  A desired behavior for archival purposes, but not for what I was doing here.