Re: [fossil-users] Automating fossil source builds?

2014-03-23 Thread Baruch Burstein
On Sun, Mar 23, 2014 at 5:49 AM, Jon wrote: > > but I haven't yet found a way to create a URL to download a tarball > for a specific release tag of fossil. > > Ideally, I'd like to type `./build_fossil.ps1 1.28` and have it > download the tarball from > > http://www.fossil-scm.org/fossil/info/3d4

Re: [fossil-users] about fossil ignore and clean

2014-03-23 Thread Jan Nijtmans
2014-03-22 18:47 GMT+01:00 Benedikt Ahrens : > I am confused by fossil ignore and clean behaviour. > I have a lot of files, recognizable by extension, that I would like to > ignore when calling "fossil status" (1), but delete when calling "fossil > clean" (2). Well, "fossil clean" is not supposed

Re: [fossil-users] GitHub-style template

2014-03-23 Thread Stephan Beal
On Sun, Mar 23, 2014 at 1:17 AM, wrote: > To get more out of this it might ultimatively make sense to introduce > a "/script" > page (like /header /footer and /style) for the fossil cgi/server. > Otherwise it could > get difficult (and traffic-wastey) to maintain more complex > client-side script

Re: [fossil-users] Automating fossil source builds?

2014-03-23 Thread Stephan Beal
On Sun, Mar 23, 2014 at 8:21 AM, Baruch Burstein wrote: > Replace the uuid with the tag, e.g.: > > > http://www.fossil-scm.org/fossil/tarball/Fossil_1.28.tar.gz?uuid=version-1.28 > > You "might" also be interested in the libfossil CLI tools, one of which can generate ZIP files: [stephan@host:~/

[fossil-users] Is it possible to keep original file dates where reverting / updating?

2014-03-23 Thread tonyp
Hi all, Like the subject says: Is it possible to restore the original file dates whenever reverting / updating to a given version? This is important for MAKE files to not consider a file updated and try to rebuild. TIA___ fossil-users mailing list fo

Re: [fossil-users] Is it possible to keep original file dates where reverting / updating?

2014-03-23 Thread Stephan Beal
On Sun, Mar 23, 2014 at 11:48 AM, wrote: > Like the subject says: Is it possible to restore the original file > dates whenever reverting / updating to a given version? > Fossil doesn't actually remember a file's real modification time. Instead it computes it based on the time of the checkin th

Re: [fossil-users] Is it possible to keep original file dates where reverting / updating?

2014-03-23 Thread tonyp
On the other hand, when updating to a previous version, you’re actually interested in getting a snapshot of how things were at that time, and if every restored file is given a ‘now’ timestamp, using MAKE is the equivalent of always using the –B option, which is not likely what you wanted to do.

Re: [fossil-users] nginx fronting fossil best practices?

2014-03-23 Thread Joseph Prostko
On Sat, Mar 22, 2014 at 6:23 PM, Jon wrote: > With a fresh build of 684eb478e my SCGI setup with nginx 1.5.12 on > Ubuntu Server 13.10 64bit appears to be working. > > Fossil is started via upstart using: > > exec /usr/local/sbin/fossil server --localhost --scgi /srv/fossils/partner > > Nice cat

Re: [fossil-users] Is it possible to keep original file dates where reverting / updating?

2014-03-23 Thread Stephan Beal
On Sun, Mar 23, 2014 at 1:48 PM, wrote: > Anyway, wouldn't it nice to have an option to keep the original > timestamp? Perhaps, with a default 'now' timestamp for REVERT operations > and 'original' timestamp for UPDATE operations (at least when no specific > file set is given, and the whole tr

Re: [fossil-users] nginx fronting fossil best practices?

2014-03-23 Thread Jon
> Also, I'm going to experiment with Upstart a bit now due to this > thread. I admit I've always been an init script kind of guy, but it > doesn't hurt to try something new when it is supported on your > platform. re: the future of upstart on ubuntu http://www.markshuttleworth.com/archives/1316

Re: [fossil-users] nginx fronting fossil best practices?

2014-03-23 Thread Joseph Prostko
On Sun, Mar 23, 2014 at 10:03 AM, Jon wrote: >> Also, I'm going to experiment with Upstart a bit now due to this >> thread. I admit I've always been an init script kind of guy, but it >> doesn't hurt to try something new when it is supported on your >> platform. > > re: the future of upstart on

Re: [fossil-users] Automating fossil source builds?

2014-03-23 Thread Jon
> > Are there other URL schemes I haven't yet discovered that alias to >> source tarballs for specific tags? > > > Replace the uuid with the tag, e.g.: > > > http://www.fossil-scm.org/fossil/tarball/Fossil_1.28.tar.gz?uuid=version-1.28 > > > Nice. I see `uuid` controls things so I can also do this

Re: [fossil-users] Automating fossil source builds?

2014-03-23 Thread Stephan Beal
On Sun, Mar 23, 2014 at 6:05 PM, Jon wrote: > 1) Should the comments for `src/tar.c:tarball_page:L577` be updated to > include query param doco similar to `src/browse.c:page_tree:L403`? The > current the `URL: /tarball/RID.tar.gz` comment doesn't capture the current > URL flexibility. > i can't

Re: [fossil-users] Automating fossil source builds?

2014-03-23 Thread Stephan Beal
On Sun, Mar 23, 2014 at 6:09 PM, Stephan Beal wrote: > i can't answer that one off hand, but will look at it after my pizza's > done. But... > Pizza's still processing, but here you go; http://fossil-scm.org/index.html/info/7ba06f150c -- - stephan beal http://wanderinghorse.net/home/steph

Re: [fossil-users] Automating fossil source builds?

2014-03-23 Thread Jon
> Pizza's still processing, but here you go; > > http://fossil-scm.org/index.html/info/7ba06f150c :) same for `src/zip.c:baseline_zip_page` please. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/