| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 03/11/2016 07:35 PM, Brian Dolbec wrote: |
| 5 |
> On Thu, 10 Mar 2016 18:40:31 -0800 Patrick McLean |
| 6 |
> <chutzpah@g.o> wrote: |
| 7 |
> |
| 8 |
>> On Thu, 10 Mar 2016 18:30:07 -0800 Brian Dolbec |
| 9 |
>> <dolsen@g.o> wrote: |
| 10 |
|
| 11 |
|
| 12 |
>> YAML - like JSON but made to be edited/read by humans (comment |
| 13 |
>> support is a big feature). Also valid JSON is valid YAML. Also |
| 14 |
>> can be validated just like JSON can. |
| 15 |
> |
| 16 |
> OK, I just had a closer look at yaml. It does look easier for |
| 17 |
> humans to edit and read. And seems to have the same data type |
| 18 |
> flexibility. Maybe not quite as many languages have libs for it. |
| 19 |
> But I don't think that is an issue for this data. |
| 20 |
> |
| 21 |
|
| 22 |
Yaml should be well supported so indeed, wouldn't expect any issues. |
| 23 |
|
| 24 |
> |
| 25 |
> I also want to separate the repoman release from the main portage |
| 26 |
> release. This will have several advantages. |
| 27 |
> |
| 28 |
|
| 29 |
Sounds reasonable |
| 30 |
|
| 31 |
|
| 32 |
- -- |
| 33 |
Kristian Fiskerstrand |
| 34 |
OpenPGP certificate reachable at hkp://pool.sks-keyservers.net |
| 35 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
| 36 |
-----BEGIN PGP SIGNATURE----- |
| 37 |
|
| 38 |
iQEcBAEBCgAGBQJW5Fl4AAoJECULev7WN52FDlQH/16B/DG09LOJnJiVeMhsCVYe |
| 39 |
MpvsPy4EJfzzAmqgYJhKY4NxD3/X/Y0CbMlO2o1C65WtaO6B85DdzCYuV44lq4Wd |
| 40 |
EujeJT5dveRU/uihEIPU9P45yLiHd/3iUJ6p0mu2f+OxcVXbEubuf16o4J9j2nmJ |
| 41 |
4p3xhOjPoYUlFKalDN2dNEy+JpAB/0gFjnmO5HMyhgnwnxj6o7SLHBLANBm4bReA |
| 42 |
m6CpmKxoxVpQ88c+xEJz9/X/FjtMVEFixVDphA9zrv1MEMh1K5RuDat0Y2U5BuYT |
| 43 |
71/M8AvG+2B64hSmM22EwK/Wk/mzddFQrwYahFfDofd42jYYIQw18gd5t76j6es= |
| 44 |
=FNfI |
| 45 |
-----END PGP SIGNATURE----- |
Archives