Re: [fossil-users] Fossil for Android?

2011-02-28 Thread a . chavasse

On Feb 27, 2011 5:53am, Timothy Brown  wrote:

For your consideration,


How hard would it be to build Fossil for Android? For that matter how  
hard would it be to get Fossil built for iOS?
With all these Android tablets about to burst on the scene it would be  
nice to be able to take cloned repositories with you (if you start using  
tablets more than notebooks).


Taking your code/presentations/papers with you in a cloned Fossil  
repository would be nice.


Just trying to stir the pot...to get Fossil more places and seen by more  
developers. It would be cool to see Android and iOS listed in the  
downloads section.



Someone has actually been working on an iOS port, but I have no idea what  
the status is on it:

http://chiselapp.com/user/cutterpillow/repository/fossil-iOS
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] New features in Fossil - please test them out...

2011-02-28 Thread Richard Hipp
There have been a lot of changes to the Fossil sources over the past week.
If you are able, please compile the latest Fossil from sources and give it a
try.  Let me know if you encounter any problems.

Note:  Trying a "beta" of Fossil is not nearly as risky as it sounds.  You
are very unlikely to lose archived work.  (See
http://www.fossil-scm.org/fossil/doc/trunk/www/selfcheck.wiki for an
explanation of why not.)  About the worst that is going to happen with these
changes is that an execute-permission bit might get misapplied on an
"update" or "revert".

The two changes that need testing are:

(1) The ability to sync private branches.   See
http://www.fossil-scm.org/fossil/doc/trunk/www/private.wiki for additional
information.

(2) The fix to the execute-permission tracking problem of ticket
http://www.fossil-scm.org/fossil/doc/trunk/www/private.wiki

Note that when upgrading, the execute-permission bit information in your
local check-out (your _FOSSIL_ file) might not be quite right.  It is
recommended that you do:

 fossil checkout current

>From existing local checkouts in order to make sure that all the local
information is up-to-date.  If you fail to do this, some execute permission
bits might get turned off by mistake, but nothing worse than that should
happen.

Please report both success and failure.  I'm trying to get to the point were
we can do another precompiled-binary release in about a week or so.  Thanks
for your hep.

-- 
D. Richard Hipp
d...@sqlite.org
___
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] New features in Fossil - please test them out...

2011-02-28 Thread Stanislav Paskalev
To make it more in line with current fossil behavior, perhaps "scrub
--private" should mark private branches for deletion and "rebuild"
should delete them if there are any, just like shunned artifacts ?
(and undo should revert those if executed prior to rebuild)

Stanislav Paskalev

On Mon, Feb 28, 2011 at 5:09 PM, Richard Hipp  wrote:
> There have been a lot of changes to the Fossil sources over the past week.
> If you are able, please compile the latest Fossil from sources and give it a
> try.  Let me know if you encounter any problems.
>
> Note:  Trying a "beta" of Fossil is not nearly as risky as it sounds.  You
> are very unlikely to lose archived work.  (See
> http://www.fossil-scm.org/fossil/doc/trunk/www/selfcheck.wiki for an
> explanation of why not.)  About the worst that is going to happen with these
> changes is that an execute-permission bit might get misapplied on an
> "update" or "revert".
>
> The two changes that need testing are:
>
> (1) The ability to sync private branches.   See
> http://www.fossil-scm.org/fossil/doc/trunk/www/private.wiki for additional
> information.
>
> (2) The fix to the execute-permission tracking problem of ticket
> http://www.fossil-scm.org/fossil/doc/trunk/www/private.wiki
>
> Note that when upgrading, the execute-permission bit information in your
> local check-out (your _FOSSIL_ file) might not be quite right.  It is
> recommended that you do:
>
>  fossil checkout current
>
> From existing local checkouts in order to make sure that all the local
> information is up-to-date.  If you fail to do this, some execute permission
> bits might get turned off by mistake, but nothing worse than that should
> happen.
>
> Please report both success and failure.  I'm trying to get to the point were
> we can do another precompiled-binary release in about a week or so.  Thanks
> for your hep.
>
> --
> D. Richard Hipp
> d...@sqlite.org
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
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] fossil on windows-file-server with unc-path

2011-02-28 Thread Will West
Easy fix while people think of real answers: map a drive letter to \\server\path
--
Will Owen West



On Mon, Feb 28, 2011 at 01:15, Christian Busch  wrote:
> Hello user group,
>
> I have an issue with unc pathes on a windows machine.
> My fossil version is: This is fossil version [6502627a3e] 2011-02-08 12:52:37 
> UTC
>
> Is there any known restraint regarding unc pathes on windows?
>
> I tried the following:
> I had a repo on my harddisk drive C, cloned it to a file server using the 
> unc-path \\server\path\subpath\repo.fossil
> This worked perfectly.
> Then I made changes in the local repository and I tried to push these changes 
> into the remote repo on the file server and I get this error message: 
> fossil.exe: server sends error: >repository does not exist or
>  is in an unreadable directory: /server/path/subpath/repo.fossil
>
> The error message "changed" backslashes to slashes and skipped one backslash 
> before the server-name.
>
> It is possible to start the local server with the remote repo and push the 
> changes using http://127.0.0.1:8080/ but not directly with the file path.
>
> Anybody has the same experience? Should it be possible to do this or do I 
> have a comprehension problem?
>
> Thank you for any feedback.
> Regards, Christian
> --
> NEU: FreePhone - kostenlos mobil telefonieren und surfen!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
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] Fossil - new user question on multiple clones and autosync?

