summaryrefslogtreecommitdiffstats
path: root/archives/extend/2013-August.txt
blob: 6dde6851653e8a804b7ff58bacafa0315201840a (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
From fgallaire at gmail.com  Fri Aug  2 17:01:26 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:01:26 +0200
Subject: [99s-extend] Mailing lists
Message-ID: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>

The extend projets are great and very popular, they need to have each
one a different mailing list.

And mailman has a really useless web interface.

Florent

-- 
FLOSS Engineer & Lawyer


From fgallaire at gmail.com  Fri Aug  2 17:06:42 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:06:42 +0200
Subject: [99s-extend] Riak in Farwest
Message-ID: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>

I love the farwest technical choices. But Riak seems to only be the
"prototype' database, and PostgreSQL the real target.

FMO, this is a huge fail. Riak is by far superior to PostgreSQL. I
want Riak, who really wants PostgresSQL ??

Florent

-- 
FLOSS Engineer & Lawyer


From essen at ninenines.eu  Fri Aug  2 17:08:47 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:08:47 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
Message-ID: <[email protected]>

Please tell us what you think makes Riak superior.

On 08/02/2013 05:06 PM, Florent Gallaire wrote:
> I love the farwest technical choices. But Riak seems to only be the
> "prototype' database, and PostgreSQL the real target.
>
> FMO, this is a huge fail. Riak is by far superior to PostgreSQL. I
> want Riak, who really wants PostgresSQL ??
>
> Florent
>


-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From essen at ninenines.eu  Fri Aug  2 17:09:58 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:09:58 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
Message-ID: <[email protected]>

On 08/02/2013 05:01 PM, Florent Gallaire wrote:
> The extend projets are great and very popular, they need to have each
> one a different mailing list.

That would be true if there was actual activity on the mailing lists. 
There isn't.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From fgallaire at gmail.com  Fri Aug  2 17:14:00 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:14:00 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <[email protected]>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
Message-ID: <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>

On Fri, Aug 2, 2013 at 5:09 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:
> On 08/02/2013 05:01 PM, Florent Gallaire wrote:
>>
>> The extend projets are great and very popular, they need to have each
>> one a different mailing list.
>
>
> That would be true if there was actual activity on the mailing lists. There
> isn't.

There is no activity because Mailman is useless.

Florent

-- 
FLOSS Engineer & Lawye


From lee.sylvester at gmail.com  Fri Aug  2 17:20:05 2013
From: lee.sylvester at gmail.com (Lee Sylvester)
Date: Fri, 2 Aug 2013 16:20:05 +0100
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
Message-ID: <[email protected]>

It's a bit like comparing sports cars to superbikes.  Riak has some very powerful features; Pipes, true clustering, fault tolerance, Riak CS etc.  Plus, it's built on Erlang :-)  PostgreSQL has SQL queries, real tables (rather than simple corruptible namespacing), complex query capabilities, real data types etc.  Each has their place.  For typical websites, PostgreSQL is the better choice.  For distributed applications, Riak is often the better choice. ***

Lee 

*** Mostly my opinion, only.



On 2 Aug 2013, at 16:08, Lo?c Hoguin <essen at ninenines.eu> wrote:

> Please tell us what you think makes Riak superior.
> 
> On 08/02/2013 05:06 PM, Florent Gallaire wrote:
>> I love the farwest technical choices. But Riak seems to only be the
>> "prototype' database, and PostgreSQL the real target.
>> 
>> FMO, this is a huge fail. Riak is by far superior to PostgreSQL. I
>> want Riak, who really wants PostgresSQL ??
>> 
>> Florent
>> 
> 
> 
> -- 
> Lo?c Hoguin
> Erlang Cowboy
> Nine Nines
> http://ninenines.eu
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend



From essen at ninenines.eu  Fri Aug  2 17:21:39 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:21:39 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
Message-ID: <[email protected]>

On 08/02/2013 05:14 PM, Florent Gallaire wrote:
> On Fri, Aug 2, 2013 at 5:09 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:
>> On 08/02/2013 05:01 PM, Florent Gallaire wrote:
>>>
>>> The extend projets are great and very popular, they need to have each
>>> one a different mailing list.
>>
>>
>> That would be true if there was actual activity on the mailing lists. There
>> isn't.
>
> There is no activity because Mailman is useless.

I said no activity, I didn't say no members. Please keep your complaints 
about the tool down, it's got nothing to do with it, and you just end up 
spamming people here.

All development happens on IRC, so this leaves the mailing lists only 
useful for questions, which should be rarer over time considering the 
docs keep improving and the archives provide great answers for the rest. 
It's all good.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From fgallaire at gmail.com  Fri Aug  2 17:25:22 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:25:22 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
Message-ID: <CAB9F1cdo2SLt2hdtjik1RtXPRGOQAxVEdr2Nxyx_06L=dbybJg@mail.gmail.com>

On Fri, Aug 2, 2013 at 5:08 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:
> Please tell us what you think makes Riak superior.

Riak is written in Erlang. See your own argumentations on why Erlang
is the best langage to program high load/fault-tolerent web software.

Riak is written in Erlang, as all the 99 other soft -> good
integration of the whole.

Riak is a NoSQL Dynamo database with Availability and Partition
tolerance, and this is what I want for my web applications. PostgreSQL
is a SQL Availability and Consistency old school database.

Riak is just what want a developer who use erlang to have a scaling platform.

Florent

-- 
FLOSS Engineer & Lawyer


From Kevin.Brown at turner.com  Fri Aug  2 17:29:35 2013
From: Kevin.Brown at turner.com (Brown, Kevin)
Date: Fri, 2 Aug 2013 15:29:35 +0000
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>,
 <[email protected]>
Message-ID: <[email protected]>

Postgres has been made to scale well in GIS applications.  Apple is using Postgres for their current Maps geo point storage.  

On Aug 2, 2013, at 11:20 AM, "Lee Sylvester" <lee.sylvester at gmail.com> wrote:

> It's a bit like comparing sports cars to superbikes.  Riak has some very powerful features; Pipes, true clustering, fault tolerance, Riak CS etc.  Plus, it's built on Erlang :-)  PostgreSQL has SQL queries, real tables (rather than simple corruptible namespacing), complex query capabilities, real data types etc.  Each has their place.  For typical websites, PostgreSQL is the better choice.  For distributed applications, Riak is often the better choice. ***
> 
> Lee 
> 
> *** Mostly my opinion, only.
> 
> 
> 
> On 2 Aug 2013, at 16:08, Lo?c Hoguin <essen at ninenines.eu> wrote:
> 
>> Please tell us what you think makes Riak superior.
>> 
>> On 08/02/2013 05:06 PM, Florent Gallaire wrote:
>>> I love the farwest technical choices. But Riak seems to only be the
>>> "prototype' database, and PostgreSQL the real target.
>>> 
>>> FMO, this is a huge fail. Riak is by far superior to PostgreSQL. I
>>> want Riak, who really wants PostgresSQL ??
>>> 
>>> Florent
>> 
>> 
>> -- 
>> Lo?c Hoguin
>> Erlang Cowboy
>> Nine Nines
>> http://ninenines.eu
>> _______________________________________________
>> Extend mailing list
>> Extend at lists.ninenines.eu
>> http://lists.ninenines.eu:81/listinfo/extend
> 
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend
> 



From fgallaire at gmail.com  Fri Aug  2 17:33:32 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:33:32 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <[email protected]>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
Message-ID: <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>

> I said no activity, I didn't say no members. Please keep your complaints
> about the tool down, it's got nothing to do with it, and you just end up
> spamming people here.
>
> All development happens on IRC, so this leaves the mailing lists only useful
> for questions, which should be rarer over time considering the docs keep
> improving and the archives provide great answers for the rest. It's all
> good.

I don't agree. More you have users, more you should have questions on
the mailing list, even if the documentation is improving.

I'm on the mailing lists of **a lot** of free software with great
documentations, and they are very active.

Where is the history of the choices/debates made on IRC ?

Florent

-- 
FLOSS Engineer & Lawyer


From lee.sylvester at gmail.com  Fri Aug  2 17:33:53 2013
From: lee.sylvester at gmail.com (Lee Sylvester)
Date: Fri, 2 Aug 2013 16:33:53 +0100
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <CAB9F1cdo2SLt2hdtjik1RtXPRGOQAxVEdr2Nxyx_06L=dbybJg@mail.gmail.com>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1cdo2SLt2hdtjik1RtXPRGOQAxVEdr2Nxyx_06L=dbybJg@mail.gmail.com>
Message-ID: <[email protected]>

NoSQL is a trend, but is often not the best choice for data storage.  The reason it has had a strong revival recently (no, NoSQL is not a new thing) is because it is simpler for non-SQL developers to jump into and requires less thought on structuring your data.  However, there are many scenarios where NoSQL is a bad choice.  For example, I would certainly hope my bank doesn't log my transactions using NoSQL!

Lee




On 2 Aug 2013, at 16:25, Florent Gallaire <fgallaire at gmail.com> wrote:

> On Fri, Aug 2, 2013 at 5:08 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:
>> Please tell us what you think makes Riak superior.
> 
> Riak is written in Erlang. See your own argumentations on why Erlang
> is the best langage to program high load/fault-tolerent web software.
> 
> Riak is written in Erlang, as all the 99 other soft -> good
> integration of the whole.
> 
> Riak is a NoSQL Dynamo database with Availability and Partition
> tolerance, and this is what I want for my web applications. PostgreSQL
> is a SQL Availability and Consistency old school database.
> 
> Riak is just what want a developer who use erlang to have a scaling platform.
> 
> Florent
> 
> -- 
> FLOSS Engineer & Lawyer
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend



From essen at ninenines.eu  Fri Aug  2 17:35:13 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:35:13 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <[email protected]>
Message-ID: <[email protected]>

Let me clarify a few misconceptions here. (Mostly to show the choice 
isn't random, don't take it wrong.)

Riak and Riak CS are two different things. You most likely don't want to 
run them together, especially considering the hardware requirements will 
differ.

Riak core, pipes, etc. are not really useful if you only use Riak as a 
data store. It's cool that your DB has a great distributed processing 
framework but pretty useless when you just want to retrieve some data 
and format it in a web page.

Riak has clustering, yes. PostgreSQL has clustering too.

Riak has data-center aware clustering also if you get Riak Enterprise. 
But it costs a lot (per node!). You can do the same with PostgreSQL at a 
fraction of the price.

Riak is built on Erlang, sure. But why should I care? I only want it to 
handle my data. I don't want to look at the code. PostgreSQL is a much 
proven piece of software.

On 08/02/2013 05:20 PM, Lee Sylvester wrote:
> It's a bit like comparing sports cars to superbikes.  Riak has some very powerful features; Pipes, true clustering, fault tolerance, Riak CS etc.  Plus, it's built on Erlang :-)  PostgreSQL has SQL queries, real tables (rather than simple corruptible namespacing), complex query capabilities, real data types etc.  Each has their place.  For typical websites, PostgreSQL is the better choice.  For distributed applications, Riak is often the better choice. ***
>
> Lee
>
> *** Mostly my opinion, only.
>
>
>
> On 2 Aug 2013, at 16:08, Lo?c Hoguin <essen at ninenines.eu> wrote:
>
>> Please tell us what you think makes Riak superior.
>>
>> On 08/02/2013 05:06 PM, Florent Gallaire wrote:
>>> I love the farwest technical choices. But Riak seems to only be the
>>> "prototype' database, and PostgreSQL the real target.
>>>
>>> FMO, this is a huge fail. Riak is by far superior to PostgreSQL. I
>>> want Riak, who really wants PostgresSQL ??
>>>
>>> Florent
>>>
>>
>>
>> --
>> Lo?c Hoguin
>> Erlang Cowboy
>> Nine Nines
>> http://ninenines.eu
>> _______________________________________________
>> Extend mailing list
>> Extend at lists.ninenines.eu
>> http://lists.ninenines.eu:81/listinfo/extend
>


