Jean-Marc Lasgouttes wrote:
Branches for the installer is not a bad solution.
Then I'll just upload the installer to the current location and we'll
have a different branch for 1.4 and 1.5. I want to finish this now.
Joost
Jean-Marc Lasgouttes wrote:
Branches for the installer is not a bad solution.
Then I'll just upload the installer to the current location and we'll
have a different branch for 1.4 and 1.5. I want to finish this now.
Joost
Lars Gullik Bjønnes wrote:
Joost Verburg [EMAIL PROTECTED] writes:
| Bo Peng wrote:
| 1. upload lyx win installer to svn/winInstaller (parallel to
| www-devel)
That would be svn://svn.lyx.org/lyx/winInstaller then.
| 2. upload patches to various external programs (with readme)
| 3. upload
Joost Verburg wrote:
Bo Peng wrote:
Are you going to upload sources or patches of aspell etc? It is better
to put the installer in the trunk, since a branch sounds temporary to
me. Then, we'd better only keep patches to external programs. If the
installer works for both 1.4.x and 1.5.x, the
Lars Gullik Bjønnes wrote:
Joost Verburg <[EMAIL PROTECTED]> writes:
| Bo Peng wrote:
| > 1. upload lyx win installer to svn/winInstaller (parallel to
| > www-devel)
That would be svn://svn.lyx.org/lyx/winInstaller then.
| > 2. upload patches to various external programs (with readme)
| > 3.
Joost Verburg wrote:
Bo Peng wrote:
Are you going to upload sources or patches of aspell etc? It is better
to put the installer in the trunk, since a branch sounds temporary to
me. Then, we'd better only keep patches to external programs. If the
installer works for both 1.4.x and 1.5.x, the
Joost Verburg [EMAIL PROTECTED] writes:
| Bo Peng wrote:
| 1. upload lyx win installer to svn/winInstaller (parallel to
| www-devel)
That would be svn://svn.lyx.org/lyx/winInstaller then.
| 2. upload patches to various external programs (with readme)
| 3. upload modified binaries to
Joost Verburg <[EMAIL PROTECTED]> writes:
| Bo Peng wrote:
| > 1. upload lyx win installer to svn/winInstaller (parallel to
| > www-devel)
That would be svn://svn.lyx.org/lyx/winInstaller then.
| > 2. upload patches to various external programs (with readme)
| > 3. upload modified binaries to
Hello,
I'm currently working on a package with the source code of the new
Windows installer including the required utilities (modified versions of
Aspell, Aiksaurus, Dvipost, DTL, Bakoma fonts etc.). This will make it a
lot easier to compile the installer package and create a stable Windows
I'm currently working on a package with the source code of the new
Windows installer including the required utilities (modified versions of
Aspell, Aiksaurus, Dvipost, DTL, Bakoma fonts etc.). This will make it a
lot easier to compile the installer package and create a stable Windows
version of
Bo Peng wrote:
Are you going to upload sources or patches of aspell etc? It is better
to put the installer in the trunk, since a branch sounds temporary to
me. Then, we'd better only keep patches to external programs. If the
installer works for both 1.4.x and 1.5.x, the top directory (parellel
Joost Verburg wrote:
Bo Peng wrote:
Are you going to upload sources or patches of aspell etc? It is better
to put the installer in the trunk, since a branch sounds temporary to
me. Then, we'd better only keep patches to external programs. If the
installer works for both 1.4.x and 1.5.x, the top
I think it's better to upload the complete source of Aspell etc. instead
of just a patch. This will allow the whole package to be compiled at
once without having to download and patch a large number of tools. Of
course it will also be in this separate directory.
Is there a compiler issue for
Abdelrazak Younes wrote:
It will be good enough if you convince them to put the needed windows
binaries in SVN. But even that is far from sure.
Why binaries in SVN instead of source code?
Joost
Bo Peng wrote:
Is there a compiler issue for aspell etc? I heard that you have to
have Peter's patch for aspell/cvs to use msvc. This is unfortunate
since msvc will generate smaller and potentially faster binary
files...
The 1.4 releases will use MinGW. For future 1.5 releases I will try to
I wish you good luck convincing the big guns. Pragmatism is an insult
in this list.
It will be good enough if you convince them to put the needed windows
binaries in SVN. But even that is far from sure.
We can do patch, source and binary of external programs. They are in
an increasing order of
Joost Verburg wrote:
Abdelrazak Younes wrote:
It will be good enough if you convince them to put the needed windows
binaries in SVN. But even that is far from sure.
Why binaries in SVN instead of source code?
Because it is not the job of LyX to maintain other project source code,
so they
Bo Peng wrote:
My suggestion? patches and binaries. We have the best of both ends.
Binaries on the FTP server and patches in SVN is also fine with me. Then
the remaining question is whether to maintain identical installers in
branch and trunk or have a separate directory.
Joost
Because it is not the job of LyX to maintain other project source code,
so they say.
Exactly, also because it is difficult to keep them up to date. What if
aspell has a new release?
The binaries (including headers and libs like your Aspell package)
should be compatible for all version of
Binaries on the FTP server and patches in SVN is also fine with me.
This is what I just proposed.
Then the remaining question is whether to maintain identical installers in
branch and trunk or have a separate directory.
Which ever is easier for you.
Bo
Bo Peng wrote:
1. upload lyx win installer to svn/winInstaller (parallel to www-devel)
2. upload patches to various external programs (with readme)
3. upload modified binaries to devel.lyx.org/contrib or /winInstaller.
I agree. Lars, is this SVN directory OK?
Joost
Bo Peng wrote:
Because it is not the job of LyX to maintain other project source code,
so they say.
Exactly, also because it is difficult to keep them up to date. What if
aspell has a new release?
Aspell releases are not frequent at all. Same for Aiksaurus (2003), etc.
If that is the case
Hello,
I'm currently working on a package with the source code of the new
Windows installer including the required utilities (modified versions of
Aspell, Aiksaurus, Dvipost, DTL, Bakoma fonts etc.). This will make it a
lot easier to compile the installer package and create a stable Windows
I'm currently working on a package with the source code of the new
Windows installer including the required utilities (modified versions of
Aspell, Aiksaurus, Dvipost, DTL, Bakoma fonts etc.). This will make it a
lot easier to compile the installer package and create a stable Windows
version of
Bo Peng wrote:
Are you going to upload sources or patches of aspell etc? It is better
to put the installer in the trunk, since a branch sounds temporary to
me. Then, we'd better only keep patches to external programs. If the
installer works for both 1.4.x and 1.5.x, the top directory (parellel
Joost Verburg wrote:
Bo Peng wrote:
Are you going to upload sources or patches of aspell etc? It is better
to put the installer in the trunk, since a branch sounds temporary to
me. Then, we'd better only keep patches to external programs. If the
installer works for both 1.4.x and 1.5.x, the top
I think it's better to upload the complete source of Aspell etc. instead
of just a patch. This will allow the whole package to be compiled at
once without having to download and patch a large number of tools. Of
course it will also be in this separate directory.
Is there a compiler issue for
Abdelrazak Younes wrote:
It will be good enough if you convince them to put the needed windows
binaries in SVN. But even that is far from sure.
Why binaries in SVN instead of source code?
Joost
Bo Peng wrote:
Is there a compiler issue for aspell etc? I heard that you have to
have Peter's patch for aspell/cvs to use msvc. This is unfortunate
since msvc will generate smaller and potentially faster binary
files...
The 1.4 releases will use MinGW. For future 1.5 releases I will try to
I wish you good luck convincing the big guns. "Pragmatism" is an insult
in this list.
It will be good enough if you convince them to put the needed windows
binaries in SVN. But even that is far from sure.
We can do patch, source and binary of external programs. They are in
an increasing order
Joost Verburg wrote:
Abdelrazak Younes wrote:
It will be good enough if you convince them to put the needed windows
binaries in SVN. But even that is far from sure.
Why binaries in SVN instead of source code?
Because it is not the job of LyX to maintain other project source code,
so they
Bo Peng wrote:
My suggestion? patches and binaries. We have the best of both ends.
Binaries on the FTP server and patches in SVN is also fine with me. Then
the remaining question is whether to maintain identical installers in
branch and trunk or have a separate directory.
Joost
Because it is not the job of LyX to maintain other project source code,
so they say.
Exactly, also because it is difficult to keep them up to date. What if
aspell has a new release?
The binaries (including headers and libs like your Aspell package)
should be compatible for all version of
Binaries on the FTP server and patches in SVN is also fine with me.
This is what I just proposed.
Then the remaining question is whether to maintain identical installers in
branch and trunk or have a separate directory.
Which ever is easier for you.
Bo
Bo Peng wrote:
1. upload lyx win installer to svn/winInstaller (parallel to www-devel)
2. upload patches to various external programs (with readme)
3. upload modified binaries to devel.lyx.org/contrib or /winInstaller.
I agree. Lars, is this SVN directory OK?
Joost
Bo Peng wrote:
Because it is not the job of LyX to maintain other project source code,
so they say.
Exactly, also because it is difficult to keep them up to date. What if
aspell has a new release?
Aspell releases are not frequent at all. Same for Aiksaurus (2003), etc.
If that is the case
36 matches
Mail list logo