2011-02-28 Thread Richard Hipp
On Mon, Feb 28, 2011 at 10:30 AM,  wrote:

> Hi,
> New user dumb question.
> Fossil Documentation:
>
> "By default, everything you check into a Fossil repository is shared
> to all clones of that repository. In Fossil, you don't push and pull
> individual branches; you push and pull everything all at once."
>
> I do not see this behavior?
> I want autosync to commit changes to more than 1 clone, but I only see
> 1 clone getting the updates.
> Yes, I can manually push to the remaining clones, but wanted to know
> if there is an option to add multiple clones in the sync process?
>

There is not currently an option to get Fossil to auto-sync to more than one
repository.

On the SQLite project (for which Fossil was created) we have three separate
repositories on three geographically distributed servers.  One is the "main"
server to which all the developers autosync.  The two "mirrors" sync against
the "main" periodically using a cron job.  This has worked well enough for
us.  We can still sync against a mirror, if desired or if the main goes
down, but usually we just use the main server and let the cron jobs worry
about keeping everybody in sync.


-- 
D. Richard Hipp
d...@sqlite.org
___
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] fossil on windows-file-server with unc-path

2011-02-28 Thread Richard Hipp
On Mon, Feb 28, 2011 at 2:15 AM, Christian Busch wrote:

> Hello user group,
>
> I have an issue with unc pathes on a windows machine.
> My fossil version is: This is fossil version [6502627a3e] 2011-02-08
> 12:52:37 UTC
>
> Is there any known restraint regarding unc pathes on windows?
>
> I tried the following:
> I had a repo on my harddisk drive C, cloned it to a file server using the
> unc-path \\server\path\subpath\repo.fossil
>

I'm not real clear exactly what a unc-path is, and it is a reasonable guess
that I don't have the hardware/software at hand to test any changes that
might be made to support them.  So I'm going to be looking to the windows
experts on this list to suggest patches for fixing this.


> This worked perfectly.
> Then I made changes in the local repository and I tried to push these
> changes into the remote repo on the file server and I get this error
> message: fossil.exe: server sends error: >repository does not exist or
>  is in an unreadable directory: /server/path/subpath/repo.fossil
>
> The error message "changed" backslashes to slashes and skipped one
> backslash before the server-name.
>
> It is possible to start the local server with the remote repo and push the
> changes using http://127.0.0.1:8080/ but not directly with the file path.
>
> Anybody has the same experience? Should it be possible to do this or do I
> have a comprehension problem?
>
> Thank you for any feedback.
> Regards, Christian
> --
> NEU: FreePhone - kostenlos mobil telefonieren und surfen!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>



-- 
D. Richard Hipp
d...@sqlite.org
___
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] New features in Fossil - please test them out...

2011-02-28 Thread Ron Aaron
On 02/28/2011 05:09 PM, Richard Hipp wrote:
> There have been a lot of changes to the Fossil sources over the past
> week.  If you are able, please compile the latest Fossil from sources
> and give it a try.  Let me know if you encounter any problems.

Not something about this latest build specifically, but a general gripe. 

I try to keep my fossil pretty much "up to date".  Often, I get told
that a repository is an older schema or something, and that I need to
run "fossil rebuild" on it.

My gripe is that if fossil already knows what is wrong, it should just
do a rebuild without telling me I should do it...

___
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] New features in Fossil - please test them out...

2011-02-28 Thread Joerg Sonnenberger
On Mon, Feb 28, 2011 at 06:09:42PM +0200, Ron Aaron wrote:
> My gripe is that if fossil already knows what is wrong, it should just
> do a rebuild without telling me I should do it...

I disagree, it can be very unwanted if you have a large repository.
E.g. it might require schedulung downtime or extra disk space etc.

Joerg
___
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] New features in Fossil - please test them out...

2011-02-28 Thread Ron Aaron
On 02/28/2011 06:15 PM, Joerg Sonnenberger wrote:

> I disagree, it can be very unwanted if you have a large repository.
> E.g. it might require schedulung downtime or extra disk space etc.
>
>
Ah, well; that is a good point. 

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] [PATCH] Fix building with MSVC 6.0

2011-02-28 Thread Konstantin Khomoutov
Please consider two patches which fix building the trunk's HEAD with
MSVC 6.0.