-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From fgallaire at gmail.com  Fri Aug  2 17:35:58 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:35:58 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1cdo2SLt2hdtjik1RtXPRGOQAxVEdr2Nxyx_06L=dbybJg@mail.gmail.com>
 <[email protected]>
Message-ID: <CAB9F1cdp2DwdhvFre+y0AMrugmvOvUB3GLY6T7AczzRG3aZLTg@mail.gmail.com>

> For example, I would certainly hope my bank doesn't log my transactions using NoSQL!

You're right, but is Farwest designed to develop banf software ? I
don't think so.

Florent

-- 
FLOSS Engineer & Lawyer


From fgallaire at gmail.com  Fri Aug  2 17:39:04 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:39:04 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <[email protected]>
 <[email protected]>
Message-ID: <CAB9F1cc0e+DqtTUW-YKEBW2LjF7b3i2Q0vbawDPoDuMB4P3CEQ@mail.gmail.com>

> PostgreSQL is a much proven piece of software.

Ouch !! And Apache is a much proven piece of software than cowboy, why
don't use it for Farwest ?

Florent


-- 
FLOSS Engineer & Lawyer


From essen at ninenines.eu  Fri Aug  2 17:39:58 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:39:58 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <CAB9F1cdo2SLt2hdtjik1RtXPRGOQAxVEdr2Nxyx_06L=dbybJg@mail.gmail.com>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1cdo2SLt2hdtjik1RtXPRGOQAxVEdr2Nxyx_06L=dbybJg@mail.gmail.com>
Message-ID: <[email protected]>

On 08/02/2013 05:25 PM, Florent Gallaire wrote:
> On Fri, Aug 2, 2013 at 5:08 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:
>> Please tell us what you think makes Riak superior.
>
> Riak is written in Erlang. See your own argumentations on why Erlang
> is the best langage to program high load/fault-tolerent web software.
 >
> Riak is written in Erlang, as all the 99 other soft -> good
> integration of the whole.

See the post I just sent. I have no reason to care about the language 
here. It's not going to run in the same node. I'm not going to look at 
it. And PostgreSQL is a much proven software, much more than Riak who's 
had issues with the Erlang schedulers and more and is still young.

> Riak is a NoSQL Dynamo database with Availability and Partition
> tolerance, and this is what I want for my web applications. PostgreSQL
> is a SQL Availability and Consistency old school database.

The need for partitioning comes a *lot* later for SQL databases. They 
can deal with big amounts of data just fine. And Farwest is made for 
small to medium applications, therefore the issue will likely never come 
up until Farwest itself becomes the issue.

> Riak is just what want a developer who use erlang to have a scaling platform.

This is the first time I hear complaints about choosing PostgreSQL.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From essen at ninenines.eu  Fri Aug  2 17:41:39 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:41:39 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <CAB9F1cc0e+DqtTUW-YKEBW2LjF7b3i2Q0vbawDPoDuMB4P3CEQ@mail.gmail.com>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <CAB9F1cc0e+DqtTUW-YKEBW2LjF7b3i2Q0vbawDPoDuMB4P3CEQ@mail.gmail.com>
Message-ID: <[email protected]>

On 08/02/2013 05:39 PM, Florent Gallaire wrote:
>> PostgreSQL is a much proven piece of software.
>
> Ouch !! And Apache is a much proven piece of software than cowboy, why
> don't use it for Farwest ?

Because CGI, PHP, Perl, ... aren't. But you can put Apache in front of 
Farwest just fine if you need to.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From lee.sylvester at gmail.com  Fri Aug  2 17:43:49 2013
From: lee.sylvester at gmail.com (Lee Sylvester)
Date: Fri, 2 Aug 2013 16:43:49 +0100
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <[email protected]>
 <[email protected]>
Message-ID: <[email protected]>

Hey, don't direct that at me :-S  I was agreeing with you :-D

The only point I would differ with (and I may be wrong, as it was about 12 months ago that I researched this) is that I do feel, for clustering, that Riak does it better.  I'd much rather the dynamo model than a master-to-many slaves model.

Lee



On 2 Aug 2013, at 16:35, Lo?c Hoguin <essen at ninenines.eu> wrote:

> Let me clarify a few misconceptions here. (Mostly to show the choice isn't random, don't take it wrong.)
> 
> Riak and Riak CS are two different things. You most likely don't want to run them together, especially considering the hardware requirements will differ.
> 
> Riak core, pipes, etc. are not really useful if you only use Riak as a data store. It's cool that your DB has a great distributed processing framework but pretty useless when you just want to retrieve some data and format it in a web page.
> 
> Riak has clustering, yes. PostgreSQL has clustering too.
> 
> Riak has data-center aware clustering also if you get Riak Enterprise. But it costs a lot (per node!). You can do the same with PostgreSQL at a fraction of the price.
> 
> Riak is built on Erlang, sure. But why should I care? I only want it to handle my data. I don't want to look at the code. PostgreSQL is a much proven piece of software.
> 
> On 08/02/2013 05:20 PM, Lee Sylvester wrote:
>> It's a bit like comparing sports cars to superbikes.  Riak has some very powerful features; Pipes, true clustering, fault tolerance, Riak CS etc.  Plus, it's built on Erlang :-)  PostgreSQL has SQL queries, real tables (rather than simple corruptible namespacing), complex query capabilities, real data types etc.  Each has their place.  For typical websites, PostgreSQL is the better choice.  For distributed applications, Riak is often the better choice. ***
>> 
>> Lee
>> 
>> *** Mostly my opinion, only.
>> 
>> 
>> 
>> On 2 Aug 2013, at 16:08, Lo?c Hoguin <essen at ninenines.eu> wrote:
>> 
>>> Please tell us what you think makes Riak superior.
>>> 
>>> On 08/02/2013 05:06 PM, Florent Gallaire wrote:
>>>> I love the farwest technical choices. But Riak seems to only be the
>>>> "prototype' database, and PostgreSQL the real target.
>>>> 
>>>> FMO, this is a huge fail. Riak is by far superior to PostgreSQL. I
>>>> want Riak, who really wants PostgresSQL ??
>>>> 
>>>> Florent
>>>> 
>>> 
>>> 
>>> --
>>> Lo?c Hoguin
>>> Erlang Cowboy
>>> Nine Nines
>>> http://ninenines.eu
>>> _______________________________________________
>>> Extend mailing list
>>> Extend at lists.ninenines.eu
>>> http://lists.ninenines.eu:81/listinfo/extend
>> 
> 
> 
> -- 
> Lo?c Hoguin
> Erlang Cowboy
> Nine Nines
> http://ninenines.eu



From essen at ninenines.eu  Fri Aug  2 17:45:07 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:45:07 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
Message-ID: <[email protected]>

On 08/02/2013 05:33 PM, Florent Gallaire wrote:
> Where is the history of the choices/debates made on IRC ?

No such thing. No need for it either, the choices tend to change a few 
times until things stabilize.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From fgallaire at gmail.com  Fri Aug  2 17:46:53 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:46:53 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
Message-ID: <CAB9F1cco6H-t=L6FXu1aa6O5opNVoVqAZbm2a=eRxAp+GD+awA@mail.gmail.com>

> The only point I would differ with (and I may be wrong, as it was about 12 months ago that I researched this) is that I do feel, for clustering, that Riak does it better.  I'd much rather the dynamo model than a master-to-many slaves model.

Yes you're right, all clustering are far to be equal. Dynamo is really
great, and master-to-master is just an archaic way to do things you
don't really know to do.

Florent

-- 
FLOSS Engineer & Lawyer


From essen at ninenines.eu  Fri Aug  2 17:47:39 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:47:39 +0200
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <[email protected]>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
Message-ID: <[email protected]>

I know, hence the "don't take it wrong".

You have a few different projects enabling multi-master replication for 
PostgreSQL. It's not an issue.

On 08/02/2013 05:43 PM, Lee Sylvester wrote:
> Hey, don't direct that at me :-S  I was agreeing with you :-D
>
> The only point I would differ with (and I may be wrong, as it was about 12 months ago that I researched this) is that I do feel, for clustering, that Riak does it better.  I'd much rather the dynamo model than a master-to-many slaves model.
>
> Lee
>
>
>
> On 2 Aug 2013, at 16:35, Lo?c Hoguin <essen at ninenines.eu> wrote:
>
>> Let me clarify a few misconceptions here. (Mostly to show the choice isn't random, don't take it wrong.)
>>
>> Riak and Riak CS are two different things. You most likely don't want to run them together, especially considering the hardware requirements will differ.
>>
>> Riak core, pipes, etc. are not really useful if you only use Riak as a data store. It's cool that your DB has a great distributed processing framework but pretty useless when you just want to retrieve some data and format it in a web page.
>>
>> Riak has clustering, yes. PostgreSQL has clustering too.
>>
>> Riak has data-center aware clustering also if you get Riak Enterprise. But it costs a lot (per node!). You can do the same with PostgreSQL at a fraction of the price.
>>
>> Riak is built on Erlang, sure. But why should I care? I only want it to handle my data. I don't want to look at the code. PostgreSQL is a much proven piece of software.
>>
>> On 08/02/2013 05:20 PM, Lee Sylvester wrote:
>>> It's a bit like comparing sports cars to superbikes.  Riak has some very powerful features; Pipes, true clustering, fault tolerance, Riak CS etc.  Plus, it's built on Erlang :-)  PostgreSQL has SQL queries, real tables (rather than simple corruptible namespacing), complex query capabilities, real data types etc.  Each has their place.  For typical websites, PostgreSQL is the better choice.  For distributed applications, Riak is often the better choice. ***
>>>
>>> Lee
>>>
>>> *** Mostly my opinion, only.
>>>
>>>
>>>
>>> On 2 Aug 2013, at 16:08, Lo?c Hoguin <essen at ninenines.eu> wrote:
>>>
>>>> Please tell us what you think makes Riak superior.
>>>>
>>>> On 08/02/2013 05:06 PM, Florent Gallaire wrote:
>>>>> I love the farwest technical choices. But Riak seems to only be the
>>>>> "prototype' database, and PostgreSQL the real target.
>>>>>
>>>>> FMO, this is a huge fail. Riak is by far superior to PostgreSQL. I
>>>>> want Riak, who really wants PostgresSQL ??
>>>>>
>>>>> Florent
>>>>>
>>>>
>>>>
>>>> --
>>>> Lo?c Hoguin
>>>> Erlang Cowboy
>>>> Nine Nines
>>>> http://ninenines.eu
>>>> _______________________________________________
>>>> Extend mailing list
>>>> Extend at lists.ninenines.eu
>>>> http://lists.ninenines.eu:81/listinfo/extend
>>>
>>
>>
>> --
>> Lo?c Hoguin
>> Erlang Cowboy
>> Nine Nines
>> http://ninenines.eu
>


-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From fgallaire at gmail.com  Fri Aug  2 17:49:00 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:49:00 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <[email protected]>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
 <[email protected]>
