Re: [fossil-users] Using fossil with Golang (go get)

2018-06-18 Thread Zack Scholl
Hi Mark, The meta tag will not work for importing Go code. The first term needs to match the import path, e.g. "X" in the `go get X` command. And "http(s)://" is not allowed in the import path for `go get`. Is there a fossil variable similar to "$baseurl" for the base URL without the

Re: [fossil-users] A fossil library

2018-06-18 Thread Alek Paunov
Sorry: s/collection, UDFs/collection of UDFs/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] A fossil library

2018-06-18 Thread Alek Paunov
But those intricate algorithms for deduplication, hash chaining, and merging, those would come in handy across the board. A bit about drift: it's a natural outcome of parallel codebases, even with something like a common standard. Without that, it's guaranteed, unless one of the forks doesn't

Re: [fossil-users] A fossil library

2018-06-18 Thread Sam Putman
On Mon, Jun 18, 2018 at 4:54 AM, Stephan Beal wrote: > On Sun, Jun 17, 2018 at 11:11 PM Sam Putman wrote: > >> On Sun, Jun 17, 2018 at 6:39 AM, David Mason wrote: >> >>> Just had a quick thought that might make the conversion to library much >>> easier. >>> >>> If you have a relatively small

Re: [fossil-users] A fossil library

2018-06-18 Thread Sam Putman
On Mon, Jun 18, 2018 at 4:43 AM, Stephan Beal wrote: > On Sun, Jun 17, 2018 at 11:07 PM Sam Putman wrote: > >> About those objects... >> >> What your docs call fossil(1) is written in plain C. Or rather C, Tcl, >> SQL and TH1, if you prefer. >> In any case, not C++. >> > > liubfossil is 100%

Re: [fossil-users] Using fossil with Golang (go get)

2018-06-18 Thread Mark Janssen (fossil)
On 2018-06-17 14:57, Zack Scholl wrote: All you need to do is update your "Header" skin (Admin -> Skins) to include a special meta tag that `go get` will fetch to interpret your fossil as a Go library/program. For example, if you have a fossil hosted at https://yourdomain.com/hello-world then

Re: [fossil-users] Perception of Fossil

2018-06-18 Thread Eduard
A lot of people allow wiki append by anonymous on their repos. You may choose not to. Maybe PR should get its own capability so you may restrict to authenticated or particular users (or not). On June 18, 2018 8:39:59 AM EDT, Karel Gardas wrote: >On Mon, 18 Jun 2018 00:01:33 +0300 >John Found

Re: [fossil-users] Perception of Fossil

2018-06-18 Thread Karel Gardas
On Mon, 18 Jun 2018 00:01:33 +0300 John Found wrote: > > Please no, this would be real security nightmare. Anyone can attack any > > fossil public repo then by simple DoS. Do not ever allow anonymous to play > > with your pristine repository! If anon needs to "push" something, then > > he/she

Re: [fossil-users] A fossil library

2018-06-18 Thread Stephan Beal
On Sun, Jun 17, 2018 at 11:11 PM Sam Putman wrote: > On Sun, Jun 17, 2018 at 6:39 AM, David Mason wrote: > >> Just had a quick thought that might make the conversion to library much >> easier. >> >> If you have a relatively small API interface, each of the API functions >> could do a setjmp

Re: [fossil-users] A fossil library

2018-06-18 Thread Stephan Beal
On Sun, Jun 17, 2018 at 11:07 PM Sam Putman wrote: > About those objects... > > What your docs call fossil(1) is written in plain C. Or rather C, Tcl, SQL > and TH1, if you prefer. > In any case, not C++. > liubfossil is 100% C89 except that it requires "long long" because sqlite3 requires it.