Tiny Core Linux

Tiny Core Extensions => TCE News => TCE 2.x => Topic started by: Jason W on May 17, 2009, 08:45:46 PM

Title: dictclient
Post by: Jason W on May 17, 2009, 08:45:46 PM

Thanks to Kingdomcome for dictclient:

Code: [Select]

Title: dictclient.tce
Description: dictclient              (TESTING)
Version: 1.0.3.1
Author: John Goerzen
Original-site: http://packages.debian.org/stable/interpreters/python-dictclient
Copying-Policy: GPL2
Size: 8.0K
Extension_by: Kingdomcome
Comments: python dictclient module
Requires python.tc{e,z}l

This extension is PPI compatible
Change-log: ----
Current: 2009/05/16 First Version



Code: [Select]

Title: dictclient.tcz
Description: dictclient              (TESTING)
Version: 1.0.3.1
Author: John Goerzen
Original-site: http://packages.debian.org/stable/interpreters/python-dictclient
Copying-Policy: GPL2
Size: 12.0K
Extension_by: Kingdomcome
Comments: python dictclient module
Requires python.tc{e,z}l
Change-log: ----
Current: 2009/05/16 First Version



Title: Re: dictclient
Post by: jpeters on May 18, 2009, 10:34:24 AM

Why is dep python.tc{e,z}l listed 4 times?   

Title: Re: dictclient
Post by: Kingdomcome on May 18, 2009, 02:36:13 PM

Another oversight on my part.  I can resubmit with a corrected dep.  I have written a generic build script that I used to create the extensions I submitted in a bundle and since submitting, I have found a few errors in my script.  I tried to check over everything and make sure it was ready for the repo, but apparently I missed a few things.  As this was my first contribution, I hope the community will bear with me a bit I will try to clean up my mistakes and also share the generic build script once the bugs have been ironed out.

Title: Re: dictclient
Post by: Jason W on May 18, 2009, 05:20:41 PM

I can correct a dep file quickly by logging into ibiblio, normally no need to resubmit.

Your extension submission was as thorough as I have seen - included list files, links to source, (TESTING) label, build scripts, clear indication of what is for 1.x and 2.x, and so on.  Those kind of things save me (and sometimes the submitter too) a lot of time.  Overall the community is doing very well with this, but I wanted to make a mention of yours as everything was place to make quick work of posting a large batch of extensions.

Title: Re: dictclient
Post by: jpeters on May 18, 2009, 06:03:08 PM

Quote from: Jason W on May 18, 2009, 05:20:41 PM

I can correct a dep file quickly by logging into ibiblio, normally no need to resubmit.

Your extension submission was as thorough as I have seen - included list files, links to source, (TESTING) label, build scripts, clear indication of what is for 1.x and 2.x, and so on.  Those kind of things save me (and sometimes the submitter too) a lot of time. 

Maybe a little more description in the wiki on submitting extensions?

Title: Re: dictclient
Post by: Jason W on May 18, 2009, 06:44:45 PM

I've put it all in the guidelines thread, but it is spread around through the posts in there. I don't have direct access to the wiki but I will draw up a document and get it all in one place.

Title: Re: dictclient
Post by: ^thehatsrule^ on May 18, 2009, 07:27:32 PM

(OT) The wiki actually points to the forum thread as well.

Title: Re: dictclient
Post by: jpeters on May 18, 2009, 07:34:55 PM

Quote from: ^thehatsrule^ on May 18, 2009, 07:27:32 PM

(OT) The wiki actually points to the forum thread as well.

That's clear....but as Jason indicated, having it in one place (ie, coherent doc) would probably yield better results....