Troy Simpson wrote:
> I have been looking at the issues and the first thing I'd like to clarify is
> that given Subversion utilises technologies that licenses need to be
> distributed with, shouldn't the licenses exist in the Subversion repository
> at a higher level? No external files should really be attached to the
> installer that do not exist inside the repository (except for binaries).
There's no real need to store the license files in the subversion
repository, except for the fact that it makes it easier to build binary
packages. At least the license files should already be included in the
zip files (the binaries), this is not a problem that the creator of the
installer has to solve.
I propose to include the license files in a licenses folder in the zip
package, so we can extend the install script to copy all files from this
licenses folder in the installer.
These are the license files we need to include:
(apache 2.0 license, same as apr)
> There is a LOT of manual setup required to make a Subversion setup file, and
> generally it takes a number of attempts before all pre-requisites are in
> place. I might try and see if I can simplify the installation to reduce
> errors in packaging.
I spent an hour this morning to download and install all tools needed to
make an installer from the zip file for 1.4.1. There are some manual
steps which can be eliminated, but all in all it's not too bad.
> At this stage, considering that most problems are pre-existing, it might be
> a better idea to try to fix the problems in a future installer rather than
> the current one so that we can avoid packaging files from a newer trunk
> (which may undergo further updates).
1.4.1 is coming out in the next days, would be nice if we could at least
fix some of the most obvious stuff, like the broken link to the svn
license file, copyright dates etc.
> Once all files are inside the repository we can make minor releases if
> necessary - we can make a new tag with corrections for the minor release.
> We can then merge those corrections to the trunk. Without a tag there is no
> real audit trail.
As far as I see the installer scripts only change the week before or after a release, be it a major or minor release, so as far as I'm concerned we can always use the latest version of trunk.
> -----Original Message-----
> From: Lieven Govaerts [mailto:firstname.lastname@example.org]
> Sent: Thursday, 21 September 2006 3:51 PM
> To: email@example.com
> Subject: [Fwd: Issues with the Windows installer package for svn 1.4]
> * in pre.rtf: the link to CHANGES is the version on trunk instead of the
> 1.4 version.
Attached patch will fix the link to CHANGES.
In the Windows installer, link to the CHANGES file of 1.4.x instead of trunk
* packages/windows-innosetup/Pre.rtf: change URL to 1.4.x branch.
--- packages/windows-innosetup/Pre.rtf (revision 22154)
+++ packages/windows-innosetup/Pre.rtf (working copy)
@@ -5,7 +5,7 @@
- http://svn.collab.net/repos/svn/trunk/CHANGES for more info.\par
+ http://svn.collab.net/repos/svn/branches/1.4.x/CHANGES for more info.\par
Subversion is using some external programs and libraries included in this package.\par
The proper licenses are in the licenses folder in the application path created after this installation.\par
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Oct 29 11:38:11 2006