chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] Requesting subversion access


From: Estevo
Subject: Re: [Chicken-users] Requesting subversion access
Date: Sun, 14 Jul 2013 12:26:18 -0700 (PDT)

I'm in a similar situation.  I just completed version 0.1 of the hexgrid module, to work with hexagonal grids like those in old-school wargames.

You can check it out at

https://github.com/euccastro/hexgrid

Where tests/run.scm are the automated tests, tests/visualize.scm is an interactive visualization of what it does (see docstring).

and documentation has been tentatively uploaded to http://wiki.call-cc.org/eggref/4/hexgrid

It passes all salmonella checks.  Should you approve this, the line to add to egg-locations would be:

(hexgrid "https://github.com/euccastro/hexgrid/raw/master/release-info")



De: "address@hidden" <address@hidden>
Para: address@hidden
Enviadas: Domingo, 14 de Julho de 2013 18:00
Assunto: Chicken-users Digest, Vol 128, Issue 15

Send Chicken-users mailing list submissions to
    address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.nongnu.org/mailman/listinfo/chicken-users
or, via email, send a message with subject or body 'help' to
    address@hidden

You can reach the person managing the list at
    address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Chicken-users digest..."


Today's Topics:

  1. Re: Requesting subversion access (Mario Domenech Goulart)


----------------------------------------------------------------------

Message: 1
Date: Sun, 14 Jul 2013 12:24:52 +0000
From: Mario Domenech Goulart <address@hidden>
To: address@hidden
Subject: Re: [Chicken-users] Requesting subversion access
Message-ID: <address@hidden>
Content-Type: text/plain

Hi Tim,

On Sat, 13 Jul 2013 14:58:29 +0200 Tim van der Linden <address@hidden> wrote:

> I finished up an early version of my egg and, as stated in the
> "releasing-your-egg" manual, I should ask somebody here for access to
> SVN so I can add it :)

We have a a special file (egg-locations) which contains a list of
"pointers" to the actual location of egg source repositories, and
editing that list is the only step which requires special permissions
(you only have to request it when releasing your egg for the first
time).

If the code repository for your egg is avaliable from a public server,
all you need to do is send the list the location and someone with admin
access will add it to the coop.  We'll take care of adding a pointer to
your egg as soon as you publish its location.

An svn account will probably still be useful, though, for
documentation.  We keep egg documentation in the wiki, which uses svn as
backend storage.  You can edit it with an anonymous account, which is
not recommended, since we have to keep one eye on anonymous edits to
check for wiki spam, and that means manual work.  So, it's recommended
that you create an svn account and use it to edit the wiki (just send me
the username you inted to use and the hash of your password -- it can be
generated with "openssl passwd -apr1").

Finally, before releasing your egg, make sure it gets approved by
salmonella (http://wiki.call-cc.org/egg/salmonella), the tool we use to
perform basic checks on eggs.  If you don't have it installed, it's just
a matter of running:

  $ chicken-install salmonella

To use it, you can:

  $ cd <egg source dir>
  $ salmonela

If salmonella doesn't indicate anything wrong, you are good.  If you see
any failure, you can see more details about it using the log viewer:

  $ salmonella-log-viewer salmonella.log

Once your egg gets added to the coop, it'll be daily tested by
salmonella (see http://tests.call-cc.org)

Best wishes.
Mario
--
http://parenteses.org/mario



------------------------------

_______________________________________________
Chicken-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/chicken-users


End of Chicken-users Digest, Vol 128, Issue 15
**********************************************



reply via email to

[Prev in Thread] Current Thread [Next in Thread]