tc-ext-tools: A package build system for Tiny Core Linux

[AmatCoder]

Hi
AmatCoder, thank u for keeping alive tc-ext-tools.
Before I was using a script by kingdomcome which automatically splits the dev files and the locales.
U can look a the script in the src section of the tinycore site on my packages.

Yes, this could be done. I will do some tests...

The scripts of my recent packages also automatically adjust the info files.

Those scripts does not seem very different from how tc-ext-tools make info files...

The package to send to tcesubmit is a tar.bz2, maybe change it to xz.

bz2 or gz archives are acceptable to send, but a xz archive is not...as far as I know.

also this to scripts from jason could be included:
http://forum.tinycorelinux.net/index.php/topic,12002.0.html
  http://forum.tinycorelinux.net/index.php/topic,2475.0.html

Some functions from submitqc4 have their equivalent in tc-ext-tools...I will look to include the others.

Regards.

[jls]

regarding the info file for existing extensions I did this:

Code: [Select]

sed -i "s/Current:/ /" $PACKAGE.tcz.info
echo "Current: $CURRENT" >> $PACKAGE.tcz.info

My latest extensions where sent in xz format and whithout encryption and they had been  all published

[AmatCoder]

regarding the info file for existing extensions I did this:

Code: [Select]

sed -i "s/Current:/ /" $PACKAGE.tcz.info
echo "Current: $CURRENT" >> $PACKAGE.tcz.info


Oh, I see now...Old Current  goes to Change-log  automagically when update...I also will look this.

My latest extensions where sent in xz format and whithout encryption and they had been  all published

tc-ext-tools simply follow the wiki instructions:

Code: [Select]

[...] create an archive and then bcrypt it (using the password “tinycore”) in order to avoid any problems with GMail. but I don't know if it is required always...

[gutmensch]

If the package creation is scripted either way, better keep the tinycore bcrypt because of several mail filter issues, which can lead to some confusion... better safe than sorry

[solorin]

Arslan S. et. al.

Wow. Tried it for the first time today.
Very impressed by this tool.

Automates packaging to the point of editing a couple files, and typing a few commands.
A great time saver.
With a bit of tweaking(in the docs perhaps),
I would heartily recommend this to those who demand a certain package.

Some feedback.
git support doesn't quite seem to be there.
I kept getting 'schema invalid' after
buildit --download && buildit --print message

a lot of projects are moving to git.

it might also be interesting to put one's packaging directory under git.

2)the extension name in
addit --extensions="extension name" should not have .tcz appended as the tools
will append that when they package. perhaps this should be made clear in the docs.

3)buildit --split doesn't seem to work for me at the moment
i'll have a closer look at the examples.

other than that. Great work!

And on a personal note: Hope you're feeling the fresh breeze of freedom, Arslan S.!

cheerio,
solorin

[gutmensch]

git support doesn't quite seem to be there.
I kept getting 'schema invalid' after
buildit --download && buildit --print message

a lot of projects are moving to git.

whenever possible one should download only tags with released versions from the git repo, which is most of the time possible like any other source download of an archive (no git checkout). reason for this is to concentrate on somewhat stable releases, which a pull of the current tree isn't necessarily.

[solorin]

guter Punkt gutenmensch.
stable releases for submissions to the repo it is
(and has been).

however, maybe there are a small number of cases when tarballs are not made available?

[Arslan S.]

hello tc people i am back on track after about 6 months away.
planning mass update of extensions starting from mostly anticipated ones such as chromium, midori, minitube, vlc etc.

i have been checking the forums especially tce are all day and according to feedback received the update list will be arranged.
also special thanks to amatcoder for patching tc-ext-tools to work with latest tc and jls for updates

S. Arslan

[netnomad]

hi arslan,

great that you are back!
especially i'm glad that you want to contribute to the community again.
we are looking forward for your updates of all that favored packages as minitube, vlc and virtualbox
happy packaging, thanks.

[Onyarian]

welcome again to tc! 

[ndrancs]

Hi Arslan welcome back.
I have some questions for anyone.
in the common file is in the "source" could use a local file, eg like this.

Code: [Select]

PACKAGE="srware-iron"
VERSION="18.0.1050.0"
SOURCE="/mnt/sda5/PM/iron-linux.tar.gz->srware-iron-${VERSION}.tar.gz"
BUILD_DEPENDS=""
I have tried this and failed. What script should I modify. whether downloadit script?

[Arslan S.]

you can put the file in src directory and create the file download.stamp manually

[ndrancs]

Hi Arslan
Thank you, the trick works well, my internet connection is less stable areas, so I donlod use axel or aria2 file first.
another question: Can you make the nvidia-96.43.20 package for kernel 3.0.21 here:
http://tc-ext-tools.googlecode.com/svn/packages/

[Arslan S.]

Added local file support
http://code.google.com/p/tc-ext-tools/source/detail?r=603

usage:

SOURCE=file::/path/to/file

packaging old nvidia drivers is easy but no hardware to test

[ndrancs]

Hi Arslan S.
thanks for the quick revision to support the local file. for nvidia let me make my own package.