Message-ID: <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>

> No such thing. No need for it either, the choices tend to change a few times
> until things stabilize.

This is a really wrong way. Free software needs public transparency.

Florent

-- 
FLOSS Engineer & Lawyer


From essen at ninenines.eu  Fri Aug  2 17:50:32 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 02 Aug 2013 17:50:32 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
 <[email protected]>
 <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
Message-ID: <[email protected]>

On 08/02/2013 05:49 PM, Florent Gallaire wrote:
>> No such thing. No need for it either, the choices tend to change a few times
>> until things stabilize.
>
> This is a really wrong way. Free software needs public transparency.

The regular contributors don't seem to complain.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From tristan.sloughter at gmail.com  Fri Aug  2 17:52:17 2013
From: tristan.sloughter at gmail.com (Tristan Sloughter)
Date: Fri, 02 Aug 2013 08:52:17 -0700
Subject: [99s-extend] Mailing lists
In-Reply-To: <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
 <[email protected]>
 <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
Message-ID: <[email protected]>

Public transparency like a public IRC channel anyone can join and log?

On Fri, Aug 2, 2013, at 08:49 AM, Florent Gallaire wrote:
> > No such thing. No need for it either, the choices tend to change a few times
> > until things stabilize.
> 
> This is a really wrong way. Free software needs public transparency.
> 
> Florent
> 
> -- 
> FLOSS Engineer & Lawyer
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend


From fgallaire at gmail.com  Fri Aug  2 17:54:34 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Fri, 2 Aug 2013 17:54:34 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <[email protected]>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
 <[email protected]>
 <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
 <[email protected]>
Message-ID: <CAB9F1cdfRBtfAYzu99hOt9OKsv7MpVMyAPLmmpA_Bazqfp3W8A@mail.gmail.com>

On Fri, Aug 2, 2013 at 5:52 PM, Tristan Sloughter
<tristan.sloughter at gmail.com> wrote:
> Public transparency like a public IRC channel anyone can join and log?

Haha, what a joke. It's a pity you don't understand that.

Florent

-- 
FLOSS Engineer & Lawyer


From tristan.sloughter at gmail.com  Fri Aug  2 17:54:38 2013
From: tristan.sloughter at gmail.com (Tristan Sloughter)
Date: Fri, 02 Aug 2013 08:54:38 -0700
Subject: [99s-extend] Riak in Farwest
In-Reply-To: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
References: <CAB9F1ccXD0RMYrMeu1zOr=s638sWN4DBQcVLrn9Rk8_q+xWKKA@mail.gmail.com>
Message-ID: <[email protected]>

Me for one. Rarely have a use case that fits Riak but daily have use
cases that fit a RDBMS, and Postgres is the best of those in my opinion.

On Fri, Aug 2, 2013, at 08:06 AM, Florent Gallaire wrote:
> I love the farwest technical choices. But Riak seems to only be the
> "prototype' database, and PostgreSQL the real target.
> 
> FMO, this is a huge fail. Riak is by far superior to PostgreSQL. I
> want Riak, who really wants PostgresSQL ??
> 
> Florent
> 
> -- 
> FLOSS Engineer & Lawyer
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend


From jeremy at quarkgames.com  Fri Aug  2 21:33:59 2013
From: jeremy at quarkgames.com (Jeremy Ong)
Date: Fri, 2 Aug 2013 12:33:59 -0700
Subject: [99s-extend] Mailing lists
In-Reply-To: <CAB9F1cdfRBtfAYzu99hOt9OKsv7MpVMyAPLmmpA_Bazqfp3W8A@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
 <[email protected]>
 <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
 <[email protected]>
 <CAB9F1cdfRBtfAYzu99hOt9OKsv7MpVMyAPLmmpA_Bazqfp3W8A@mail.gmail.com>
Message-ID: <CAKD1GY56gKubvDkz911s9a47Bnu-YxGk48xJfe0DkpitfbwH3g@mail.gmail.com>

Florent, I suggest you actually contribute something before telling
the project maintainer how to run things and flaming people who *have*
contributed.

On Fri, Aug 2, 2013 at 8:54 AM, Florent Gallaire <fgallaire at gmail.com> wrote:
> On Fri, Aug 2, 2013 at 5:52 PM, Tristan Sloughter
> <tristan.sloughter at gmail.com> wrote:
>> Public transparency like a public IRC channel anyone can join and log?
>
> Haha, what a joke. It's a pity you don't understand that.
>
> Florent
>
> --
> FLOSS Engineer & Lawyer
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend


From edgurgel at gmail.com  Fri Aug  2 21:57:22 2013
From: edgurgel at gmail.com (Eduardo Gurgel)
Date: Fri, 2 Aug 2013 16:57:22 -0300
Subject: [99s-extend] Fwd:  Mailing lists
In-Reply-To: <CAKAMJXjcwWJf7STqau=ghbsnnZRmobOSqxD9fjrrkgETu+v9Kw@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
 <[email protected]>
 <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
 <[email protected]>
 <CAB9F1cdfRBtfAYzu99hOt9OKsv7MpVMyAPLmmpA_Bazqfp3W8A@mail.gmail.com>
 <CAKD1GY56gKubvDkz911s9a47Bnu-YxGk48xJfe0DkpitfbwH3g@mail.gmail.com>
 <CAKAMJXjcwWJf7STqau=ghbsnnZRmobOSqxD9fjrrkgETu+v9Kw@mail.gmail.com>
Message-ID: <CAKAMJXhSdYePQz55u5Hw6E1Qk-Je_o+ydP4vC+Yma=u=tBy4Jw@mail.gmail.com>

Forgot to reply to all

---------- Forwarded message ----------
From: Eduardo Gurgel <edgurgel at gmail.com>
Date: Fri, Aug 2, 2013 at 4:57 PM
Subject: Re: [99s-extend] Mailing lists
To: Jeremy Ong <jeremy at quarkgames.com>




On Fri, Aug 2, 2013 at 4:33 PM, Jeremy Ong <jeremy at quarkgames.com> wrote:

> Florent, I suggest you actually contribute something before telling
> the project maintainer how to run things and flaming people who *have*
> contributed.
>

Agreed.

Too much pointing finger on this thread...

-- 
Eduardo



-- 
Eduardo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130802/4f7baee0/attachment.html>

From fgallaire at gmail.com  Sat Aug  3 00:16:30 2013
From: fgallaire at gmail.com (Florent Gallaire)
Date: Sat, 3 Aug 2013 00:16:30 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <CAKD1GY56gKubvDkz911s9a47Bnu-YxGk48xJfe0DkpitfbwH3g@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
 <[email protected]>
 <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
 <[email protected]>
 <CAB9F1cdfRBtfAYzu99hOt9OKsv7MpVMyAPLmmpA_Bazqfp3W8A@mail.gmail.com>
 <CAKD1GY56gKubvDkz911s9a47Bnu-YxGk48xJfe0DkpitfbwH3g@mail.gmail.com>
Message-ID: <CAB9F1cfpRX=WnK79_Q5s+hsW-uuybujnuqt6TeBcSXp5TbiLsg@mail.gmail.com>

> Florent, I suggest you actually contribute something before telling
> the project maintainer how to run things and flaming people who *have*
> contributed.

Jeremy, I tried to test farwest very early :
https://github.com/extend/farwest/pull/4

My "bad idee" of a server-sent events handler is now part of bullet :
https://github.com/extend/bullet/issues/16

Jeremy, maybe I haven't contribute something on this project because :
- I spend a lot of time working as a lawyer
- I spend a lot of time working on other free software
- I'm not yet a great Erlang programmer

AND

- There's no visibility on what is really doing, and who is doing it,
and why, and how it's decided. So I can't lose more time on that
because I can't know what is happened and what will happen.

I flame nobody. I give the 2 cents of help I can give. This is a
contribution. You can think it's useless, but I don't think so.

In free software, if you want a great success, you should be more open
that just have a free software licence.
You should do the life easier for the people interested in this
project and who want to help. You can think it's not a problem, but I
think it is. Is that a flame ?

Florent

FLOSS Engineer & Lawyer


From essen at ninenines.eu  Sat Aug  3 09:13:50 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Sat, 03 Aug 2013 09:13:50 +0200
Subject: [99s-extend] Mailing lists
In-Reply-To: <CAB9F1cfpRX=WnK79_Q5s+hsW-uuybujnuqt6TeBcSXp5TbiLsg@mail.gmail.com>
References: <CAB9F1ceSGWQMLisLg67Hakg5BkEPEqNMgkwQhujV=9z_uE89vg@mail.gmail.com>
 <[email protected]>
 <CAB9F1cfDsMpoaD+YYGm+uErfqk1EM+piV4FN1KFOrdOGnB4BKA@mail.gmail.com>
 <[email protected]>
 <CAB9F1ce6aVHGpNsSwApUGOyPGgruMsRrrZvWJc=EsqQE6Rae5g@mail.gmail.com>
 <[email protected]>
 <CAB9F1ccF7aY92-00nZYJuzyu+xYbme6zeHv_9kt_Oj4FLJhooA@mail.gmail.com>
 <[email protected]>
 <CAB9F1cdfRBtfAYzu99hOt9OKsv7MpVMyAPLmmpA_Bazqfp3W8A@mail.gmail.com>
 <CAKD1GY56gKubvDkz911s9a47Bnu-YxGk48xJfe0DkpitfbwH3g@mail.gmail.com>
 <CAB9F1cfpRX=WnK79_Q5s+hsW-uuybujnuqt6TeBcSXp5TbiLsg@mail.gmail.com>
Message-ID: <[email protected]>

On 08/03/2013 12:16 AM, Florent Gallaire wrote:
> - There's no visibility on what is really doing, and who is doing it,
> and why, and how it's decided. So I can't lose more time on that
> because I can't know what is happened and what will happen.

Or, you know, you could just open a ticket or ask like anyone else, 
preferrably the former. Chances are whatever you're thinking of doing 
has no chance of being merged at all, or could be interesting but only 
if certain implementation details are respected, or needs to involve 
other people.

Even if we did put more info on who does what, this still wouldn't 
remove the necessity for you to ask if you want to avoid losing your time.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From thebullno1 at gmail.com  Mon Aug  5 07:38:04 2013
From: thebullno1 at gmail.com (Bach Le)
Date: Mon, 5 Aug 2013 13:38:04 +0800
Subject: [99s-extend] Mailing lists
Message-ID: <CAG=BNYp2-Z04DZhXYDqEANBm=PS5CLzOCbGQD8k3JbTFr0Dawg@mail.gmail.com>

>You can think it's not a problem, but Ithink it is. Is that a flame ?
This is a flame:
> Haha, what a joke. It's a pity you don't understand that.

I for one, prefer Postgres. Not everything can be mapped to kv and that's
the only thing Riak is good for. It's not fit for a general purpose
database.
To me, NoSQL is about specialization. Each db excels at one type of
operation (and then there's mongo, but that's for another time), while
RDBMSs offer general purpose solutions. I begin my projects with an RDBMS
(usually Postgres) and when a particular piece of data is the bottleneck, I
move it to the appropriate NoSQL db.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130805/9fd5783b/attachment.html>

From essen at ninenines.eu  Wed Aug 14 19:50:18 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Wed, 14 Aug 2013 19:50:18 +0200
Subject: [99s-extend] [ANN] Farwest 0.3.0
Message-ID: <[email protected]>

It's finally here!

  *  https://github.com/extend/farwest/

