Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: andyj on June 19, 2013, 03:26:11 PM
-
I've finished my scripts which let me build an extension for open-vm-tools easy peasy. I've got the .tcz, .dep, .list, .info, and .tree and .md5.txt files done. How do I share the joy?
Andy
-
Hi andyj
Go to the bottom of:
http://wiki.tinycorelinux.net/wiki:creating_extensions
and read the paragraph called Send to
-
I tried running the submitqc4 script, but it threw out a lot of errors:
gunzip: invalid magic
sed: can't read /tmp/submitqc/.info.lst: No such file or directory
open-vm-tools-3.0.21-tinycore.tcz has proper startup script name open-vm-tools-3.0.21-tinycore
grep: /tmp/submitqc/.info.lst: No such file or directory
cat: /tmp/submitqc/.info.lst: No such file or directory
The following errors are found in open-vm-tools-3.0.21-tinycore.tcz.info. No news is good news:
Change-log: field is not valid in open-vm-tools-3.0.21-tinycore.tcz.info.
open-vm-tools-3.0.21-tinycore.tcz is a valid tcz file. Checking MD5 for open-vm-tools-3.0.21-tinycore.tcz:
open-vm-tools-3.0.21-tinycore.tcz: OK
Obviously I haven't found the documentation for this yet.
Andy
-
You'll need to create an info file
Sent from my iPad using Tapatalk HD
-
I have an info file, in the same directory:
Title: open-vm-tools-3.0.21-tinycore.tcz
Description: Open Source client tools for VMWare hosted virtual machines
Version: 9.2.3-1031360
Author: VMWare
Original-site: http://sourceforge.net/projects/open-vm-tools/files/open-vm-tools/
Copying-policy: Lesser GPL 2.1
Size: 616K
Extension_by: Andyj
Tags: VMWare client tools
Comments: Install extension dependencies first as this replaces the nic driver
Add open-vm-tools-KERNEL.tcz to onboot.lst
Append blacklist=pcnet32 to boot command line
Add to .xsession after mouse initialization:
[ $(which vmware-checkvm) ] && [ vmware-checkvm ] && vmware-user &
Change-log:
Current: 2013/06/19 Original
-
Please read the whole link you were given before. The info file needs to be in the upload tarfile.
-
Hi andyj
You don't supply the tree file. That gets generated in the repo.
-
A few things. The wiki says to run the audit tool, then tar, gzip, bcrypt. Secondly, when I think of documentation I don't think of a long rambling five page forum thread. Even so, I figured out the problem was that my /opt/tcemirror didn't end with a slash. Not a problem for tce-load, but a problem for submitqc4. Now that it's fixed it runs with no errors.
The all in two compile and package scripts aren't part of the extension. How would you like those delivered?
Andy
-
Everything is to be included in the encrypted tarfile that you submit.
-
Hi andyj
The all in two compile and package scripts aren't part of the extension. How would you like those delivered?
I would place those in a second encrypted tar file and state what that file is in the email.
-
Everything is to be included in the encrypted tarfile that you submit.
Why do you encrypt the tar file?
-
I have never sent an encrypted tar.gz, I always just sent a tar with no compression and I've never had any problems, plus now with google driver can send large files without any fear
-
Everything is to be included in the encrypted tarfile that you submit.
Because the instructions said to bcrypt the file.
Why do you encrypt the tar file?
-
No need to encrypt files. Files of a tcz package are Google neutral, not executable on WINDOWS. Encryption is good only to cause problems,.
For more info a Gmail see
https://support.google.com/mail/answer/6590
-
We've had gmail block some attachments in the past.
-
I always bcrypt the compressed extension files as requested and they have never had a problem
-
I always bcrypt the compressed extension files as requested and they have never had a problem
No one tolt it is causing a problem. It is just causing unnecessary additional work on both ends. I have never used bcrypt in my life. During years I sent many extensions, never had any problem dute to lack of enncryption.
It is easy. Send it unancrypted. If there is a problem with file types, Google will send you an error report. Than you can correct your submission.
-
bmarkus
Anything that makes it easier for us newbies to become downstream maintainers is good thing!
I am sure coreplayer2 does not follow my advice, but I suspect he has, like me, been following the wiki. If the wiki is wrong or more correctly,
no longer relevant in the make BFE section, lets change it.
We need more maintainers to share the load, but I am reluctant to change the wiki without gutmensch being aware of it. Maybe you could pm him?
I have made some mistakes and can't afford to annoy him more than necessary, otherwise I would have done this myself.
thanks for reading and what ever your decision is.
Gordon
-
bmarkus, we didn't make the rules seems easy enough to do as asked of us, we do this until further advised
8)