The first patch is more of a hack -- it works around the absence of the
"long long" integer size modifier in that ancient compiler. I'm not
sure the patch should go in as is because, for instance sqlite3.* source
files do also have their own defines to handle 64-bit integers, and it
might worth thinking about introducing some common set of #ifdeffery to
make the solution more generic. Anyway, it works for me in its current
form.

The second patch (for win\Makefile.msc) simply enables building and
linking of shell.c -- seems like this makefile just gone out of sync
with the other Makefiles.


__int64.patch
Description: Binary data


vc-makefile.patch
Description: Binary data
___
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] fossil on windows-file-server with unc-path

2011-02-28 Thread Christian Busch

Hello,

thank you for the hint with the drive letter, I knew this option but I'd 
like to avoid this extra step.


I'm only working on windows machines so I don't know whether this is a 
windows specific problem or how it looks on other os. For the unc-path I 
only can refer to wikipedia: 
http://en.wikipedia.org/wiki/Path_%28computing%29#Uniform_Naming_Convention

But I guess you've already checked this.

Any suggestion more from somebody?

Thanks, Christian

Am 28.02.2011 16:44, schrieb Richard Hipp:



On Mon, Feb 28, 2011 at 2:15 AM, Christian Busch 
mailto:busch.christ...@gmx.de>> wrote:


Hello user group,

I have an issue with unc pathes on a windows machine.
My fossil version is: This is fossil version [6502627a3e]
2011-02-08 12:52:37 UTC

Is there any known restraint regarding unc pathes on windows?

I tried the following:
I had a repo on my harddisk drive C, cloned it to a file server
using the unc-path \\server\path\subpath\repo.fossil


I'm not real clear exactly what a unc-path is, and it is a reasonable 
guess that I don't have the hardware/software at hand to test any 
changes that might be made to support them.  So I'm going to be 
looking to the windows experts on this list to suggest patches for 
fixing this.


This worked perfectly.
Then I made changes in the local repository and I tried to push
these changes into the remote repo on the file server and I get
this error message: fossil.exe: server sends error: >repository
does not exist or
 is in an unreadable directory: /server/path/subpath/repo.fossil

The error message "changed" backslashes to slashes and skipped one
backslash before the server-name.

It is possible to start the local server with the remote repo and
push the changes using http://127.0.0.1:8080/ but not directly
with the file path.

Anybody has the same experience? Should it be possible to do this
or do I have a comprehension problem?

Thank you for any feedback.
Regards, Christian
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren: http://www.gmx.net/de/go/freephone
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org

http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




--
D. Richard Hipp
d...@sqlite.org 


--
christian busch
schleissheimer str 63
80797 muenchen
0179 7650333

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] [PATCH] Patches for MinGW makefile

2011-02-28 Thread Mark Janssen
Please find attached a patch that contains the following changes to
the windows Makefile.mingw

* Build the fossil.exe with the icon file in /win
* Add a setup target to the Makefile to create a windows installer
(requires NSIS)
* Change the Makefile so that SSL enabled builds can be created by
defining FOSSIL_ENABLE_SSL

I can split the patch in separate patches if need.

Regards,
Mark


mingw-build.patch
Description: Binary data


icon.rc
Description: Binary data
___
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] [PATCH] Fix building with MSVC 6.0

2011-02-28 Thread Venkat Iyer

Konstantin,

Thanks.  I still build a lot of things with MSVC 6.0 (originally
because it was the last version which didn't need runtime dlls to be
installed, though I don't know if that's still true).

 - Venkat


-Original Message-
From: Konstantin Khomoutov 
Sent: Monday, February 28, 2011 21:51:06
Subject: [fossil-users] [PATCH] Fix building with MSVC 6.0

Please consider two patches which fix building the trunk's HEAD with
MSVC 6.0.

The first patch is more of a hack -- it works around the absence of
the "long long" integer size modifier in that ancient compiler. I'm
not sure the patch should go in as is because, for instance sqlite3.*
source files do also have their own defines to handle 64-bit integers,
and it might worth thinking about introducing some common set of
#ifdeffery to make the solution more generic. Anyway, it works for me
in its current form.

The second patch (for win\Makefile.msc) simply enables building and
linking of shell.c -- seems like this makefile just gone out of sync
with the other Makefiles.
___
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] [PATCH] Fix building with MSVC 6.0

2011-02-28 Thread Ross Berteig
At 03:41 PM 2/28/2011, Venkat Iyer wrote:
 >I still build a lot of things with MSVC 6.0 (originally
 >because it was the last version which didn't need runtime dlls 
to be
 >installed, though I don't know if that's still true).

Yes and no. Its runtime DLL is included with (essentially) all
versions of Windows itself. Later C runtimes are often likely to
be present, but cannot be guaranteed to be present.

As an alternative to MSVC6, you can also use MinGW GCC. By
default it links to the same C runtime DLL (MSVCRT.DLL) as MSVC6,
but provides more standards compliance than MSVC6, and is often
easier to use for building portable code.


Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users