It's still a mess in the two other repositories so I recommend waiting 
before digging in too much. This is just a direct port of the prototype 
to a more workable build suite and repository structure.

  *  https://github.com/extend/farwest_core/
  *  https://github.com/extend/farwest_ui/

A lot of work will be done on farwest_core next, while at the same time 
the frontend dude takes care of making the UI good.

Enjoy!

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From essen at ninenines.eu  Thu Aug 15 16:19:42 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Thu, 15 Aug 2013 16:19:42 +0200
Subject: [99s-extend] [ANN] erlang.mk build tool
Message-ID: <[email protected]>

Hello friendly people,

I would like to make an official announcement of erlang.mk now that all 
the features I wanted are in.

erlang.mk is a rebar replacement. It was initially created for allowing 
a faster development process than rebar and for better compatibility 
with Linux build tools. It should work on Linux and OSX with GNU Make 
installed.

Projects using erlang.mk are still compatible with rebar. Dependencies 
fetched by rebar are stored in the same deps/ directory, and projects 
using erlang.mk can still be used as rebar dependencies, with or without 
a rebar.config file.

erlang.mk also features a simple package index. Try `make pkg-list` to 
list all packages currently available. All the packages listed are 
compatible with erlang.mk with no tweaking required.

Makefiles written with erlang.mk are *VERY* simple, here are two examples:

  *  https://github.com/extend/farwest/blob/master/Makefile
  *  https://github.com/extend/cowboy/blob/master/Makefile

I wrote about erlang.mk and relx recently on the Nine Nines blog. 
erlang.mk is the perfect companion to relx.

  *  http://ninenines.eu/articles/erlang.mk-and-relx

Here are examples of projects that are using and compatible with erlang.mk:

  *  https://github.com/jlouis/etorrent
  *  https://github.com/extend/cowboy
  *  https://github.com/extend/farwest

You can find erlang.mk at the following URL:

  *  https://github.com/extend/erlang.mk

Contributions to the package index are of course welcome! The only 
requirement is that the package is to be compatible with erlang.mk 
itself. Just send a PR to the erlang.mk project updating the 
packages.v1.txt!

Enjoy!

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From desired.mta at gmail.com  Thu Aug 15 17:07:42 2013
From: desired.mta at gmail.com (=?UTF-8?Q?Motiejus_Jak=C5=A1tys?=)
Date: Thu, 15 Aug 2013 17:07:42 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
Message-ID: <CAFVMu-qtqDgB+-W6KXY1iYudeU-KsbF-OkNEEDTX8Hac+5MxoQ@mail.gmail.com>

On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:
> Hello friendly people,
>
> I would like to make an official announcement of erlang.mk now that all the
> features I wanted are in.

Please include an ability to cleanly override any target so make does
not emit warnings about overwritten target. There are a few ways to do
it, but I find this the easiest: prefix every target in erlang.mk with
a variable:

$(.erlang-mk-all)all:
  <your stuff>

That way, if $(.erlang-mk-all) is defined (from my application
Makefile before including erlang.mk), your 'all' target will be the
one that does not cause me warnings.

Motiejus Jak?tys


From essen at ninenines.eu  Thu Aug 15 18:32:04 2013
From: essen at ninenines.eu (=?UTF-8?B?TG/Dr2MgSG9ndWlu?=)
Date: Thu, 15 Aug 2013 18:32:04 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <CAFVMu-qtqDgB+-W6KXY1iYudeU-KsbF-OkNEEDTX8Hac+5MxoQ@mail.gmail.com>
References: <[email protected]>
 <CAFVMu-qtqDgB+-W6KXY1iYudeU-KsbF-OkNEEDTX8Hac+5MxoQ@mail.gmail.com>
Message-ID: <[email protected]>

On 08/15/2013 05:07 PM, Motiejus Jak?tys wrote:
> On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:
>> Hello friendly people,
>>
>> I would like to make an official announcement of erlang.mk now that all the
>> features I wanted are in.
>
> Please include an ability to cleanly override any target so make does
> not emit warnings about overwritten target. There are a few ways to do
> it, but I find this the easiest: prefix every target in erlang.mk with
> a variable:
>
> $(.erlang-mk-all)all:
>    <your stuff>
>
> That way, if $(.erlang-mk-all) is defined (from my application
> Makefile before including erlang.mk), your 'all' target will be the
> one that does not cause me warnings.

Yes I was thinking about this, but so far nobody needed it. If you do, 
though, patches welcome!

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From essen at ninenines.eu  Fri Aug 16 16:34:56 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 16 Aug 2013 16:34:56 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
Message-ID: <[email protected]>

On 08/16/2013 10:39 AM, Benoit Chesneau wrote:
> The big problem with erlang.mk <http://erlang.mk> is requiring to have
> gmake and more importantly wget installed imo.

wget is only used for fetching the package index file. I'm sure if it 
doesn't work somewhere it'll be patched eventually.

> Which makes it quite annoying to distribute on systems that have none of
> them. It would be interrestin to have the support for curl for example.
> Also what are the makefile extensions that you really need to require gmake?

