On 11/02/2016 12:33 PM, Tony Papadimitriou wrote:
> c:\fossil\win\winhttp.h(24) : error C2004: expected 'defined(id)'
> c:\fossil\win\winhttp.h(24) : fatal error C1012: unmatched parenthesis :
> missing ')'
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> Studio 12.0\VC\BIN\
On 11/02/2016 06:33 AM, Martin Gagnon wrote:
> If you want to use openssl from your distro, you need to install the
> development package of openssl.
>
> I think it's "openssl-devel" on CentOS.
>
> I'm not very familiar with CentOS but if you do:
>
> $ yum install openssl-devel
>
> the config
On 11/02/2016 05:45 AM, Jan Nijtmans wrote:
> 2016-11-02 7:29 GMT+01:00 Joe Mistachkin:
>> I think using OpenSSL 1.1 will only work on the "openssl-1.1.0" branch.
>
> For Windows, that's true. For other platforms, openssl-1.1 works fine
> in Fossil 1.36 or later. The reason is that dll names were
On 11/02/2016 02:29 AM, Joe Mistachkin wrote:
> I think using OpenSSL 1.1 will only work on the "openssl-1.1.0" branch.
>
> Here are the commands I generally use to get things all working in the
> source tree:
>
> cd compat/zlib && ./configure && make
> cd ..
> wget -4 https://www.openssl.org/sou
When compiling on CentOS-7, 'configure --with-openssl=auto' doesn't find
what is needed. How can OpenSSL or LibreSSL source be placed in the
'fossil/compat' directory such that 'configure --with-openssl=tree' will
work? I've tried both:
tar xzf openssl-1.1.0b.tar.gz -C ~/build/fossil/compat/
cd ~/
On 10/31/2016 06:24 AM, Richard Hipp wrote:
> On 10/31/16, Artur Shepilko wrote:
>> I would've
>> gladly fixed it myself, but have not mailed yet the Contributor Agreement..
>> (I have signed it though :)
>>
>
> Please do mail in your CLA. And maybe also post a patch to this mailing list.
>
W
On 10/26/2016 05:37 PM, Karel Gardas wrote:
> I'm now able to import OpenBSD
> source tree from OpenBSD src git mirror to fossil.
This might be a silly question since I am terribly uniformed of the
issues but could you have imported the OpenBSD source directly from
their CVS repository?
http://ww
On 10/24/2016 04:59 PM, Warren Young wrote:
> On Oct 24, 2016, at 2:32 PM, Adam Jensen wrote:
>> Isn't it a file (version) management system based on an embedded database?
>
> Under casual inspection, Fossil presents itself to the user that way, but if
> you dig into th
On 10/24/2016 03:07 PM, Warren Young wrote:
> I don’t know that Fossil is all that close to any other software
> system you’ve likely used before.
Isn't it a file (version) management system based on an embedded database?
On 10/23/2016 06:13 PM, Scott Doctor wrote:
> My current workflow uses a d
On 10/24/2016 02:17 PM, Richard Hipp wrote:
> Yes, except that Andy broken the build while we were in the quiet
> period leading up to the 1.36 release
Nice job, Andy
http://big.assets.huffingtonpost.com/tumblr_nqxexloObr1rubttio1_400.gif
___
fossil-u
On 10/24/2016 01:33 PM, Scott Doctor wrote:
[snip]
> I think the documentation should group the most commonly used commands
> from the master list. Maybe make several groups presented in most-used
> to rarely-used groupings. A primer should avoid permuting the possible
> operations until later (it
On 10/23/2016 06:13 PM, Scott Doctor wrote:
>
> On 10/23/2016 13:59, Artur Shepilko wrote:
>> It's not clear what type of project the OP is trying to setup, whether
>> it's a programming-related project, or general document-repo type.
>>
> I am doing research where we may do a dozen iterations a d
Concerning the actual contents of a documentation system, I suppose a
framework might be composed of templates for:
1. Command syntax quick reference - fossil help ?cmd?
2. Command detailed reference
3. Cookbook-like containing "recipes" for various scenarios
4. Overview
4a. System introduction
On 10/11/2016 08:31 PM, Ron W wrote:
> Sounds like something Google Docs does or could easily do (at least in
> Google docs for Business).
I'm not familiar with any recent incarnation of Google Docs. A quick
glance at my white board and I see four loops of interaction with the
documentation system
On 10/11/2016 03:39 PM, jungle Boogie wrote:
> I would call that a wiki, not only inside fossil-scm but in general.
I am inclined to think that a wiki probably isn't sufficient for many
projects. What I am casually proposing (just brainstorming, really) is a
documentation framework that supports s
Here's an idea that might be a little complicated to describe:
Every time a [potential] user interacts with the documentation there is
human attention, intelligence, and effort that is engaging the system.
What if the system were designed to harness some of that?
If a documentation framework incl
On 10/10/2016 01:49 PM, Richie Adler wrote:
> *Nobody* has the
> excuse that version control is costly or complicated anymore.
As I sit here trying to untangle the [Permuted Index][1] of documents, I
realize there is most definitely a cost; I am paying it now. And,
unfortunately, none of this atte
On 10/10/2016 10:02 AM, Adam Jensen wrote:
> Along the same lines, it might be awesome if there were a dhr@
s/dhr/drh-crew
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fos
On 10/10/2016 08:12 AM, Adam Jensen wrote:
> On 10/09/2016 09:31 PM, Richard Hipp wrote:
>> https://news.ycombinator.com/item?id=12673229
>
> These are probably significant decision points for a lot of people:
>
> "My intent is to continue personally supporting and m
On 10/09/2016 09:31 PM, Richard Hipp wrote:
> https://news.ycombinator.com/item?id=12673229
These are probably significant decision points for a lot of people:
"My intent is to continue personally supporting and maintaining Fossil
for at least three more decades."
https://youtu.be/Jib2AmRb_rk?t=
Given the vast technical resources that are available (and becoming
available), documentation creation and refinement seems like a keystone
technology. Dedicating weeks or months to evaluate a piece of technology
is increasingly becoming a less viable practice. It's something that
I've thought abou
On 10/08/2016 06:40 PM, Richard Hipp wrote:
> I do not know how to make the documentation any clearer.
It's something I've been thinking about [in general] for a while and I
just used this opportunity to inject the idea into the Fossil community.
This seems like the sweet spot with TCL on one side
On 10/08/2016 02:23 PM, Zeev Pekar wrote:
> Ok. I understood the consequences - I'll operate on a copy of a repo. So
> could you, please, provide the two examples anyway?
*snide humor alert*
The reluctance of some programmer communities to provide examples has
always surprised me. I think documen
Is TH1 required to run Tcl scripts?
Are there any examples of Tcl use-with/extensions-of Fossil?
I am having some trouble sorting out the documentation and determining
the build options that would enable exploration.
The build page[1] might be out of date/sync with the build options.
[1]: http
On 09/16/2016 06:54 PM, Nickolas Lloyd wrote:
> see my email on fossil-dev for reference
"The current archive is only available to the list members."[1]
[1]: http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-dev
Is that unusual for an open-source project? (Not that I am opposed t
On 09/12/2016 02:55 PM, Ross Berteig wrote:
> Clumsy, perhaps, but it would work today.
Thanks. The `fossil fusefs ...` performance kills the possibility of
using Fossil as a large binary file repository manager.
I find myself casually reading "Practical File System Design"[1] and the
HDF5 Specs[
On 09/11/2016 05:30 PM, Stephan Beal wrote:
> And i would argue against it as falling well out of scope for an SCM ;)
I'm okay with that.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/lis
On 09/11/2016 06:38 PM, Scott Robison wrote:
> Of course, adding differentiation and specialization increases
> complexity, so it can be a tricky balancing act.
We, as a species, have already gone down that rabbit hole.
___
fossil-users mailing list
fos
On 09/11/2016 04:42 PM, Scott Robison wrote:
> I may not be understanding you, but from my point of view, it already
> does what you want by supporting versioned files that you simply never
> change. For example, you could have a repo that has a structure along
> the lines of:
>
> /root/static-dat
On 09/11/2016 01:54 PM, Stephan Beal wrote:
> On Sep 11, 2016 18:18, "Adam Jensen" <mailto:han...@riseup.net>> wrote:
[snip]
>> '''
>> 5.4 Unversioned File Sync
>>
>> "Unversioned files" are files held in the repository wh
On 09/11/2016 05:41 AM, Stephan Beal wrote:
> On Sep 10, 2016 19:31, "Adam Jensen" <mailto:han...@riseup.net>> wrote:
>> 1. What is the largest size of any single file that can be checked into
>> a repository?
>
> effectively limited by system memory: fos
fossil version used for this test:
checkout: 871f978d9b080403b73408858a63353ddaaf85a3 2016-09-10 20:01:51 UTC
I did some tests with fusefs[1] today.
[1]: https://www.fossil-scm.org/fossil/help?cmd=fusefs
Some issues:
1. Unversioned files (e.g., fossil unversioned add 128MB-file.test)
don't show
On 09/10/2016 01:31 PM, Adam Jensen wrote:
[snip]
> 1. What is the largest size of any single file that can be checked into
> a repository?
[snip]
I did some tests with Fossil trunk, checked-out and compiled today.
too big: dd if=/dev/urandom of=1GB-file.test bs=64M count=16
too big: dd i
On 09/09/2016 10:20 PM, Richard Hipp wrote:
> On 9/9/16, Adam Jensen wrote:
>> On 09/05/2016 05:23 PM, Adam Jensen wrote:
>>> B. I suspect the storage requirement will be twice (2x) the data size -
>>> the data is stored once in the Fossil database and another copy
On 09/05/2016 05:23 PM, Adam Jensen wrote:
> B. I suspect the storage requirement will be twice (2x) the data size -
> the data is stored once in the Fossil database and another copy would
> exist in the file-system [as a check-out].
I wonder if it would be nifty if Fossil could export
On 09/05/2016 03:00 AM, Gour wrote:
[snip]
> Now, when I got rid of ownCloud and replaced it with something lighter
> to sync my calendars/contacts with the phone, I plan to manually cp-ing
> media files to my computer and considering to put all those
> photos/videos as unversioned files in a Fossi
On 09/02/2016 01:05 PM, Richard Hipp wrote:
[snip]
> I have the request to optionally include unversioned files in the
> check-out. But that is not yet implemented.
Super cool. Not to hijack this thread but a next step might be to track,
manage, and share items in the file-system that are not act
On 08/30/2016 02:31 PM, Richard Hipp wrote:
> A new feature of Fossil (currently unreleased and only available to
> people who are willing to recompile the code on trunk) is "unversioned
> files".
>
> https://www.fossil-scm.org/fossil/doc/trunk/www/unvers.wiki
Hey, cool. This seems like a mov
On 08/02/2016 02:17 PM, Joe Mistachkin wrote:
>
> Adam Jensen wrote:
>>
>> So neither the TH1 or the embedded Tcl engine have typical shell-like
>> access the OS?
>>
>
> If the Tcl integration features of Fossil are enabled, the Tcl interpreter
> will
On 08/02/2016 10:57 AM, Ron W wrote:
> On Tue, Aug 2, 2016 at 12:26 AM, Adam Jensen <mailto:han...@riseup.net>> wrote:
>
>
> Subversion has "Repository Hooks" (a program triggered by some
> repository event); Fossil might have had a similar
On 08/02/2016 05:00 AM, Richard Hipp wrote:
> On 8/2/16, John Found wrote:
>> I have to move my web site on a server that supports only FastCGI interface.
>> Is there an easy way to host fossil repositories on it?
>
> Fossil only support CGI and SCGI. What web server are you running
> that has o
On 08/01/2016 11:01 PM, Ron W wrote:
> On Mon, Aug 1, 2016 at 8:22 PM, Adam Jensen Is there a way to run these scripts automatically after each checkout?
>
>
> My team and I do this as part of the build procedure. Basically, we
> treat those as part of the "product"
On 08/01/2016 10:25 PM, Steve Stefanovich wrote:
> At the end, you didn't add the empty-dirs file. You need to do 'fossil add *
> --dotfiles' or explicitly do 'f add .fossil-settings/empty-dirs', then
> commit. Then a subsequent checkout will create the directories.
>
Thanks. Following John's d
On 08/01/2016 07:40 PM, bch wrote:
> There has been lots of discussion about this over the years
> (https://www.google.ca/search?q=fossil-users+empty+directory).
>
> I personally handle this (and other metadata things like user:group
> ownership or permissions (though we now handle --x (executable
On 08/01/2016 07:25 PM, Steve Stefanovich wrote:
>
> Create a .fossil-settings directory in the root of your checkout, and in it
> add empty-dirs file with relative paths to where you want empty directories
> created, fossil add/commit.
>
Is there documentation for that approach? I can't seem
Hi,
I haven't before used fossil to manage a project. Is there a way to
commit empty directories to the repository so the project's directory
structure can be preserved and reconstructed?
Actually, some of the directories aren't empty but rather their contents
are ignored:
fsl add --ignore '*.db
On 07/27/2016 10:37 AM, Ron W wrote:
> On Sun, Jul 24, 2016 at 10:58 PM, Adam Jensen <mailto:han...@riseup.net>> wrote:
>
>
> [The Session Extension](http://www.sqlite.org/sessionintro.html) pointed
> out by Eduardo seems to have a lot of potential.
>
&
On 07/25/2016 04:38 AM, Carlo Miron wrote:
> See also [rqlite] (https://github.com/rqlite/rqlite).
>
Hey, sweet! That might be slick for situations where three to nine
SQLite databases need to be continuously synchronized through automated
consensus. That scenario is quite a bit different from DV
On 07/23/2016 07:05 PM, Ron W wrote:
> Hello,
>
> What you are thinking is not impossible.
>
Thanks for the confirmation, I've been speculating about novel system
architectures and unusual use-cases without sufficient fundamental
knowledge and experience - that makes for dangerous propositions a
On 07/24/2016 03:49 AM, Eduardo Morras wrote:
>
> You can use the Sqlite session extension to produce patch files between
> db file versions. It has some restrictions on schema and documentation
> is scarce, but if I had the same goal as you, I'll try that way.
>
> To use it you need Sqlite versi
On 07/23/2016 03:37 PM, Richard Hipp wrote:
> On 7/23/16, Adam Jensen wrote:
>> I'm a little puzzled by the lack of response
>
> Lots of people on vacation. Not much activity on *any* project during
> the summer months
>
I'm beginning to suspect that I migh
iliar with these communities and I am concerned that I might have
stumbled into some kind of faux pas here.
On 07/14/2016 02:31 PM, Adam Jensen wrote:
> I sent a message last night before joining the mailing list (today) and
> I'm not certain if it (last night's post) was distributed
I sent a message last night before joining the mailing list (today) and
I'm not certain if it (last night's post) was distributed to the list or
not. It's not displayed in the list archive yet. Just in case, here it is:
On 07/13/2016 06:18 PM, Adam Jensen wrote:
> This might b
On Tue, 21 Jul 2015 12:40:27 -0700
jungle Boogie wrote:
> I'm not a maintainer but this is what I have done in the past, with
> guidance of others.
>
> 0. clone the repo
> 1. make your changes
> 2. fossil changes to list your changes
> 3. fossil diff filename
>
> here's the diff:
> --- www/webu
N00b here, I am reading the documentation on fossil-scm.org and as I
[inevitably] find issues how should they be reported? (Hey, it's free
proof-reading; might as well make use of it to improve the documents, right?)
For example,
http://fossil-scm.org/index.html/doc/trunk/www/webui.wiki
within
55 matches
Mail list logo