On 2018-06-22 20:40, Joerg Sonnenberger wrote:
[---]
> BTW, the main mercurial list uses the following mail format for "batch"
> changes:
>
> https://www.mercurial-scm.org/pipermail/mercurial-devel/2018-June/117551.html
This is highly machine parse-friendly. I like it a lot.
--
Kind Regards
dy Monday in my timezone, but the news outlets don't seem to care
> about non-US timezones :/.
Someone on twitter jested: "Sign in with your Office 365 account to
access github.". I think there are a lot of people a gritting their
teeth over that joke right now.
--
Kind Re
On 2018-06-04 00:35, Stephan Beal wrote:
[---]
> It does kind of make sense: the global leader in creating
> market-leading-yet-unusable software acquires one more piece of
> market-leading-yet-unusable software.
This appeals to my sense of order. :)
--
Kind Regards,
Jan D
On 2018-04-11 00:17, Stephan Beal wrote:
> i suspect that the old sqlite version has something to do with this. Try
> using "fossil sqlite" instead of sqlite3.
D'oh! Of course it is; I knew you were right before even trying.
Thanks!
--
Kind Re
ded up in the same state.
Browsing the source online repo seems to work fine, so I'm assuming
it's a local problem -- but how can it end up in this state? I did no
more than clone it.
--
Kind Regards,
Jan Danielsson
___
fossil-users mailing
e's even a page for it on fossil's
wiki. You could start by comparing that to your configuration. (That
said, I haven't actually followed that guide; I don't recall if it was
for SSL, and nor do I know if cloning works through it).
--
Kind
solution
works with regards to client certificates/keys.
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
r to go back to the original idea of using
statically-linked libraries for the pre-built binaries. That way when
Apple decide to eliminate the dynamic libraries as well (not that I
think they can do that any time soon) the monolithic fossil binary will
continue to work.
--
Kind regards,
Jan D
-C) library
instead. The dynamic OpenSSL libraries remain in the system for
compatibility, but they no longer include the headers -- so when you
build fossil on new:ish Macs (read: XCode), build systems tend to find
non-system instances of OpenSSL and use them instead.
--
Kind rega
for that.". (As it happens, this tool X
was a desktop application for the local checkout, which - in my mind -
kind of defeated the purpose).
Maybe this is tangentially related to the cathedral vs bazaar
discussion; with Fossil, you typically have a central
plans
(not for 2.0, 2.1 or beyond). There's a separate project which is
designed to accomplish what you're looking for:
http://fossil.wanderinghorse.net/repos/libfossil
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-us
On 2017-02-04 14:07, Konstantin Khomoutov wrote:
> On Fri, 3 Feb 2017 09:00:54 -0700
> Warren Young wrote:
>
>> https://developers.slashdot.org/story/17/02/03/1427213/microsoft-introduces-gvfs-git-virtual-file-system
>
> Care to elaborate a bit?
[---]
Granted, I just skimmed a few seconds, b
On 2017-01-04 20:06, Damien Sykes-Lindley wrote:
> Hi there,
> I have recently delved into the technical joys and jargon of Linux, but I’m
> still fairly new so you’ll have to excuse me if these questions are more
> system than Fossil related.
> 1. I am currently only aware of installing software
On 05/08/16 02:51, Ross Berteig wrote:
[---]
> I just created test cases for fossil set manifest that verify that the
> files manifest, manifest.uuid, and manifest.tags appear and disappear as
> the setting is changed. I did not verify that any of the files have the
> right content.
Many thanks
On 04/08/16 20:44, Warren Young wrote:
>> That's one of the things I realized after a few
>> failures -- whatever scheme you come up with, it has its limitations.
>
> That’s part of what I mean, but I’m not just talking about simple
> limitations. The second and third applications of the code in
On 04/08/16 00:08, Warren Young wrote:
>> This means that the same
>> information is available in two different places
>
> Only two? Aren’t you the lucky one. :)
Not that lucky, unfortunately. :( That was mostly referring to
cases such as sqlite and even fossil itself. In our case it refer
Hello,
Since I've finally got a few days off, I've done some updates to the
jan-manifest-tags; merge with trunk, made some bugfixes, and thought I'd
reintroduce the branch (since it's been a while).
The basic idea is the following: It's common practice for projects
to tag new release versi
On 02/05/16 22:17, Steve Schow wrote:
> I wish to include my fossil repos in backup to cloud backup service.
>
> what is the best approach for doing this? if a fossil operation is in the
> middle of trying to do something when the automated cloud backup daemon
> decides to backup the repo file,
On 11/04/16 17:17, Stephan Beal wrote:
[---]
>>Is there a timestamp for when artifacts where locally added to the
>> repository? (I'm not overly concerned with configuration changes and
>> such; it's detecting checkins, tickets and other artifact changes that's
>> important).
>
> rcvfrom migh
Hello,
Short version: What's the best way to determine if a repository has
changed?
I have two systems which are sync'd in a cronjob. On one of the
systems I run a cronjob which should take action only if the repository
was changed. Before there were two systems I simply used mtime on th
On 02/02/16 23:19, Martin Vahi wrote:
[---]
> Thank You for the comparison. What regards to
> Your statement that "e-mail refuses to go away", then
> my answer is that the majority of the population on
> planet Earth does not consist of software developers
> or old-school communications technicians
Hello,
This started happening recently:
Undefined symbols for architecture x86_64:
"_compress", referenced from:
_blob_compress in blob.o
_sqlcmd_compress in sqlcmd.o
(maybe you meant: _blob_compress2, _test_cycle_compress ,
_compress2_cmd ,
On 21/01/16 19:17, Stephan Beal wrote:
> i recently started using the Blitz skin on all my repos, but
> fixed-/max-width pages annoy me to no end, so it go hacked every so
> slightly to remove the max width. For anyone interested, here it is:
>
> http://fossil.wanderinghorse.net/download/skin.foss
On 17/01/16 06:53, Yannick Duchêne wrote:
> I received a spam from `nella_br...@expertisetour.xyz` with subject “RE:
> [fossil-users] What does the Older button's intended to do in the web UI?”.
> So it appears a spammer subscribed to this mailing list, intercepts messages
> and replies to it, w
On 09/01/16 01:15, bch wrote:
> Just talked to Joerg off-list (who indicated that he updated fossil
> to latest on his server), and:
>
> $ fossil pull -verily
>
> Pull done, sent: 5064 received: 49107978 ip: 85.214.214.108
>
> $ fossil timeline
> === 2015-05-30 ===
> 14:42:26 [0bb26b5ab6] *CU
On 05/01/16 09:14, Steve Stefanovich wrote:
[---]
>>Is this not sufficient for your needs? I'm not completely opposed to
>> implementing what you're asking for, but if it can already be done without
>> adding a "within a checkout" special case, I would prefer to leave it as it
>> is.
>
> I d
On 04/01/16 08:18, Steve Stefanovich wrote:
> Would it be too difficult to put the branch tag (i.e the tag with asterisk
> from 'fossil br li' output) in the first line of manifest.tags?
It probably wouldn't, but I've been trying to keep the code agnostic
with regards to being used in a checko
Hello,
drh and sgbeal brought up the following points:
1) Make sure an existing [managed] manifest.tags isn't overwritten.
2) fossil add needs to be made manifest.tags-aware.
3) Tarballs and zips need to be made manifest.tags-aware.
4) fossil clean needs to be made manifest.tags
On 04/01/16 02:02, Richard Hipp wrote:
> On 1/3/16, bch wrote:
>> Indeed. I thought maybe the \n of the checkin-card (is this the right
>> characterization ?) bug/fix might fix what I've been experiencing, so
>> I updated to the latest. I'm nearly always running the tip of TRUNK.
>
> Any idea wha
On 01/01/16 18:43, Jan Danielsson wrote:
[---]
>Optimally the tagged version _is_ the source version. [...]
I'm home sick, so I started working on this in the branch
jan-manifest-tags.
I'd like some feedback on the settings semantics. What I want to
accomplish is that
Hello,
I have build systems which use the commit id from the manifest to
embed the commit artifact id in the binary. I also, in most projects,
have an ordinal version number which is loosely coupled between the
repository and the build system/source in the sense that I can forget to
update the
On 03/11/15 00:38, Scott Robison wrote:
>>> On 11/2/15, Jan Danielsson wrote:
>>>>
>>>> Supporting symlinks on Windows would currently be a little mess.
>>>
>>> What if we just say that symlinks don't work on Windows and that if
>>
On 03/11/15 00:00, Warren Young wrote:
> On Nov 2, 2015, at 3:56 PM, Richard Hipp wrote:
>>
>> On 11/2/15, Jan Danielsson wrote:
>>>
>>> Supporting symlinks on Windows would currently be a little mess.
>>
>> What if we just say that symlinks don
On 02/11/15 23:23, Warren Young wrote:
>> Windows will ultimately get decent symlink support.
>
> I doubt it. Microsoft has tried to take a bite of that apple twice, and
> screwed it up both times.
>
> First there was the Windows 95 *.lnk file feature, which is basically only a
> symlink to Wi
On 01/11/15 13:30, Damien Sykes-Pendleton wrote:
> I’m running Windows. I’m not personally running anything on port 80, though I
> get a blank web page (as opposed to a 404 or problem loading error) when I
> visit localhost.
I forget the name of the tool, but in there's a nifty tool for
Windo
On 31/10/15 06:27, Michal Suchanek wrote:
[---]
>> (For instance, my recent thread about how to clip off a a branch via the
>> command line when the UI can’t do it because it was created empty, something
>> Fossil can’t do, but which apparently CVS or SVN can, so it got into my
>> Fossil tree wh
On 16/08/15 19:56, Saul Hazledine wrote:
> Hello,
> I have been using a self-signed certificate on my Fossil server for
> the last year and it just expired. I have replaced the expired
> self-signed certificate with a new/different self-signed certificate.
I assume you aren't using client cer
On 18/07/15 17:09, Scott Robison wrote:
> Still on phone. Instead of -euser how about -author? Instinctively seems
> less clumsy but it's just a knee-jerk reaction to -euser which seems both
> long and short simultaneously. :)
I agree x 2.
--
Kind Regards,
Jan
On 17/06/15 11:38, Joerg Sonnenberger wrote:
[---]
> Sadly, a plain pull is not 100% read-only, so WAL doesn't help avoiding
> such problems.
Out of curiosity; why aren't pulls 100% read-only on the server?
--
Kind Regards,
Jan
___
fossil-users mail
On 05/06/15 13:08, jim Schimpf wrote:
[---]
> EDITED Docs/HayJam.pdf
> NOT_A_FILE Docs/images/Detector.graffle
> EDITED Docs/images/Detector.png
>
> So I then did a fossil rm of this file and did an OS rm and removed if from
> the directory.
>
> put it back in the directory and fossil ad
On 29/05/15 22:15, Matt Welland wrote:
> "We emphatically do NOT want Fossil second-guessing what branch you
> want to be on when you do "fossil update" without an argument."
>
> Whatever option you decide - either way you are second guessing the users
> intent.
>
> 1. Current behavior is really,
On 13/03/15 19:11, James Moger wrote:
[---]
> Blitz has two variants (with logo & without logo). It includes an
> alternative Ticket page layout and several image resources which may be of
> use to other skins.
Would you be willing to change the upper-case 'A-F' in hex digits to
lower-case in
On 13/03/15 19:11, James Moger wrote:
> Hello Fossil community,
[---]
This just became my new favorite skin. Thank you for submitting this.
--
Kind Regards,
Jan
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm
On 13/03/15 20:55, Richard Hipp wrote:
>> Few organizations have the problem that the full power of Git solves.
> And yet many organizations voluntarily take on the problems that come
> with using Git. Weird.
One shouldn't underestimate the power of "because everyone else does it".
--
Kind R
On 08/03/15 06:48, Andy Bradford wrote:
> There have recently been some changes to make short UUIDs more
> prominent, however, I think that new checkins should still display the
> full UUID:
[---]
> Thoughts?
None other than a simple "I agree".
/Jan
___
On 06/03/15 15:10, Jan Nijtmans wrote:
[---]
> "fossil rename" already exists as alias to "fossil mv", so I
> suggest to add "fossil forget" as alias to "fossil rm". Then
> later the behavior of fossil rm/mv" can be modified, while
> forget/rename will continue to behave as rm/mv do now.
>
> Any o
On 02/02/15 23:23, Warren Young wrote:
>> The annoying thing is that when it fails, it wipes away whatever
>> progress it has made.
> Yes, well, that’s the nature of transactional DB updates: all or nothing.
Implied: There's only one way to use transactions when performing
initial synchroniza
Hello,
I used to have major difficulties cloning huge repositories. (See
http://lists.fossil-scm.org:8080/pipermail/fossil-users/2014-May/016234.html).
In that thread the commit
http://www.fossil-scm.org/index.html/info/b4dffdac5e706980d911a0e672526ad461ec0640
was brought up as a potential
On 17/10/14 20:01, Jan Danielsson wrote:
[.. -wal & -shm remain after ctrl-c:ing out of fossil ui ..]
>A quick grep through the source leads me to believe that there is no
> registered signal handler to handle SIGINT apart from when an sqlite
> shell is started. Which leave
Hello,
I just noticed something which I can't recall seeing before. I
started "fossil ui" on a repository (-R foo.fossil), and when I hit
ctrl-c, it terminated as expected, but it left the corresponding -shm
and -wal files. I'm pretty sure I have used fossil ui on wal'd fossil
repository data
On 25/09/14 13:18, Matt Wellans wrote:
> I suspect fossil would slow down faster than git in that scenario but I'd
> also argue that because fossil is easier to understand that scenario is a
> little less likely to happen.
Let's all be honest here; this a unique case where you'd _want_ it to
On 12/06/14 20:29, Ron Aaron wrote:
> Nope, no proxy. And I can connect from my linux clients just fine.
>
> I tend to think it's related to the certificates.
openssl in Mac OS X is very old, so if you're using EC, RSA/PSS or
something of the sort it could be an issue.
--
Kind Regards,
Jan
On 12/06/14 18:06, Ron Aaron wrote:
> OK, my second fossil question in one day:
>
> I recently moved my repo from standard http to https (behind Apache)
>
> My linux machines had no problem with the change over.
>
> But the OS/X machine cannot connect to my repo. I get:
>
> SSL: cannot connect
On 02/05/14 19:57, Andy Bradford wrote:
>>> Artifacts sent: 0 received: 895 Error: Database error: database is locked:
>>> {UPDATE event SET mtime=(SELECT m1 FROM time_fudge WHERE mid=objid) WHERE
>>> objid IN (SELECT mid FROM time_fudge);} <#key_3_2>
>>[...]
>>As you say, it is highly rep
On 10/05/14 10:53, Gerald Gutierrez wrote:
[---]
> pContent=, N=) + 50 at http_ssl.c:399
>396 size_t got;
>397 size_t total = 0;
>398 while( N>0 ){
> -> 399 got = BIO_read(iBio, pContent, N);
>400 if( got<=0 ) break;
>401 total += got;
>402 N -= got;
>
On 18/04/14 17:52, Matt Welland wrote:
> Just FYI, I'm seeing this kind of message quite often. This is due to
> overlapping clone operations on large fossils on relatively slow disk.
[---]
> Artifacts sent: 0 received: 895 Error: Database error: database is locked:
> {UPDATE event SET mtime=(SELEC
Hello,
I did some work to get https-over-proxy working because both a friend
and I both needed it, and there was a ticket requesting the feature.
Now the place where my friend works no longer uses proxies for
outgoing traffic, so he no longer needs it, and I very rarely use it.
So, the
On 28/10/13 13:39, Jan Nijtmans wrote:
[---]
> Conclusion: your branch works fine as long as the password is
> not taken from the (https) url.
>
> I hope this feedback is useful to you.
Yes, very useful. We only use client certificates, and apache is set
up to set REMOTE_USER from the client c
Hello,
The jan-httpsproxytunnel branch has been tested on NetBSD, Mac OS X,
Linux and Windows against three different proxies, at two very different
environments, and it is working well.
Feedback from people more accustomed to the world of http proxies
would be appreciated.
/Jan
___
;.
--
Kind regards,
Jan Danielsson
signature.asc
Description: OpenPGP digital signature
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
been -- so slight
rewiring is required.
The usual check, to avoid duplicate work: Is anyone else working on
this already?
Is anyone planning on touching the ssl and/or http-proxy code in the
very near future?
--
Kind regards,
Jan Danielsson
signature.asc
Description: OpenPGP digital sign
On 08/23/13 18:10, Stephan Beal wrote:
> THANK YOU Mark - i wasn't paying attention. Jan, i'll send you the NEW
> password off-list.
For a short moment there I thought "This has to be the most trusting
community EVER!". :)
--
Ki
On 8/15/13 3:23 PM, John Long wrote:
> Hi, is it possible to ignore UNIX executables? I want to do an addr on a
> directory tree but I don't know how to tell fossil not to track the binaries
> since they have no naming pattern. Until now I've been living with it but it
> is very annoying and time f
On 8/11/13 2:07 AM, Chad Perrin wrote:
> So . . . let's say I have a server (running FreeBSD, and I'll probably
> be setting this up in a jail) and a router that can forward ports
> (already has SSH forwarded to this server). For argument's sake, let's
> say we're confined to only one port per pro
On 7/25/13 2:10 PM, Richard Hipp wrote:
> Move to banish __CYGWIN__ from both Fossil and SQLite sources. Do I have a
> second?
Seconded.
/Jan
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bi
On 7/25/13 2:05 PM, Lluís Batlle i Rossell wrote:
[---]
>> "grep" tells me that there are 33 instances of the __CYGWIN__ macro in
>> Fossil, in 8 different files. So if you use "sed" to change them all to
>> __CYGWIN_OFF_ (or something else harmless) and then do "./configure; make",
>> does it wor
/joelface.com/fossil/fdiff?v1=98aec3c55155011b&v2=d74d0c320c455abd&sbs=1(you
> can click anywhere inside a diff and use the left/right arrow keys to
> scroll)
I instantly can't live without it.
--
Kind regards,
Jan Danielsson
signature.asc
On 5/28/13 3:08 PM, Richard Hipp wrote:
> Survey: How many people know that in the web-based timeline for Fossil,
> you can click on any two nodes in the graph and get a diff between those
> two nodes?
I knew about it. When I read the first paragraph I was afraid you
were about to suggest remo
nd it easily if you
look for it), which should be somewhere in your "Start"-menu (under the
Visual Studio folder).
It'll set up the environment, and you'll be able to build fossil.
--
Kind regards,
Jan Danielsson
signature.asc
Description: OpenPGP digital signature
___
od in my book.
Nico and Joerg have made it clear to me, as a "rebase n00b", that
there's a very fossil way to have rebase. And if I read Michal Suchanek
correctly, we could even do it better than the arch-typical example of
rebase (git).
..and I hope Nico's construc
On 12/31/12 11:17, Nico Williams wrote:
[---]
> But I feel I must at least address this
> insinuation that I was trolling.
It's obvious that you aren't trolling. You don't have to defend
yourself against such nonsense.
--
Kind re
to limited clones -- but there's also a point in
limiting the size of the transfer, so the limited clone feels like a
better "first try" project, since it *definitely* solves one issue, and
_may_ solve another one.
--
Kind regards,
Jan Danielsson
_
e.
> not that this would matter for 99.9% of all projects.
Definitely true.
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
ame to fossil from bazaar which I abandoned
because it had scalability issues (which were even worse), so it's not
an exclusive fossil-problem. (git isn't affected by this though, but
it's noteworthy that the NetBSD project on github is (was?) imported
fro
regular basis and I
> really do not care what they do. Sorry.
You're missing the point; whatever problems with the actual
implementation, somehow others have managed to work around them and made
systems which work and that people are happy wi
works just like "fossil rm -f"
So, you'll be able to continue doing exactly what you are doing sans
s/rm/unmanage/. Everyone gets the behavior they want; others who
previously opposed real mv/rm seem to think that the latest suggestion
was a good comp
ever check in (clever) and then decide to stop tracking the files
> and issue 'fossil rm' assuming the files are left alone on disk and only
> then discover they were not). the transition period should guarantee
> that this will not evelove into a real-world problem I'd s
ected "relocate" and "obliterate" to
be a database only operations. For me, then rather than two commands
which has behavior which doesn't make sense, we'd have four.
I vote no, and again reaffirm my vote for the suggestion drh wrote
last night (local time).
--
Kin
uot;fossil delete"
>
> Stage 2 (after a stage 1 has been released for a while):
> (e) "fossil rm" works just like "fossil rm -f"
I vote "Yes" to all the above.
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
. Rather than
to talk about affecting real lives and how much money is involved and
other irrelevant nonsense, post those exact SCM definitions which are
relevant to the mv/rm issues and we can judge that information directly.
--
Kind regards,
Jan Danielsson
___
- is there any reason we can't
have both?
mv/rm - change to principle of least surprise
move/remove - behaves like current mv/rm
That way we all get what we want .. no?
--
Kind regards,
Jan Danielsson
___
fossil-users mailin
that I don't know what a VCS is or
> should do.
>
> Done with this thread. Keep it classy, detractors.
100% agree.
I must say, I'm not quite as fond of the fossil community as I once
was. I have no interest in being insu
On 12/14/12 00:23, Richard Hipp wrote:
> But, should there be an opt-in option to also make the disk changes?
Yes -- definitely.
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fos
of the cons?". I don't think there are many
annoyances with fossil, so the mv/rm behavior is a relatively minor
issue in the grand scheme of things, but still -- could we make it do
all of the work, not just half of it, I would be pleased and have one
less "con" in my list.
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
can be retrieve from previous version on
the repository.
What's "unsafe" with that behavior compared to the behavior we have
today?
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
the requested filesystem
operations immediately, and a few people are really upset about it. I
could write a wrapper script for those uses which does essentially the
following:
cp $file $file.tmp
fossil rm $file
mv $file.tmp $file
That way, people can still do it in two separate ste
in fossil to get the canonical behavior?).
I too am a little skeptical about adding too many settings to fossil,
but this is definitely one that I would think merits a setting if the
current (default) behavior is kept in 2.0.
Sorry if this came out as a rant; i
Hey,
I know it's "only" a short-cut for something which we could do
before. But I love this new feature; it's one of those "I didn't know
how much I wanted it until I started using it", and now I won't be able
to live without it.
Fantastic fe
ary play nice on 64-bit Windows it would
be great.
Anyone know if there's a trivial fix?
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
n my source tree, and "fossil
extras" just shows me all the gazillion files doxygen created.
Try living with it for a while and see if you change your mind. I did.
--
Kind regards,
Jan Danielsson
signature.asc
Description: OpenPGP digital signature
___
ssil users" is roughly empty.
Tag last win95-compatible version so anyone so inclined can dig it up
easily, just in case?
--
Kind regards,
Jan Danielsson
signature.asc
Description: OpenPGP digital signature
___
fossil-users mailing list
fossi
t-in wiki and ticket system): I think it's easier to read/parse
(mentally) and write than any wiki syntax I've seen so far. And even if
we get a nice WYSIWYG editor for the web interface (in theory rendering
the stored format irrelevant), I'll still be sitting writing wiki
docume
ver being overloaded,
but when I finally got all of it downloaded to one of my servers, I
tried to pull it to other systems from there, but I'm running into the
"504 Gateway Time-out" problem here as well (and this particular server
has lots of time to spare).
Any
feature.
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
lightly modified version of the final link
command line I got what I wanted. And if anyone else needs/wants it, the
information is easily found via a web search.
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.or
laris systems, and I want to be able to
build one fossil binary and move it around; so there's a practical
reason for my battle with static builds on Solaris).
> Can we address the dynamic configure/build issues, and then possibly
>
get about the details two months from now when I want to redo it
all, which is why I'm looking for a more automatic solution. :)
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
bout dynamically
linking when it was explicitly requested by the users that static
linking be used. At the same time, the way I look at it, the project
should build and run on standard OS installations, with as few separate
dependencies as possible.
Input is welcome.
--
Kind regards,
Jan Da
t;, and simply told it to always add
those extra libraries to LIBS, but it didn't, so I assume it's the build
system I don't understand). Any help is appreciated.
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fossil-users@li
a few times before.
(Yes, I know Solaris technically does it right, and I respect that,
but it's getting a little old running into this problem every five-six
months or so).
Thanks!
--
Kind regards,
Jan Danielsson
___
fossil-users mailing list
fo
1 - 100 of 155 matches
Mail list logo