No idea. Patches are welcome for compatibility with different OS/build 
tools (as long as it's not "rewrite the whole file" of course, then 
you're better off just using gmake).

> - benoit
>
>
> On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu
> <mailto:essen at ninenines.eu>> wrote:
>
>     Hello friendly people,
>
>     I would like to make an official announcement of erlang.mk
>     <http://erlang.mk> now that all the features I wanted are in.
>
>     erlang.mk <http://erlang.mk> is a rebar replacement. It was
>     initially created for allowing a faster development process than
>     rebar and for better compatibility with Linux build tools. It should
>     work on Linux and OSX with GNU Make installed.
>
>     Projects using erlang.mk <http://erlang.mk> are still compatible
>     with rebar. Dependencies fetched by rebar are stored in the same
>     deps/ directory, and projects using erlang.mk <http://erlang.mk> can
>     still be used as rebar dependencies, with or without a rebar.config
>     file.
>
>     erlang.mk <http://erlang.mk> also features a simple package index.
>     Try `make pkg-list` to list all packages currently available. All
>     the packages listed are compatible with erlang.mk <http://erlang.mk>
>     with no tweaking required.
>
>     Makefiles written with erlang.mk <http://erlang.mk> are *VERY*
>     simple, here are two examples:
>
>       * https://github.com/extend/__farwest/blob/master/Makefile
>     <https://github.com/extend/farwest/blob/master/Makefile>
>       * https://github.com/extend/__cowboy/blob/master/Makefile
>     <https://github.com/extend/cowboy/blob/master/Makefile>
>
>     I wrote about erlang.mk <http://erlang.mk> and relx recently on the
>     Nine Nines blog. erlang.mk <http://erlang.mk> is the perfect
>     companion to relx.
>
>       * http://ninenines.eu/articles/__erlang.mk-and-relx
>     <http://ninenines.eu/articles/erlang.mk-and-relx>
>
>     Here are examples of projects that are using and compatible with
>     erlang.mk <http://erlang.mk>:
>
>       * https://github.com/jlouis/__etorrent
>     <https://github.com/jlouis/etorrent>
>       * https://github.com/extend/__cowboy
>     <https://github.com/extend/cowboy>
>       * https://github.com/extend/__farwest
>     <https://github.com/extend/farwest>
>
>     You can find erlang.mk <http://erlang.mk> at the following URL:
>
>       * https://github.com/extend/__erlang.mk
>     <https://github.com/extend/erlang.mk>
>
>     Contributions to the package index are of course welcome! The only
>     requirement is that the package is to be compatible with erlang.mk
>     <http://erlang.mk> itself. Just send a PR to the erlang.mk
>     <http://erlang.mk> project updating the packages.v1.txt!
>
>     Enjoy!
>
>     --
>     Lo?c Hoguin
>     Erlang Cowboy
>     Nine Nines
>     http://ninenines.eu
>     _________________________________________________
>     erlang-questions mailing list
>     erlang-questions at erlang.org <mailto:erlang-questions at erlang.org>
>     http://erlang.org/mailman/__listinfo/erlang-questions
>     <http://erlang.org/mailman/listinfo/erlang-questions>
>
>


-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From jesper.louis.andersen at erlang-solutions.com  Fri Aug 16 10:01:01 2013
From: jesper.louis.andersen at erlang-solutions.com (Jesper Louis Andersen)
Date: Fri, 16 Aug 2013 10:01:01 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
Message-ID: <CAGrdgiWNpD7GAgE-8xHamW9FQSvnp=1SxODXeHy8erK8+P5wVg@mail.gmail.com>

On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:

> I would like to make an official announcement of erlang.mk now that all
> the features I wanted are in.
>

I have been using erlang.mk for a while now, and recently I converted
etorrent to use it as a test of the viability in larger projects. Typical
gotchas:

* Projects has no Makefile. erlang.mk needs one. So add one!
* No `modules` section in the .app file. erlang.mk needs one to replace it.
Not adding this makes relx behave badly.
* If you use relx, it is more strict in what it accepts.
* Relx can't yet overlay sys.config :/

Apart from that, erlang.mk is a bliss to work with. In one project I am
working with:

Core i5 2.4Ghz approx 2010 Macbook Pro, encrypted disk (this hurts
performance like mad):

Cold build:

Rebar: 40 secs
elrang.mk: 42 secs

Build where each file is compiled in advance:

Rebar: 20 secs
erlang.mk: 0.4 secs

For my development cycle, this is important enough to spend time rewriting
projects to use erlang.mk. Also note that rebar.config and erlang.mk can
co-exist, so you don't need to abandon rebar for erlang.mk, which is
important.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130816/1c70f542/attachment.html>

From bchesneau at gmail.com  Fri Aug 16 10:39:27 2013
From: bchesneau at gmail.com (Benoit Chesneau)
Date: Fri, 16 Aug 2013 10:39:27 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
Message-ID: <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>

The big problem with erlang.mk is requiring to have gmake and more
importantly wget installed imo.

Which makes it quite annoying to distribute on systems that have none of
them. It would be interrestin to have the support for curl for example.
Also what are the makefile extensions that you really need to require gmake?

- benoit


On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:

> Hello friendly people,
>
> I would like to make an official announcement of erlang.mk now that all
> the features I wanted are in.
>
> erlang.mk is a rebar replacement. It was initially created for allowing a
> faster development process than rebar and for better compatibility with
> Linux build tools. It should work on Linux and OSX with GNU Make installed.
>
> Projects using erlang.mk are still compatible with rebar. Dependencies
> fetched by rebar are stored in the same deps/ directory, and projects using
> erlang.mk can still be used as rebar dependencies, with or without a
> rebar.config file.
>
> erlang.mk also features a simple package index. Try `make pkg-list` to
> list all packages currently available. All the packages listed are
> compatible with erlang.mk with no tweaking required.
>
> Makefiles written with erlang.mk are *VERY* simple, here are two examples:
>
>  *  https://github.com/extend/**farwest/blob/master/Makefile<https://github.com/extend/farwest/blob/master/Makefile>
>  *  https://github.com/extend/**cowboy/blob/master/Makefile<https://github.com/extend/cowboy/blob/master/Makefile>
>
> I wrote about erlang.mk and relx recently on the Nine Nines blog.
> erlang.mk is the perfect companion to relx.
>
>  *  http://ninenines.eu/articles/**erlang.mk-and-relx<http://ninenines.eu/articles/erlang.mk-and-relx>
>
> Here are examples of projects that are using and compatible with erlang.mk
> :
>
>  *  https://github.com/jlouis/**etorrent<https://github.com/jlouis/etorrent>
>  *  https://github.com/extend/**cowboy <https://github.com/extend/cowboy>
>  *  https://github.com/extend/**farwest<https://github.com/extend/farwest>
>
> You can find erlang.mk at the following URL:
>
>  *  https://github.com/extend/**erlang.mk<https://github.com/extend/erlang.mk>
>
> Contributions to the package index are of course welcome! The only
> requirement is that the package is to be compatible with erlang.mkitself. Just send a PR to the
> erlang.mk project updating the packages.v1.txt!
>
> Enjoy!
>
> --
> Lo?c Hoguin
> Erlang Cowboy
> Nine Nines
> http://ninenines.eu
> ______________________________**_________________
> erlang-questions mailing list
> erlang-questions at erlang.org
> http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130816/ff4591a1/attachment.html>

From dronnikov at gmail.com  Fri Aug 16 13:25:20 2013
From: dronnikov at gmail.com (Vladimir Dronnikov)
Date: Fri, 16 Aug 2013 15:25:20 +0400
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
Message-ID: <CAE9na_MBpyKA1K0wVTf_NA58UNkohOmGQRSx6cy+q8ds0kjtGQ@mail.gmail.com>

I believe
curl -L $(PKG_FILE_URL) >$(PKG_FILE)
is kinda drop-in replacement for
wget -O $(PKG_FILE) $(PKG_FILE_URL)
used in erlang.mk.

Should be tested


On Fri, Aug 16, 2013 at 12:39 PM, Benoit Chesneau <bchesneau at gmail.com>wrote:

> The big problem with erlang.mk is requiring to have gmake and more
> importantly wget installed imo.
>
> Which makes it quite annoying to distribute on systems that have none of
> them. It would be interrestin to have the support for curl for example.
> Also what are the makefile extensions that you really need to require gmake?
>
> - benoit
>
>
> On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu> wrote:
>
>> Hello friendly people,
>>
>> I would like to make an official announcement of erlang.mk now that all
>> the features I wanted are in.
>>
>> erlang.mk is a rebar replacement. It was initially created for allowing
>> a faster development process than rebar and for better compatibility with
>> Linux build tools. It should work on Linux and OSX with GNU Make installed.
>>
>> Projects using erlang.mk are still compatible with rebar. Dependencies
>> fetched by rebar are stored in the same deps/ directory, and projects using
>> erlang.mk can still be used as rebar dependencies, with or without a
>> rebar.config file.
>>
>> erlang.mk also features a simple package index. Try `make pkg-list` to
>> list all packages currently available. All the packages listed are
>> compatible with erlang.mk with no tweaking required.
>>
>> Makefiles written with erlang.mk are *VERY* simple, here are two
>> examples:
>>
>>  *  https://github.com/extend/**farwest/blob/master/Makefile<https://github.com/extend/farwest/blob/master/Makefile>
>>  *  https://github.com/extend/**cowboy/blob/master/Makefile<https://github.com/extend/cowboy/blob/master/Makefile>
>>
>> I wrote about erlang.mk and relx recently on the Nine Nines blog.
>> erlang.mk is the perfect companion to relx.
>>
>>  *  http://ninenines.eu/articles/**erlang.mk-and-relx<http://ninenines.eu/articles/erlang.mk-and-relx>
>>
>> Here are examples of projects that are using and compatible with
>> erlang.mk:
>>
>>  *  https://github.com/jlouis/**etorrent<https://github.com/jlouis/etorrent>
>>  *  https://github.com/extend/**cowboy <https://github.com/extend/cowboy>
>>  *  https://github.com/extend/**farwest<https://github.com/extend/farwest>
>>
>> You can find erlang.mk at the following URL:
>>
>>  *  https://github.com/extend/**erlang.mk<https://github.com/extend/erlang.mk>
>>
>> Contributions to the package index are of course welcome! The only
>> requirement is that the package is to be compatible with erlang.mkitself. Just send a PR to the
>> erlang.mk project updating the packages.v1.txt!
>>
>> Enjoy!
>>
>> --
>> Lo?c Hoguin
>> Erlang Cowboy
>> Nine Nines
>> http://ninenines.eu
>> ______________________________**_________________
>> erlang-questions mailing list
>> erlang-questions at erlang.org
>> http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
>>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions at erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130816/8f4a69b4/attachment.html>

From steve at srstrong.com  Fri Aug 16 14:27:48 2013
From: steve at srstrong.com (Steve Strong)
Date: Fri, 16 Aug 2013 14:27:48 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
Message-ID: <[email protected]>

Looks good - I like simple!  Quick question, does it support multiple applications, for example a project laid out as:  

/proj
/deps
/stuff

/apps
/app1
/app2

Most of our stuff is in that form, with shared dependencies between the various apps.  Rebar is quite happy with that format, but I can't see how to persuade erlang.mk to handle that.

Cheers,

Steve  

--  
Steve Strong
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Thursday, 15 August 2013 at 16:19, Lo?c Hoguin wrote:

> Hello friendly people,
>  
> I would like to make an official announcement of erlang.mk now that all  
> the features I wanted are in.
>  
> erlang.mk is a rebar replacement. It was initially created for allowing  
> a faster development process than rebar and for better compatibility  
> with Linux build tools. It should work on Linux and OSX with GNU Make  
> installed.
>  
> Projects using erlang.mk are still compatible with rebar. Dependencies  
> fetched by rebar are stored in the same deps/ directory, and projects  
> using erlang.mk can still be used as rebar dependencies, with or without  
> a rebar.config file.
>  
> erlang.mk also features a simple package index. Try `make pkg-list` to  
> list all packages currently available. All the packages listed are  
> compatible with erlang.mk with no tweaking required.
>  
> Makefiles written with erlang.mk are *VERY* simple, here are two examples:
>  
> * https://github.com/extend/farwest/blob/master/Makefile
> * https://github.com/extend/cowboy/blob/master/Makefile
>  
> I wrote about erlang.mk and relx recently on the Nine Nines blog.  
> erlang.mk is the perfect companion to relx.
>  
> * http://ninenines.eu/articles/erlang.mk-and-relx
>  
> Here are examples of projects that are using and compatible with erlang.mk:
>  
> * https://github.com/jlouis/etorrent
> * https://github.com/extend/cowboy
> * https://github.com/extend/farwest
>  
> You can find erlang.mk at the following URL:
>  
> * https://github.com/extend/erlang.mk
>  
> Contributions to the package index are of course welcome! The only  
> requirement is that the package is to be compatible with erlang.mk  
> itself. Just send a PR to the erlang.mk project updating the  
> packages.v1.txt!
>  
> Enjoy!
>  
> --  
> Lo?c Hoguin
> Erlang Cowboy
> Nine Nines
> http://ninenines.eu
> _______________________________________________
> erlang-questions mailing list
> erlang-questions at erlang.org (mailto:erlang-questions at erlang.org)
> http://erlang.org/mailman/listinfo/erlang-questions
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130816/a886396a/attachment.html>

From list1 at gjunka.com  Fri Aug 16 16:42:28 2013
From: list1 at gjunka.com (Grzegorz Junka)
Date: Fri, 16 Aug 2013 15:42:28 +0100
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
 <[email protected]>
Message-ID: <[email protected]>

Why not use Erlang for downloading? Surely if erlang.mk is a tool for 
Erlang then it will be very likely installed. For example this target 
downloads Rebar:

# Erlang Rebar downloading, see:
# 
https://groups.google.com/forum/?fromgroups=#!topic/erlang-programming/U0JJ3SeUv5Y
rb_rebar_url=http://cloud.github.com/downloads/basho/rebar/rebar
./rebar:
$(ERL) -noshell -s inets -s ssl \
-eval 'httpc:request(get, {"$(rb_rebar_url)", []}, [], [{stream, 
"./rebar"}])' \
-s init stop
chmod +x ./rebar
REBAR=$(shell (type rebar 2>/dev/null || echo ./rebar) | tail -1 | awk 
'{ print $$NF }')


It could be used to download anything, not just REBAR.

- Greg


