On May 5, 2008, at 9:32 PM, Garth Corral wrote:
>
> On May 5, 2008, at 9:00 PM, Alexander Wagner wrote:
>> Pascal Georges wrote:
>>
>> Good Morning!
>>
>> [...]
>>> Great. I commited your patches into CVS as 95% of it is ok (and this
>>> will help me to start from that base). So we have time to th
On May 5, 2008, at 9:00 PM, Alexander Wagner wrote:
> Pascal Georges wrote:
>
> Good Morning!
>
> [...]
>> Great. I commited your patches into CVS as 95% of it is ok (and this
>> will help me to start from that base). So we have time to think about
>> the 5% left : @SHAREDIR@ in config.tcl.conf.
>
Pascal Georges wrote:
Good Morning!
[...]
> Great. I commited your patches into CVS as 95% of it is ok (and this
> will help me to start from that base). So we have time to think about
> the 5% left : @SHAREDIR@ in config.tcl.conf.
> I tested on Windows and I got no problem.
Sorry, I do not
2008/5/5 Alexander Wagner <[EMAIL PROTECTED]>:
> Pascal Georges wrote:
>
> Hi!
>
> > > This means there is no longer a need for config.tcl.conf, as it
> > will not be
> > > generated by autoconf : I will wait until everything is
> > validated, then
> > > simplify those thing
Garth Corral wrote:
Hi!
> In addition to the menu changes, there are a couple of small changes
> around scidShareDir to accommodate installation of an application
> bundle in an arbitrary location; scidShareDir was set to a static
> value of /usr/local/share/scid in the configure script. I h
2008/5/5 Garth Corral <[EMAIL PROTECTED]>:
>
> On May 5, 2008, at 10:43 AM, Pascal Georges wrote:
> > Maybe there are things I did not get, but I don't see the point in
> > packaging data and exec separately : I have some dependencies
> > between data and some features (training, books), and I'd p
Pascal Georges wrote:
Hi!
> > This means there is no longer a need for config.tcl.conf, as it
> will not be
> > generated by autoconf : I will wait until everything is
> validated, then
> > simplify those things.
>
> The point of this file was to make it possible
Pascal Georges wrote:
Hi!
> Point is, if you assume a Unix installation, scid is
> owned by root and not by the user. And thogh bases and
> books are an exception there're still some files with
> scid that are kept "for the site" and not "for the
> user". Usually these ar
On May 5, 2008, at 10:43 AM, Pascal Georges wrote:
> Maybe there are things I did not get, but I don't see the point in
> packaging data and exec separately : I have some dependencies
> between data and some features (training, books), and I'd prefer
> things to come in one simple package. I
2008/5/5 Garth Corral <[EMAIL PROTECTED]>:
>
> On May 5, 2008, at 6:48 AM, Marcin Kasperski wrote:
> >>> The point of this file was to make it possible to build scid
> >>> in Linux "packaged" way, where binaries and data are not
> >>> installed together, but we use sth like /usr/bin/scid (or
> >>>
On May 5, 2008, at 6:48 AM, Marcin Kasperski wrote:
>>> The point of this file was to make it possible to build scid
>>> in Linux "packaged" way, where binaries and data are not
>>> installed together, but we use sth like /usr/bin/scid (or
>>> /usr/games/scid) and /usr/share/scid/data/
>>
>> G
2008/5/5 Marcin Kasperski <[EMAIL PROTECTED]>:
> > > The point of this file was to make it possible to build scid
> > > in Linux "packaged" way, where binaries and data are not
> > > installed together, but we use sth like /usr/bin/scid (or
> > > /usr/games/scid) and /usr/share/scid/data/
> >
You will be able to change this parameter in next Scid release. The bug is
fixed and available through CVS.
Pascal
2008/5/5 Tod Damask <[EMAIL PROTECTED]>:
> How do I change that parameter? I now have 3.6.23 and the problem
> persists, unless I strip my variations.
> Tod
>
>
> Ok, this bug is fi
How do I change that parameter? I now have 3.6.23 and the problem persists,
unless I strip my variations.
Tod
Ok, this bug is fixed now (at least 4 years old
... ). The explanation is
simple : the parameter "Always keep games with
variations" was hidden
because of a simple UI bug,
> > The point of this file was to make it possible to build scid
> > in Linux "packaged" way, where binaries and data are not
> > installed together, but we use sth like /usr/bin/scid (or
> > /usr/games/scid) and /usr/share/scid/data/
>
> Given that books and bases directories are now user
> co
2008/5/5 Marcin Kasperski <[EMAIL PROTECTED]>:
> > This means there is no longer a need for config.tcl.conf, as it will not
> be
> > generated by autoconf : I will wait until everything is validated, then
> > simplify those things.
>
> The point of this file was to make it possible to build scid
>
> This means there is no longer a need for config.tcl.conf, as it will not be
> generated by autoconf : I will wait until everything is validated, then
> simplify those things.
The point of this file was to make it possible to build scid
in Linux "packaged" way, where binaries and data are not ins
2008/5/5 Garth Corral <[EMAIL PROTECTED]>:
>
> The menu/makefile patch isn't enough to build an application bundle,
> there's also an icon file (scid.icns) that I created from the
> original, and a plist file (Info.plist) that need to be part of the
> bundle. I've included these plus an extra pat
On Sun, 04 May 2008 18:47:04 +0200
Alexander Wagner <[EMAIL PROTECTED]> wrote:
> Benoit St-Pierre wrote:
>
> Hi!
>
> > Once upon a time, there was a Scid forum :
> > Do we need a forum ?
> >
> > If we (I mean : you, of course) answer "yes" to that question, there
> > comes the mighty seco
19 matches
Mail list logo
