The JVCL team just changed all their package names. This step was necessary because the current schema was Jv*D?R.bpl for runtime and Jv*D?D.bpl for designtime packages. So every packages had the Delphi version in its name. Nobody really knows why the JVCL didn’t use the $LIBSUFFIX compiler option that was introduced with Delphi 6, but from today on the JVCL packages use $LIBSUFFIX what makes it much easier for others to add JVCL packages as required packages to their packages. No more adjusting the package for every Delphi version is necessary. So much for the background story.
Because I wasn’t the one who did the major work I had to update my local SVN repository. No problem, start TortoiseSVN-Update or “svn update”. Said and done. Well not done yet. The svn update is still working. It is now almost 1 hour ago that I started the update and still no end in sight. What is subversion doing? Just for fun I started “git svn fetch” on my JVCL-git directory that I created last year / last week. And guess what. Git has done the job in little more than 1 minute. Oh, by the way, svn update is still running. It is now updating Delphi 2007. What means Delphi 2009 and 2010 are yet to come.
UPDATE 2010-06-23: The JVCL hasn’t switched from SVN to GIT. I only needed something to do while “svn update” was working. There was and is no public git repository. And my private git repository is long gone (aka deleted).
This ought to be interesting.
All my experiences with the LibSuffix tab are universally disasterous when trying to support multiple versions of Delphi. The only people I have seen use it at all was delphi itself, and they avoided the problems I ran accorss because they never had to simultaneously support multiple versions of Delphi.
Our DCP files go to Delphi version specific directories. So unless somebody messes with his search paths everything works as expected.
BTW: svn update is still working…
Thank you for switching to a better package management – hope it will be copied by other projects still following Delphi 3 style management.
Maybe Xepol had issue supporting multiple versions (of course one needs separate packages anyway), but I had big issues due to require clauses and run-time package management.
Maybe you are the first who adds JVCL packages to the requires clause 🙂
BTW: SVN has finished after 3 hours. So it is SVN 3:00 vs. GIT 0:01.
SVN is a standard. What is git ? 😉
From wikipedia http://en.wikipedia.org/wiki/Git_%28software%29, HomePage http://git-scm.com/
Git is a free distributed revision control, or software source code management project with an emphasis on being fast. Git was initially designed and developed by Linus Torvalds for Linux kernel development.
Every Git working directory is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server.
E.g. it is like CVS, SVN versioning system, but with decentralized repository.
ChAr
Delphi 5 did not support $LIBSUFFIX – that’s probably the reason, why it was not used before. Although, they could have used it for other versions.
Please note that this is not a SVN problem per se, but rather a problem with the infrastructure at Sourceforge.
The same kind of update on a corporate network here took less than a minute.
I’m not sure why, but SVN support has always been very troublesome at SF. Apparently their infrastructure doesn’t like very large repositories…