On 16/08/2013 15:34, Lo?c Hoguin wrote:
> On 08/16/2013 10:39 AM, Benoit Chesneau wrote:
>> The big problem with erlang.mk <http://erlang.mk> is requiring to have
>> gmake and more importantly wget installed imo.
>
> wget is only used for fetching the package index file. I'm sure if it 
> doesn't work somewhere it'll be patched eventually.
>
>> Which makes it quite annoying to distribute on systems that have none of
>> them. It would be interrestin to have the support for curl for example.
>> Also what are the makefile extensions that you really need to require 
>> gmake?
>
> No idea. Patches are welcome for compatibility with different OS/build 
> tools (as long as it's not "rewrite the whole file" of course, then 
> you're better off just using gmake).
>
>> - benoit
>>
>>
>> On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu
>> <mailto:essen at ninenines.eu>> wrote:
>>
>>     Hello friendly people,
>>
>>     I would like to make an official announcement of erlang.mk
>>     <http://erlang.mk> now that all the features I wanted are in.
>>
>>     erlang.mk <http://erlang.mk> is a rebar replacement. It was
>>     initially created for allowing a faster development process than
>>     rebar and for better compatibility with Linux build tools. It should
>>     work on Linux and OSX with GNU Make installed.
>>
>>     Projects using erlang.mk <http://erlang.mk> are still compatible
>>     with rebar. Dependencies fetched by rebar are stored in the same
>>     deps/ directory, and projects using erlang.mk <http://erlang.mk> can
>>     still be used as rebar dependencies, with or without a rebar.config
>>     file.
>>
>>     erlang.mk <http://erlang.mk> also features a simple package index.
>>     Try `make pkg-list` to list all packages currently available. All
>>     the packages listed are compatible with erlang.mk <http://erlang.mk>
>>     with no tweaking required.
>>
>>     Makefiles written with erlang.mk <http://erlang.mk> are *VERY*
>>     simple, here are two examples:
>>
>>       * https://github.com/extend/__farwest/blob/master/Makefile
>> <https://github.com/extend/farwest/blob/master/Makefile>
>>       * https://github.com/extend/__cowboy/blob/master/Makefile
>> <https://github.com/extend/cowboy/blob/master/Makefile>
>>
>>     I wrote about erlang.mk <http://erlang.mk> and relx recently on the
>>     Nine Nines blog. erlang.mk <http://erlang.mk> is the perfect
>>     companion to relx.
>>
>>       * http://ninenines.eu/articles/__erlang.mk-and-relx
>>     <http://ninenines.eu/articles/erlang.mk-and-relx>
>>
>>     Here are examples of projects that are using and compatible with
>>     erlang.mk <http://erlang.mk>:
>>
>>       * https://github.com/jlouis/__etorrent
>>     <https://github.com/jlouis/etorrent>
>>       * https://github.com/extend/__cowboy
>>     <https://github.com/extend/cowboy>
>>       * https://github.com/extend/__farwest
>>     <https://github.com/extend/farwest>
>>
>>     You can find erlang.mk <http://erlang.mk> at the following URL:
>>
>>       * https://github.com/extend/__erlang.mk
>>     <https://github.com/extend/erlang.mk>
>>
>>     Contributions to the package index are of course welcome! The only
>>     requirement is that the package is to be compatible with erlang.mk
>>     <http://erlang.mk> itself. Just send a PR to the erlang.mk
>>     <http://erlang.mk> project updating the packages.v1.txt!
>>
>>     Enjoy!
>>
>>     --
>>     Lo?c Hoguin
>>     Erlang Cowboy
>>     Nine Nines
>>     http://ninenines.eu
>>     _________________________________________________
>>     erlang-questions mailing list
>>     erlang-questions at erlang.org <mailto:erlang-questions at erlang.org>
>>     http://erlang.org/mailman/__listinfo/erlang-questions
>>     <http://erlang.org/mailman/listinfo/erlang-questions>
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130816/4e596577/attachment.html>

From essen at ninenines.eu  Fri Aug 16 16:42:39 2013
From: essen at ninenines.eu (=?UTF-8?B?TG/Dr2MgSG9ndWlu?=)
Date: Fri, 16 Aug 2013 16:42:39 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
 <[email protected]>
Message-ID: <[email protected]>

Well I'm sure if you create a base Makefile (without erlang.mk) that 
exports DEPS_DIR and then call $(MAKE) on all folders in /apps (which 
would themselves contain Makefiles that use erlang.mk), it would work 
just fine. You can still keep only one erlang.mk in your repos and use 
include ../../erlang.mk instead for example.

But know that this folder structure is a rebar thing and not standard 
(just like /deps you'll say, but that one is insanely useful regardless 
of the project structure otherwise).

On 08/16/2013 02:27 PM, Steve Strong wrote:
> Looks good - I like simple!  Quick question, does it support multiple
> applications, for example a project laid out as:
>
> /proj
> /deps
> /stuff
>
> /apps
> /app1
> /app2
>
> Most of our stuff is in that form, with shared dependencies between the
> various apps.  Rebar is quite happy with that format, but I can't see
> how to persuade erlang.mk to handle that.
>
> Cheers,
>
> Steve
>
> --
> Steve Strong
> Sent with Sparrow <http://www.sparrowmailapp.com/?sig>
>
> On Thursday, 15 August 2013 at 16:19, Lo?c Hoguin wrote:
>
>> Hello friendly people,
>>
>> I would like to make an official announcement of erlang.mk now that all
>> the features I wanted are in.
>>
>> erlang.mk is a rebar replacement. It was initially created for allowing
>> a faster development process than rebar and for better compatibility
>> with Linux build tools. It should work on Linux and OSX with GNU Make
>> installed.
>>
>> Projects using erlang.mk are still compatible with rebar. Dependencies
>> fetched by rebar are stored in the same deps/ directory, and projects
>> using erlang.mk can still be used as rebar dependencies, with or without
>> a rebar.config file.
>>
>> erlang.mk also features a simple package index. Try `make pkg-list` to
>> list all packages currently available. All the packages listed are
>> compatible with erlang.mk with no tweaking required.
>>
>> Makefiles written with erlang.mk are *VERY* simple, here are two examples:
>>
>> * https://github.com/extend/farwest/blob/master/Makefile
>> * https://github.com/extend/cowboy/blob/master/Makefile
>>
>> I wrote about erlang.mk and relx recently on the Nine Nines blog.
>> erlang.mk is the perfect companion to relx.
>>
>> * http://ninenines.eu/articles/erlang.mk-and-relx
>>
>> Here are examples of projects that are using and compatible with
>> erlang.mk:
>>
>> * https://github.com/jlouis/etorrent
>> * https://github.com/extend/cowboy
>> * https://github.com/extend/farwest
>>
>> You can find erlang.mk at the following URL:
>>
>> * https://github.com/extend/erlang.mk
>>
>> Contributions to the package index are of course welcome! The only
>> requirement is that the package is to be compatible with erlang.mk
>> itself. Just send a PR to the erlang.mk project updating the
>> packages.v1.txt!
>>
>> Enjoy!
>>
>> --
>> Lo?c Hoguin
>> Erlang Cowboy
>> Nine Nines
>> http://ninenines.eu
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions at erlang.org <mailto:erlang-questions at erlang.org>
>> http://erlang.org/mailman/listinfo/erlang-questions
>


-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From essen at ninenines.eu  Fri Aug 16 16:44:58 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 16 Aug 2013 16:44:58 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
 <[email protected]> <[email protected]>
Message-ID: <[email protected]>

Starting Erlang takes too long. That's a big reason why erlang.mk was 
created. :)

I recall NetBSD being able to download things with a shell script only 
(as it comes with nothing installed), this would be a more interesting 
solution especially since we can bundle it in the erlang.mk file too.

On 08/16/2013 04:42 PM, Grzegorz Junka wrote:
> Why not use Erlang for downloading? Surely if erlang.mk is a tool for
> Erlang then it will be very likely installed. For example this target
> downloads Rebar:
>
> # Erlang Rebar downloading, see:
> #
> https://groups.google.com/forum/?fromgroups=#!topic/erlang-programming/U0JJ3SeUv5Y
> rb_rebar_url=http://cloud.github.com/downloads/basho/rebar/rebar
> ./rebar:
> $(ERL) -noshell -s inets -s ssl \
> -eval 'httpc:request(get, {"$(rb_rebar_url)", []}, [], [{stream,
> "./rebar"}])' \
> -s init stop
> chmod +x ./rebar
> REBAR=$(shell (type rebar 2>/dev/null || echo ./rebar) | tail -1 | awk
> '{ print $$NF }')
>
>
> It could be used to download anything, not just REBAR.
>
> - Greg
>
>
> On 16/08/2013 15:34, Lo?c Hoguin wrote:
>> On 08/16/2013 10:39 AM, Benoit Chesneau wrote:
>>> The big problem with erlang.mk <http://erlang.mk> is requiring to have
>>> gmake and more importantly wget installed imo.
>>
>> wget is only used for fetching the package index file. I'm sure if it
>> doesn't work somewhere it'll be patched eventually.
>>
>>> Which makes it quite annoying to distribute on systems that have none of
>>> them. It would be interrestin to have the support for curl for example.
>>> Also what are the makefile extensions that you really need to require
>>> gmake?
>>
>> No idea. Patches are welcome for compatibility with different OS/build
>> tools (as long as it's not "rewrite the whole file" of course, then
>> you're better off just using gmake).
>>
>>> - benoit
>>>
>>>
>>> On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu
>>> <mailto:essen at ninenines.eu>> wrote:
>>>
>>>     Hello friendly people,
>>>
>>>     I would like to make an official announcement of erlang.mk
>>> <http://erlang.mk> now that all the features I wanted are in.
>>>
>>>     erlang.mk <http://erlang.mk> is a rebar replacement. It was
>>>     initially created for allowing a faster development process than
>>>     rebar and for better compatibility with Linux build tools. It should
>>>     work on Linux and OSX with GNU Make installed.
>>>
>>>     Projects using erlang.mk <http://erlang.mk> are still compatible
>>>     with rebar. Dependencies fetched by rebar are stored in the same
>>>     deps/ directory, and projects using erlang.mk <http://erlang.mk> can
>>>     still be used as rebar dependencies, with or without a rebar.config
>>>     file.
>>>
>>>     erlang.mk <http://erlang.mk> also features a simple package index.
>>>     Try `make pkg-list` to list all packages currently available. All
>>>     the packages listed are compatible with erlang.mk <http://erlang.mk>
>>>     with no tweaking required.
>>>
>>>     Makefiles written with erlang.mk <http://erlang.mk> are *VERY*
>>>     simple, here are two examples:
>>>
>>>       * https://github.com/extend/__farwest/blob/master/Makefile
>>> <https://github.com/extend/farwest/blob/master/Makefile>
>>>       * https://github.com/extend/__cowboy/blob/master/Makefile
>>> <https://github.com/extend/cowboy/blob/master/Makefile>
>>>
>>>     I wrote about erlang.mk <http://erlang.mk> and relx recently on the
>>>     Nine Nines blog. erlang.mk <http://erlang.mk> is the perfect
>>>     companion to relx.
>>>
>>>       * http://ninenines.eu/articles/__erlang.mk-and-relx
>>> <http://ninenines.eu/articles/erlang.mk-and-relx>
>>>
>>>     Here are examples of projects that are using and compatible with
>>>     erlang.mk <http://erlang.mk>:
>>>
>>>       * https://github.com/jlouis/__etorrent
>>> <https://github.com/jlouis/etorrent>
>>>       * https://github.com/extend/__cowboy
>>> <https://github.com/extend/cowboy>
>>>       * https://github.com/extend/__farwest
>>> <https://github.com/extend/farwest>
>>>
>>>     You can find erlang.mk <http://erlang.mk> at the following URL:
>>>
>>>       * https://github.com/extend/__erlang.mk
>>> <https://github.com/extend/erlang.mk>
>>>
>>>     Contributions to the package index are of course welcome! The only
>>>     requirement is that the package is to be compatible with erlang.mk
>>> <http://erlang.mk> itself. Just send a PR to the erlang.mk
>>> <http://erlang.mk> project updating the packages.v1.txt!
>>>
>>>     Enjoy!
>>>
>>>     --
>>>     Lo?c Hoguin
>>>     Erlang Cowboy
>>>     Nine Nines
>>> http://ninenines.eu
>>>     _________________________________________________
>>>     erlang-questions mailing list
>>> erlang-questions at erlang.org <mailto:erlang-questions at erlang.org>
>>> http://erlang.org/mailman/__listinfo/erlang-questions
>>> <http://erlang.org/mailman/listinfo/erlang-questions>
>>>
>>>
>>
>>
>
>
>
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend
>


-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From steve at srstrong.com  Fri Aug 16 16:44:07 2013
From: steve at srstrong.com (Steve Strong)
Date: Fri, 16 Aug 2013 16:44:07 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
Message-ID: <[email protected]>

Was guessing that was the answer - I'll give it a go...  

--  
Steve Strong
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Friday, 16 August 2013 at 16:42, Lo?c Hoguin wrote:

> Well I'm sure if you create a base Makefile (without erlang.mk) that  
> exports DEPS_DIR and then call $(MAKE) on all folders in /apps (which  
> would themselves contain Makefiles that use erlang.mk), it would work  
> just fine. You can still keep only one erlang.mk in your repos and use  
> include ../../erlang.mk instead for example.
>  
> But know that this folder structure is a rebar thing and not standard  
> (just like /deps you'll say, but that one is insanely useful regardless  
> of the project structure otherwise).
>  
> On 08/16/2013 02:27 PM, Steve Strong wrote:
> > Looks good - I like simple! Quick question, does it support multiple
> > applications, for example a project laid out as:
> >  
> > /proj
> > /deps
> > /stuff
> >  
> > /apps
> > /app1
> > /app2
> >  
> > Most of our stuff is in that form, with shared dependencies between the
> > various apps. Rebar is quite happy with that format, but I can't see
> > how to persuade erlang.mk to handle that.
> >  
> > Cheers,
> >  
> > Steve
> >  
> > --
> > Steve Strong
> > Sent with Sparrow <http://www.sparrowmailapp.com/?sig>
> >  
> > On Thursday, 15 August 2013 at 16:19, Lo?c Hoguin wrote:
> >  
> > > Hello friendly people,
> > >  
> > > I would like to make an official announcement of erlang.mk now that all
> > > the features I wanted are in.
> > >  
> > > erlang.mk is a rebar replacement. It was initially created for allowing
> > > a faster development process than rebar and for better compatibility
> > > with Linux build tools. It should work on Linux and OSX with GNU Make
> > > installed.
> > >  
> > > Projects using erlang.mk are still compatible with rebar. Dependencies
> > > fetched by rebar are stored in the same deps/ directory, and projects
> > > using erlang.mk can still be used as rebar dependencies, with or without
> > > a rebar.config file.
> > >  
> > > erlang.mk also features a simple package index. Try `make pkg-list` to
> > > list all packages currently available. All the packages listed are
> > > compatible with erlang.mk with no tweaking required.
> > >  
> > > Makefiles written with erlang.mk are *VERY* simple, here are two examples:
> > >  
> > > * https://github.com/extend/farwest/blob/master/Makefile
> > > * https://github.com/extend/cowboy/blob/master/Makefile
> > >  
> > > I wrote about erlang.mk and relx recently on the Nine Nines blog.
> > > erlang.mk is the perfect companion to relx.
> > >  
> > > * http://ninenines.eu/articles/erlang.mk-and-relx
> > >  
> > > Here are examples of projects that are using and compatible with
> > > erlang.mk:
> > >  
> > > * https://github.com/jlouis/etorrent
> > > * https://github.com/extend/cowboy
> > > * https://github.com/extend/farwest
> > >  
> > > You can find erlang.mk at the following URL:
> > >  
> > > * https://github.com/extend/erlang.mk
> > >  
> > > Contributions to the package index are of course welcome! The only
> > > requirement is that the package is to be compatible with erlang.mk
> > > itself. Just send a PR to the erlang.mk project updating the
> > > packages.v1.txt!
> > >  
> > > Enjoy!
> > >  
> > > --
> > > Lo?c Hoguin
> > > Erlang Cowboy
> > > Nine Nines
> > > http://ninenines.eu
> > > _______________________________________________
> > > erlang-questions mailing list
> > > erlang-questions at erlang.org <mailto:erlang-questions at erlang.org>
> > > http://erlang.org/mailman/listinfo/erlang-questions
> > >  
> >  
> >  
>  
>  
>  
> --  
> Lo?c Hoguin
> Erlang Cowboy
> Nine Nines
> http://ninenines.eu
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130816/1cd82d09/attachment.html>

From list1 at gjunka.com  Fri Aug 16 17:02:00 2013
From: list1 at gjunka.com (Grzegorz Junka)
Date: Fri, 16 Aug 2013 16:02:00 +0100
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
 <[email protected]> <[email protected]>
 <[email protected]>
Message-ID: <[email protected]>

But it "is only used for fetching the package index file"... :) If the 
target is up to date there is no starting of Erlang. But on the other 
hand it could be used conditionally, e.g. use wget on systems on which 
it is installed and Erlang otherwise. It's just down to creating a 
properly structured target, isn't?

