[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r14707 - branches/innosetup-hsuninsfix-5x-1.2.x

From: Jostein Chr. Andersen <jostein_at_josander.net>
Date: 2005-05-15 21:51:31 CEST

Hi Erik,

On Sunday 15 May 2005 20.29, Erik Huelsmann wrote:
> Hi Jostein,
> > I actually want more freedom when we talk about the installer or
> > maybe packages tree could have it's own repo or tree?
> From the thread it's obvious you have frustrations with the current
> scheme. I don't want to make assumptions about what they could be, so:
> could you tell us what problems you experience with the current scheme
> and which extra degrees of freedom you think you would need to
> aleviate the problem?
> I'm asking not to frustrate you more, but because the frustration you
> show now comes rather unexpected: I thought you were maintaining the
> installer without problems...

I don't know if it's a problem or not. It might be a problem if the trunk
or a tag allways should be in sync with the reality. As mentioned
before, this issue is being smaller and smaller :-) I mentioned that
Branko provided me with pre 1.2.x binaries earlier this year, but forgot
to mention that both you and Ben ("sussman") has been doing a great job,
trying to include the same content in the zipfiles as Branko have done.

However, I have a small example: the libdb42.dll you provided in the rc1
(?) of 1.2 instead of the libdb43.dll. This is not a problem by itself
(at least not for me) and things like that just happends from time to
time, I just changed it accordingly in the Installer and just delivered
the package on the 'net.

The "problem" in this is that the internal setup (scripts etc.) in the
svn-1.2.0-rc1-setup.exe was diffrent than the contents of the
repository's "/tags/1.2.0-rc1/". That tag was made several days before
the delivery of the binaries and svn-1.2.0-rc1-setup.exe.

I have several other examples where I have had to "do what it takes" in
order deliver a working functional installer. This range from unexpected
binary files to bugs introduced by me. I repeat again: this situation is
becoming better and better.

So, the reality is that - some times - the installer code has been
changed minutes before compiling of the setup.

So, it would be nice to let the repository reflect the reality some way.
Maybe a /tags/packages/ which contains for example
svn-1.2.0-rc1-setup.exe and the other packages.

I don't know if I'm frustrated or sad or what it is. I just know that I
feel really very bad about all this mess right now (the branches).

Thanks for caring! :-)



  • application/pgp-signature attachment: stored
Received on Sun May 15 21:52:26 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.