On Mon, 16 Dec 2013, Leif W wrote:

> I was thinking along those lines, but was not sure of the best way to handle
> it. Maybe the option can take the 4 short names mentioned (mozilla,
> mozilla-release, nss, mozilla-aurora) with the url's in an array/hash, and
> otherwise takes a URL to the certdata.txt file we want?

Yes, that's kind of what I thought too. Looking at this page:
https://wiki.mozilla.org/Tree_Rules we can see the names for the different
Mozilla trees. I believe perhaps these are the most interesting ones, in order
of how the changes trickle down:

  mozilla-incoming
         -central
         -aurora
         -beta
         -release

So incoming gets the changes first, and then they will trickle down into the
other trees when and if they meet the correct criterias.

Using those names as short names for where to pick the certdata seems
appropriate to me. And we could default to 'release' which probably would be
conservatively appropriate.

> I think I am familiar enough with perl, VBS, and PHP to make that happen,
> whatever other languages the mk-ca-bundle are, I am sure I could figure out
> enough of their syntax to make such a change. The code may not be the most
> elegant. :)

Lovely! No worries, we'll review and help out if necessary!

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html