On 16/08/2013 15:44, Lo?c Hoguin wrote:
> Starting Erlang takes too long. That's a big reason why erlang.mk was 
> created. :)
>
> I recall NetBSD being able to download things with a shell script only 
> (as it comes with nothing installed), this would be a more interesting 
> solution especially since we can bundle it in the erlang.mk file too.
>
> On 08/16/2013 04:42 PM, Grzegorz Junka wrote:
>> Why not use Erlang for downloading? Surely if erlang.mk is a tool for
>> Erlang then it will be very likely installed. For example this target
>> downloads Rebar:
>>
>> # Erlang Rebar downloading, see:
>> #
>> https://groups.google.com/forum/?fromgroups=#!topic/erlang-programming/U0JJ3SeUv5Y 
>>
>> rb_rebar_url=http://cloud.github.com/downloads/basho/rebar/rebar
>> ./rebar:
>> $(ERL) -noshell -s inets -s ssl \
>> -eval 'httpc:request(get, {"$(rb_rebar_url)", []}, [], [{stream,
>> "./rebar"}])' \
>> -s init stop
>> chmod +x ./rebar
>> REBAR=$(shell (type rebar 2>/dev/null || echo ./rebar) | tail -1 | awk
>> '{ print $$NF }')
>>
>>
>> It could be used to download anything, not just REBAR.
>>
>> - Greg
>>
>>
>> On 16/08/2013 15:34, Lo?c Hoguin wrote:
>>> On 08/16/2013 10:39 AM, Benoit Chesneau wrote:
>>>> The big problem with erlang.mk <http://erlang.mk> is requiring to have
>>>> gmake and more importantly wget installed imo.
>>>
>>> wget is only used for fetching the package index file. I'm sure if it
>>> doesn't work somewhere it'll be patched eventually.
>>>
>>>> Which makes it quite annoying to distribute on systems that have 
>>>> none of
>>>> them. It would be interrestin to have the support for curl for 
>>>> example.
>>>> Also what are the makefile extensions that you really need to require
>>>> gmake?
>>>
>>> No idea. Patches are welcome for compatibility with different OS/build
>>> tools (as long as it's not "rewrite the whole file" of course, then
>>> you're better off just using gmake).
>>>
>>>> - benoit
>>>>
>>>>
>>>> On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu
>>>> <mailto:essen at ninenines.eu>> wrote:
>>>>
>>>>     Hello friendly people,
>>>>
>>>>     I would like to make an official announcement of erlang.mk
>>>> <http://erlang.mk> now that all the features I wanted are in.
>>>>
>>>>     erlang.mk <http://erlang.mk> is a rebar replacement. It was
>>>>     initially created for allowing a faster development process than
>>>>     rebar and for better compatibility with Linux build tools. It 
>>>> should
>>>>     work on Linux and OSX with GNU Make installed.
>>>>
>>>>     Projects using erlang.mk <http://erlang.mk> are still compatible
>>>>     with rebar. Dependencies fetched by rebar are stored in the same
>>>>     deps/ directory, and projects using erlang.mk 
>>>> <http://erlang.mk> can
>>>>     still be used as rebar dependencies, with or without a 
>>>> rebar.config
>>>>     file.
>>>>
>>>>     erlang.mk <http://erlang.mk> also features a simple package index.
>>>>     Try `make pkg-list` to list all packages currently available. All
>>>>     the packages listed are compatible with erlang.mk 
>>>> <http://erlang.mk>
>>>>     with no tweaking required.
>>>>
>>>>     Makefiles written with erlang.mk <http://erlang.mk> are *VERY*
>>>>     simple, here are two examples:
>>>>
>>>>       * https://github.com/extend/__farwest/blob/master/Makefile
>>>> <https://github.com/extend/farwest/blob/master/Makefile>
>>>>       * https://github.com/extend/__cowboy/blob/master/Makefile
>>>> <https://github.com/extend/cowboy/blob/master/Makefile>
>>>>
>>>>     I wrote about erlang.mk <http://erlang.mk> and relx recently on 
>>>> the
>>>>     Nine Nines blog. erlang.mk <http://erlang.mk> is the perfect
>>>>     companion to relx.
>>>>
>>>>       * http://ninenines.eu/articles/__erlang.mk-and-relx
>>>> <http://ninenines.eu/articles/erlang.mk-and-relx>
>>>>
>>>>     Here are examples of projects that are using and compatible with
>>>>     erlang.mk <http://erlang.mk>:
>>>>
>>>>       * https://github.com/jlouis/__etorrent
>>>> <https://github.com/jlouis/etorrent>
>>>>       * https://github.com/extend/__cowboy
>>>> <https://github.com/extend/cowboy>
>>>>       * https://github.com/extend/__farwest
>>>> <https://github.com/extend/farwest>
>>>>
>>>>     You can find erlang.mk <http://erlang.mk> at the following URL:
>>>>
>>>>       * https://github.com/extend/__erlang.mk
>>>> <https://github.com/extend/erlang.mk>
>>>>
>>>>     Contributions to the package index are of course welcome! The only
>>>>     requirement is that the package is to be compatible with erlang.mk
>>>> <http://erlang.mk> itself. Just send a PR to the erlang.mk
>>>> <http://erlang.mk> project updating the packages.v1.txt!
>>>>
>>>>     Enjoy!
>>>>
>>>>     --
>>>>     Lo?c Hoguin
>>>>     Erlang Cowboy
>>>>     Nine Nines
>>>> http://ninenines.eu
>>>>     _________________________________________________
>>>>     erlang-questions mailing list
>>>> erlang-questions at erlang.org <mailto:erlang-questions at erlang.org>
>>>> http://erlang.org/mailman/__listinfo/erlang-questions
>>>> <http://erlang.org/mailman/listinfo/erlang-questions>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Extend mailing list
>> Extend at lists.ninenines.eu
>> http://lists.ninenines.eu:81/listinfo/extend
>>
>
>



From essen at ninenines.eu  Fri Aug 16 17:10:19 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 16 Aug 2013 17:10:19 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
 <[email protected]> <[email protected]>
 <[email protected]> <[email protected]>
Message-ID: <[email protected]>

I know, and if it makes it work where it currently doesn't I'd merge it. 
But ultimately we want to avoid starting Erlang unless strictly necessary.

On 08/16/2013 05:02 PM, Grzegorz Junka wrote:
> But it "is only used for fetching the package index file"... :) If the
> target is up to date there is no starting of Erlang. But on the other
> hand it could be used conditionally, e.g. use wget on systems on which
> it is installed and Erlang otherwise. It's just down to creating a
> properly structured target, isn't?
>
> On 16/08/2013 15:44, Lo?c Hoguin wrote:
>> Starting Erlang takes too long. That's a big reason why erlang.mk was
>> created. :)
>>
>> I recall NetBSD being able to download things with a shell script only
>> (as it comes with nothing installed), this would be a more interesting
>> solution especially since we can bundle it in the erlang.mk file too.
>>
>> On 08/16/2013 04:42 PM, Grzegorz Junka wrote:
>>> Why not use Erlang for downloading? Surely if erlang.mk is a tool for
>>> Erlang then it will be very likely installed. For example this target
>>> downloads Rebar:
>>>
>>> # Erlang Rebar downloading, see:
>>> #
>>> https://groups.google.com/forum/?fromgroups=#!topic/erlang-programming/U0JJ3SeUv5Y
>>>
>>> rb_rebar_url=http://cloud.github.com/downloads/basho/rebar/rebar
>>> ./rebar:
>>> $(ERL) -noshell -s inets -s ssl \
>>> -eval 'httpc:request(get, {"$(rb_rebar_url)", []}, [], [{stream,
>>> "./rebar"}])' \
>>> -s init stop
>>> chmod +x ./rebar
>>> REBAR=$(shell (type rebar 2>/dev/null || echo ./rebar) | tail -1 | awk
>>> '{ print $$NF }')
>>>
>>>
>>> It could be used to download anything, not just REBAR.
>>>
>>> - Greg
>>>
>>>
>>> On 16/08/2013 15:34, Lo?c Hoguin wrote:
>>>> On 08/16/2013 10:39 AM, Benoit Chesneau wrote:
>>>>> The big problem with erlang.mk <http://erlang.mk> is requiring to have
>>>>> gmake and more importantly wget installed imo.
>>>>
>>>> wget is only used for fetching the package index file. I'm sure if it
>>>> doesn't work somewhere it'll be patched eventually.
>>>>
>>>>> Which makes it quite annoying to distribute on systems that have
>>>>> none of
>>>>> them. It would be interrestin to have the support for curl for
>>>>> example.
>>>>> Also what are the makefile extensions that you really need to require
>>>>> gmake?
>>>>
>>>> No idea. Patches are welcome for compatibility with different OS/build
>>>> tools (as long as it's not "rewrite the whole file" of course, then
>>>> you're better off just using gmake).
>>>>
>>>>> - benoit
>>>>>
>>>>>
>>>>> On Thu, Aug 15, 2013 at 4:19 PM, Lo?c Hoguin <essen at ninenines.eu
>>>>> <mailto:essen at ninenines.eu>> wrote:
>>>>>
>>>>>     Hello friendly people,
>>>>>
>>>>>     I would like to make an official announcement of erlang.mk
>>>>> <http://erlang.mk> now that all the features I wanted are in.
>>>>>
>>>>>     erlang.mk <http://erlang.mk> is a rebar replacement. It was
>>>>>     initially created for allowing a faster development process than
>>>>>     rebar and for better compatibility with Linux build tools. It
>>>>> should
>>>>>     work on Linux and OSX with GNU Make installed.
>>>>>
>>>>>     Projects using erlang.mk <http://erlang.mk> are still compatible
>>>>>     with rebar. Dependencies fetched by rebar are stored in the same
>>>>>     deps/ directory, and projects using erlang.mk
>>>>> <http://erlang.mk> can
>>>>>     still be used as rebar dependencies, with or without a
>>>>> rebar.config
>>>>>     file.
>>>>>
>>>>>     erlang.mk <http://erlang.mk> also features a simple package index.
>>>>>     Try `make pkg-list` to list all packages currently available. All
>>>>>     the packages listed are compatible with erlang.mk
>>>>> <http://erlang.mk>
>>>>>     with no tweaking required.
>>>>>
>>>>>     Makefiles written with erlang.mk <http://erlang.mk> are *VERY*
>>>>>     simple, here are two examples:
>>>>>
>>>>>       * https://github.com/extend/__farwest/blob/master/Makefile
>>>>> <https://github.com/extend/farwest/blob/master/Makefile>
>>>>>       * https://github.com/extend/__cowboy/blob/master/Makefile
>>>>> <https://github.com/extend/cowboy/blob/master/Makefile>
>>>>>
>>>>>     I wrote about erlang.mk <http://erlang.mk> and relx recently on
>>>>> the
>>>>>     Nine Nines blog. erlang.mk <http://erlang.mk> is the perfect
>>>>>     companion to relx.
>>>>>
>>>>>       * http://ninenines.eu/articles/__erlang.mk-and-relx
>>>>> <http://ninenines.eu/articles/erlang.mk-and-relx>
>>>>>
>>>>>     Here are examples of projects that are using and compatible with
>>>>>     erlang.mk <http://erlang.mk>:
>>>>>
>>>>>       * https://github.com/jlouis/__etorrent
>>>>> <https://github.com/jlouis/etorrent>
>>>>>       * https://github.com/extend/__cowboy
>>>>> <https://github.com/extend/cowboy>
>>>>>       * https://github.com/extend/__farwest
>>>>> <https://github.com/extend/farwest>
>>>>>
>>>>>     You can find erlang.mk <http://erlang.mk> at the following URL:
>>>>>
>>>>>       * https://github.com/extend/__erlang.mk
>>>>> <https://github.com/extend/erlang.mk>
>>>>>
>>>>>     Contributions to the package index are of course welcome! The only
>>>>>     requirement is that the package is to be compatible with erlang.mk
>>>>> <http://erlang.mk> itself. Just send a PR to the erlang.mk
>>>>> <http://erlang.mk> project updating the packages.v1.txt!
>>>>>
>>>>>     Enjoy!
>>>>>
>>>>>     --
>>>>>     Lo?c Hoguin
>>>>>     Erlang Cowboy
>>>>>     Nine Nines
>>>>> http://ninenines.eu
>>>>>     _________________________________________________
>>>>>     erlang-questions mailing list
>>>>> erlang-questions at erlang.org <mailto:erlang-questions at erlang.org>
>>>>> http://erlang.org/mailman/__listinfo/erlang-questions
>>>>> <http://erlang.org/mailman/listinfo/erlang-questions>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Extend mailing list
>>> Extend at lists.ninenines.eu
>>> http://lists.ninenines.eu:81/listinfo/extend
>>>
>>
>>
>
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend


-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From wbin00 at gmail.com  Fri Aug 16 17:40:22 2013
From: wbin00 at gmail.com (Bin Wang)
Date: Fri, 16 Aug 2013 23:40:22 +0800
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
 <[email protected]> <[email protected]>
 <[email protected]> <[email protected]>
 <[email protected]>
Message-ID: <CAD_32VXteDmb218jRdJcabGSrc7zUvuTpxov+Os=D07Ce5pSZQ@mail.gmail.com>

Will it support protobuf(https://github.com/basho/erlang_protobuffs),
I cannot compile *.proto file from src/ with erlang.mk.


From essen at ninenines.eu  Fri Aug 16 17:55:30 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Fri, 16 Aug 2013 17:55:30 +0200
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <CAD_32VXteDmb218jRdJcabGSrc7zUvuTpxov+Os=D07Ce5pSZQ@mail.gmail.com>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
 <[email protected]> <[email protected]>
 <[email protected]> <[email protected]>
 <[email protected]>
 <CAD_32VXteDmb218jRdJcabGSrc7zUvuTpxov+Os=D07Ce5pSZQ@mail.gmail.com>
Message-ID: <[email protected]>

On 08/16/2013 05:40 PM, Bin Wang wrote:
> Will it support protobuf(https://github.com/basho/erlang_protobuffs),
> I cannot compile *.proto file from src/ with erlang.mk.

That's a good question. I probably would merge such a patch right now, 
but if it ends up being too many different compilers we'll probably need 
a better solution (something like having you include both erlang.mk and 
protobuffs.mk to enable it?).

I don't use protobuffs myself so don't count on me though.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From jeremy at quarkgames.com  Fri Aug 16 18:29:36 2013
From: jeremy at quarkgames.com (Jeremy Ong)
Date: Fri, 16 Aug 2013 09:29:36 -0700
Subject: [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
In-Reply-To: <[email protected]>
References: <[email protected]>
 <CAJNb-9qrsb=pdXziwNiOa5EF12e3QieMyj0N6OdzGY=-0CCz=A@mail.gmail.com>
 <[email protected]> <[email protected]>
 <[email protected]> <[email protected]>
 <[email protected]>
 <CAD_32VXteDmb218jRdJcabGSrc7zUvuTpxov+Os=D07Ce5pSZQ@mail.gmail.com>
 <[email protected]>
Message-ID: <CAKD1GY6F-+Zo7jpSM6rJrZkAypwaazh=ZBg+Q0_YY5MyXeK2XQ@mail.gmail.com>

I'd prefer it if there were more generalized hooks for files of
different names rather than hardcoding usage of a particular library.
In the case of protobuffers, some people use piqi, others use basho's
library, and still others use their own library.

On Fri, Aug 16, 2013 at 8:55 AM, Lo?c Hoguin <essen at ninenines.eu> wrote:
> On 08/16/2013 05:40 PM, Bin Wang wrote:
>>
>> Will it support protobuf(https://github.com/basho/erlang_protobuffs),
>> I cannot compile *.proto file from src/ with erlang.mk.
>
>
> That's a good question. I probably would merge such a patch right now, but
> if it ends up being too many different compilers we'll probably need a
> better solution (something like having you include both erlang.mk and
> protobuffs.mk to enable it?).
>
> I don't use protobuffs myself so don't count on me though.
>
>
> --
> Lo?c Hoguin
> Erlang Cowboy
> Nine Nines
> http://ninenines.eu
> _______________________________________________
> Extend mailing list
> Extend at lists.ninenines.eu
> http://lists.ninenines.eu:81/listinfo/extend


From wbin00 at gmail.com  Sat Aug 17 10:00:04 2013
From: wbin00 at gmail.com (Bin Wang)
Date: Sat, 17 Aug 2013 16:00:04 +0800
Subject: [99s-extend] How to broadcaset with ranch?
Message-ID: <CAD_32VWVNb_-vHChdC2S4CcFeJ29v5n3w6B0LNS5=RqWQxKaAQ@mail.gmail.com>

Hi,

I'm new to ranch. In my application, I need to send some message to
all connections. So I'd like to know can I get all connections from
ranch, so I could use Transport:send to send them, or I must manage
all the created connections by myself? Or is there any other better
way?

Thanks.

Bin Wang


From essen at ninenines.eu  Sat Aug 17 10:10:41 2013
From: essen at ninenines.eu (=?ISO-8859-1?Q?Lo=EFc_Hoguin?=)
Date: Sat, 17 Aug 2013 10:10:41 +0200
Subject: [99s-extend] How to broadcaset with ranch?
In-Reply-To: <CAD_32VWVNb_-vHChdC2S4CcFeJ29v5n3w6B0LNS5=RqWQxKaAQ@mail.gmail.com>
References: <CAD_32VWVNb_-vHChdC2S4CcFeJ29v5n3w6B0LNS5=RqWQxKaAQ@mail.gmail.com>
Message-ID: <[email protected]>

On 08/17/2013 10:00 AM, Bin Wang wrote:
> Hi,
>
> I'm new to ranch. In my application, I need to send some message to
> all connections. So I'd like to know can I get all connections from
> ranch, so I could use Transport:send to send them, or I must manage
> all the created connections by myself? Or is there any other better
> way?

The best way to do that is on your end, using gproc properties. When the 
connection is accepted, register the process with the property and use 
the property to send messages to all processes. You don't need to 
unregister when the connection ends, gproc does that automatically.

The hackish way to do that would be to call supervisor:which_children on 
the ranch_conns_sup supervisor of your listener, but that will slow down 
the accepting of new connections, so don't do this if you need high 
accept rates.

-- 
Lo?c Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu


From seancribbs at gmail.com  Wed Aug 21 05:18:19 2013
From: seancribbs at gmail.com (Sean Cribbs)
Date: Tue, 20 Aug 2013 22:18:19 -0500
Subject: [99s-extend] [erlang-questions]  How to broadcaset with ranch?
In-Reply-To: <[email protected]>
References: <CAD_32VWVNb_-vHChdC2S4CcFeJ29v5n3w6B0LNS5=RqWQxKaAQ@mail.gmail.com>
 <[email protected]>
Message-ID: <CAPGJuCaYJnOn-Hq_GgQZV2pxmaUwCxbS372dapbnQiOZ8vWC=w@mail.gmail.com>

This is exactly the sort of thing gen_event is for. I would make each
server process register a handler at startup using
gen_event:add_sup_handler() and then have the handle_event callback simply
relay the event to the server processes. Yes, gproc can do this, but why
incur its extra features and overhead?


On Sat, Aug 17, 2013 at 3:10 AM, Lo?c Hoguin <essen at ninenines.eu> wrote:

> On 08/17/2013 10:00 AM, Bin Wang wrote:
>
>> Hi,
>>
>> I'm new to ranch. In my application, I need to send some message to
>> all connections. So I'd like to know can I get all connections from
>> ranch, so I could use Transport:send to send them, or I must manage
>> all the created connections by myself? Or is there any other better
>> way?
>>
>
> The best way to do that is on your end, using gproc properties. When the
> connection is accepted, register the process with the property and use the
> property to send messages to all processes. You don't need to unregister
> when the connection ends, gproc does that automatically.
>
> The hackish way to do that would be to call supervisor:which_children on
> the ranch_conns_sup supervisor of your listener, but that will slow down
> the accepting of new connections, so don't do this if you need high accept
> rates.
>
> --
> Lo?c Hoguin
> Erlang Cowboy
> Nine Nines
> http://ninenines.eu
>
> ______________________________**_________________
> erlang-questions mailing list
> erlang-questions at erlang.org
> http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130820/b203ebe2/attachment.html>