slack only uses first host entry in roles.conf

[Lee Colleton]

If two entries are present for a host in roles.conf only the first
will be used. This undocumented feature of slack can create problems
if multiple groups are updating the same roles.conf for a pool of
servers.

This can be caught by a presubmit check on the roles.conf through
revision control, but people implementing slack won't know about this
necessity unless forewarned.

Also, I was unable to checkout code from SVN with the following
command:
svn checkout http://slack.googlecode.com/svn/trunk/ slack-read-only
svn: URL 'http://slack.googlecode.com/svn/trunk' doesn't exist

Please advise on the code checkout, I'd rather submit a patch than
just complain on this list.

--Lee

[Alan Sundell]

Hi, Lee,

Sorry about the over-1-year lag. I'm a slacker :)
But someone just mentioned your message to me, so...

On Nov 20 2008, 11:23 am, Lee Colleton <lee.colle...@gmail.com> wrote:
> If two entries are present for a host in roles.conf only the first
> will be used. This undocumented feature of slack can create problems
> if multiple groups are updating the same roles.conf for a pool of
> servers.

I'm actually kind of OK with this behavior, just because I don't want
to make parsing more complicated, since I've seen people make other
scripts that read that file. Though documenting it or making it a
warning might be a good idea.

> This can be caught by a presubmit check on the roles.conf through
> revision control, but people implementing slack won't know about this
> necessity unless forewarned.
>

> Also, I was unable tocheckoutcode from SVN with the following

> command:
> svncheckouthttp://slack.googlecode.com/svn/trunk/slack-read-only
> svn: URL 'http://slack.googlecode.com/svn/trunk'doesn't exist
>

> Please advise on the codecheckout, I'd rather submit a patch than

> just complain on this list.

This is because Google Code was giving out the wrong instructions.
When I looked at this back then, I didn't find a way to change what
the webpage said, but when I looked again now, I found one (either
Google Code changed, or I did).

So now it properly tells you to go to svn/slack/trunk, not svn/trunk.

The reason for trunk not being at the root is there are multiple
projects in the repository. (There's also a slack-master, as you can
see if you browse, and I would not mind trying to collect these
utility scripts people write into a slack-utils or something.)

--Alan