WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Guidelines for extension submission  (Read 36543 times)

Offline JustinCB

  • WikiUser
  • *
  • Posts: 18
Re: Guidelines for extension submission
« Reply #45 on: June 02, 2017, 07:51:45 AM »
It can take a few weeks for submitted extensions to appear in the repo.
OK.  I'll be patient.  Is the number of extensions being submitted so high that whoever it is that checks them has a pipeline/waiting list of extensions to check? 

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2640
Re: Guidelines for extension submission
« Reply #46 on: June 02, 2017, 08:10:22 AM »
I'm also waiting for a number of submitted extensions to be posted..

Somehow the last 3 weekends seem to have been missed, but there's always this weekend and next weekend before I start to panic :)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9814
Re: Guidelines for extension submission
« Reply #47 on: June 02, 2017, 09:33:05 AM »
He's just busy in general, I guess.
The only barriers that can stop you are the ones you create yourself.

Offline JustinCB

  • WikiUser
  • *
  • Posts: 18
Re: Guidelines for extension submission
« Reply #48 on: June 06, 2017, 09:49:27 AM »
Mine just got processed, so I guess yours will be processed soon too. 

Offline JustinCB

  • WikiUser
  • *
  • Posts: 18
Re: Guidelines for extension submission
« Reply #49 on: October 03, 2017, 09:20:23 AM »
I sent two batches of extensions. The first went fine, but the second kept getting rejected by gmail, so I had to use bcrypt(I've never had to do that before).  They haven't appeared yet to my knowledge, but I'm sure you're busy. 

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5782
Re: Guidelines for extension submission
« Reply #50 on: October 03, 2017, 10:10:52 AM »
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.

Offline Lukasz032

  • WikiUser
  • *
  • Posts: 8
  • Developing servers (:
    • Lukasz032 Webserver
Re: Guidelines for extension submission
« Reply #51 on: November 09, 2017, 07:22:19 AM »
I've submitted some extensions on October, are there any delays in processing? I haven't gotten any confirmation since then :)
Tiny-Core Extensions Maker (mainly for server use, but not only) :)

SP5LC @ KO02MD on HF/VHF

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1652
Re: Guidelines for extension submission
« Reply #52 on: November 09, 2017, 07:28:02 AM »
It can take a few weeks for submitted extensions to appear in the repo.
;)
Download a copy and keep it handy: Core book ;)

Offline JustinCB

  • WikiUser
  • *
  • Posts: 18
Re: Guidelines for extension submission
« Reply #53 on: July 12, 2018, 06:36:41 AM »
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.
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. 

Offline aus9

  • WikiUser
  • *
  • Posts: 41
Re: Guidelines for extension submission
« Reply #54 on: July 12, 2018, 06:39:38 PM »
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 ;)
Good Luck