Tiny Core Extensions > TCE News

Guidelines for extension submission

<< < (11/11)

Rich:
Hi JustinCB
Step 6 listed here:
http://wiki.tinycorelinux.net/wiki:creating_extensions#abbreviated_steps
does mention to  bcrypt  the archive, though I thought at one time there used to be directions on how to  bcrypt  the archive
here in the submitting section of that Wiki page:
http://wiki.tinycorelinux.net/wiki:creating_extensions#submitting
As I recall, it also used to say to use the password  tinycore  when  bcrypt  asks.

Lukasz032:
I've submitted some extensions on October, are there any delays in processing? I haven't gotten any confirmation since then :)

Misalf:

--- Quote from: Misalf on June 02, 2017, 09:22:46 AM ---It can take a few weeks for submitted extensions to appear in the repo.

--- End quote ---
;)

JustinCB:

--- Quote from: Rich on October 03, 2017, 01:10:52 PM ---Hi JustinCB
Step 6 listed here:
http://wiki.tinycorelinux.net/wiki:creating_extensions#abbreviated_steps
does mention to  bcrypt  the archive, though I thought at one time there used to be directions on how to  bcrypt  the archive
here in the submitting section of that Wiki page:
http://wiki.tinycorelinux.net/wiki:creating_extensions#submitting
As I recall, it also used to say to use the password  tinycore  when  bcrypt  asks.

--- End quote ---
By the way, the wiki page has a mix between outdated & recent info, which is often confusing(in 2016 it only had info up to tce 4.x but then in 2017 & 2018 I did a half-arsed job updating it :-[ ).  We need someone who's a better writer & is willing to update it properly.  The rest of the wiki needs to be updated too, but less so than that page. 

aus9:
bcrypt IMHO should be removed because if you read the bottom lines

Files part of an extension package are Gmail neutral and accepted for delivery, no need to encrypt.

I added gmail has a size limit of 25 Mb to that section.

(2) I added a section for daemons under info that says Please show full pathways to start daemons in your info file. TC does not condone starting daemons in your tce.install script.
but me thinks it may also have to be mentioned in the custom install script section too.

Personally I use a build dir for a random package....I squash it as a TCZ and send it as that file
because if I have some new build dependencies......I sometime use the same email to keep it all together

my fav TCZ checker is very tolerant of my ways ;)

Navigation

[0] Message Index

[*] Previous page