[Cuis] [4.1][Test] PetitParser
Casey Ransberger
casey.obrien.r at gmail.com
Fri Dec 28 13:56:42 CST 2012
Wow! Thanks for putting the list together folks! This is cool! I know I'm
not supposed to use more than one exclamation point per email!
Casey
On Thu, Dec 27, 2012 at 4:08 AM, Germán Arduino <garduino at gmail.com> wrote:
> Done: https://gist.github.com/4387710
>
>
>
> 2012/12/27 H. Hirzel <hannes.hirzel at gmail.com>
>
>> On 12/27/12, Germán Arduino <garduino at gmail.com> wrote:
>> > Yes, I was thinking in a simple list, as I've said before.
>> >
>> > Yesterday night I was near of start a gist, but was to late and I went
>> to
>> > sleep :)
>> >
>> > I've several packages to add to the gist, I should fork it, update, and
>> > then request you a pull?
>>
>> Just fork my gist
>> https://gist.github.com/4387559
>> in case there is a 'fork' button on your screen (Mine does not but
>> that is probably because I created the gist).
>>
>> Change it to whatever seems suitable to you. In case I want it back to
>> add/change something I will in turn fork yours.... :-)
>>
>> >
>> > Or you prefer to update yourself being that are only a bit of text....
>> >
>> > Cheers.
>> >
>> >
>> > 2012/12/27 H. Hirzel <hannes.hirzel at gmail.com>
>> >
>> >> On 12/27/12, Angel Java Lopez <ajlopez2000 at gmail.com> wrote:
>> >> > My second suggestion was a list.
>> >>
>> >> +1
>> >>
>> >> You may fork https://github.com/jvuletich/Cuis
>> >> add a 'doc' subdirectory
>> >>
>> >> and start your list as an text file there.
>> >>
>> >> At the moment there are 4 forks and I think you are not among them.
>> >>
>> >> Or alternatively I could do it myself. :-)
>> >>
>> >> Here is my fork
>> >> https://github.com/hhzl/Cuis
>> >>
>> >> Now I have to figure out how to do the 'doc' subdirectory and create
>> the
>> >> file.
>> >>
>> >>
>> >> For the meantime a gist with a text file might be easier
>> >>
>> >> something like this
>> >>
>> >> https://gist.github.com/4387559
>> >>
>> >> (markdown, a title is underlined with -------- and shows up bold)
>> >>
>> >> More on Markdown
>> >> here
>> >> http://www.johnmacfarlane.net/pandoc/README.html
>> >>
>> >> Markdown, the main documentation format of github may be converted to
>> >> many formats.
>> >>
>> >> see for example here
>> >> http://www.johnmacfarlane.net/pandoc/try
>> >>
>> >>
>> >>
>> >>
>> >> > If the package "is outside" the central repo, the instructions to
>> >> > read/install from Cuis should be at the other author repo. Then,
>> he/she
>> >> has
>> >> > the responsability to update the info, not the central repo author.
>> >> >
>> >> > The central repo author could resolve issues like "I have a new
>> package
>> >> for
>> >> > Cuis at ..., please at to your list", the n he can add to the
>> >> > Package.md
>> >> > link page.
>> >> >
>> >> > But having the central repo with the package (not a link), has an
>> >> > advantage: central repo could have tags. So, the packages at tag
>> >> > "v0.1.0"
>> >> > are all compatible with that tag, and every improvement at tag
>> "v0.2.0"
>> >> > should be committed to that tag. The "master" tag is the development
>> >> > tag.
>> >> >
>> >> > So, I could download the v0.2.0 with all the optional packages of
>> that
>> >> > version, without struggling going to each package author repo, and
>> >> > trying
>> >> > to guess what package/tag is compatible with Cuis v0.2.0
>> >> >
>> >> > Cons: it put more responsability to central repo author(s).
>> >> >
>> >> > On Thu, Dec 27, 2012 at 8:01 AM, Germán Arduino <garduino at gmail.com>
>> >> wrote:
>> >> >
>> >> >> Yes, it's an option.
>> >> >>
>> >> >> But I was thinking in something more simple, only a list with the
>> link
>> >> of
>> >> >> the repo :) and may be some code to read/install from Cuis
>> (something
>> >> >> as
>> >> >> we
>> >> >> did in the old times of SmallLand ... using a swiki (the only tool
>> >> >> that
>> >> >> we
>> >> >> had in such times)).
>> >> >>
>> >> >> Cheers.
>> >> >>
>> >> >>
>> >> >> 2012/12/27 Angel Java Lopez <ajlopez2000 at gmail.com>
>> >> >>
>> >> >>> Until you have a package manager, first idea:
>> >> >>>
>> >> >>> Use the cuis repo at GitHub.
>> >> >>>
>> >> >>> Every contributor make a fork.
>> >> >>> He/she add the code to his/her fork.
>> >> >>> Make a pull request to central repo
>> >> >>>
>> >> >>> Maybe, a guide to have folders per package/topic.
>> >> >>>
>> >> >>> Alternatively (or complementary), a PACKAGE.md page at Cuis central
>> >> >>> GitHub repo
>> >> >>>
>> >> >>> Angel "MyLifeIsGitHub" Lopez ;-)
>> >> >>> github:ajlopez
>> >> >>>
>> >> >>>
>> >> >>> On Thu, Dec 27, 2012 at 7:49 AM, Germán Arduino
>> >> >>> <garduino at gmail.com>wrote:
>> >> >>>
>> >> >>>> Nice!
>> >> >>>>
>> >> >>>> We should have a central place where list all the available
>> packages
>> >> >>>> ready to use for Cuis?
>> >> >>>>
>> >> >>>> Cheers.
>> >> >>>>
>> >> >>>>
>> >> >>>> 2012/12/27 H. Hirzel <hannes.hirzel at gmail.com>
>> >> >>>>
>> >> >>>>> Hello
>> >> >>>>>
>> >> >>>>> I installed
>> >> >>>>> PetitParser.pck
>> >> >>>>> PetitTests.pck
>> >> >>>>>
>> >> >>>>> from
>> >> >>>>> https://github.com/pmon/Cuis-PetitParser
>> >> >>>>>
>> >> >>>>> RESULT
>> >> >>>>> The tests run fine in 4.1.
>> >> >>>>>
>> >> >>>>> _______________________________________________
>> >> >>>>> Cuis mailing list
>> >> >>>>> Cuis at jvuletich.org
>> >> >>>>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>> >> >>>>>
>> >> >>>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> --
>> >> >>>> ============================================
>> >> >>>> Germán S. Arduino <gsa @ arsol.net> Twitter: garduino
>> >> >>>> Arduino Software http://www.arduinosoftware.com
>> >> >>>> PasswordsPro http://www.passwordspro.com
>> >> >>>> greensecure.blogspot.com germanarduino.blogspot.com
>> >> >>>> ============================================
>> >> >>>> _______________________________________________
>> >> >>>> Cuis mailing list
>> >> >>>> Cuis at jvuletich.org
>> >> >>>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>> >> >>>>
>> >> >>>>
>> >> >>>
>> >> >>> _______________________________________________
>> >> >>> Cuis mailing list
>> >> >>> Cuis at jvuletich.org
>> >> >>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> Cuis mailing list
>> >> >> Cuis at jvuletich.org
>> >> >> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>> >> >>
>> >> >>
>> >> >
>> >>
>> >> _______________________________________________
>> >> Cuis mailing list
>> >> Cuis at jvuletich.org
>> >> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>> >>
>> >
>> >
>> >
>> > --
>> > ============================================
>> > Germán S. Arduino <gsa @ arsol.net> Twitter: garduino
>> > Arduino Software http://www.arduinosoftware.com
>> > PasswordsPro http://www.passwordspro.com
>> > greensecure.blogspot.com germanarduino.blogspot.com
>> > ============================================
>> >
>>
>> _______________________________________________
>> Cuis mailing list
>> Cuis at jvuletich.org
>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>>
>
>
>
> --
> ============================================
> Germán S. Arduino <gsa @ arsol.net> Twitter: garduino
> Arduino Software http://www.arduinosoftware.com
> PasswordsPro http://www.passwordspro.com
> greensecure.blogspot.com germanarduino.blogspot.com
> ============================================
>
> _______________________________________________
> Cuis mailing list
> Cuis at jvuletich.org
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jvuletich.org/pipermail/cuis_jvuletich.org/attachments/20121228/5b362f68/attachment-0002.html>
More information about the Cuis
mailing list