-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/01/2013 11:25 AM, Sune Vuorela wrote:
>> and so forth. That would be a real breakthrough. It is related to the
>> approach taken by Maven and others. All it takes is a built-in way for CMake
>> to download the find_modules into a cache location and update them when
>> needed, or on request.
>> >
>> > This would also make a lot of things a lot easier. For example, nobody
>> > would need to separately install ECM, and updates to our ECM packages can
>> > be delivered globally by commits to that repo.
> It also makes reproducible builds a lot harder. And our primary source
> of distributing stuff is thru othe people's build servers with no
> internet access.
Not necessarily. The repository interface should essentially front cgit (or
similar), and then the repository would be versioned. So in the example above,
you would use
FIND_MODULES_REPOSITORY("http://ecm.kde.org"; stable)
or
FIND_MODULES_REPOSITORY("http://ecm.kde.org"; floating_always_broken)
and get a tagged, non-changing version of the ECM modules.
As for internet access, I doubt this will be a problem. Almost everybody has
internet access for build machines, at least can selectively configure it. In
the non-C++ world, it is a requirement since ever (see Ruby or Maven, for
example). However, there can be a way to specify a local repo source, or even
to clone a repo and point CMake to that. Not in the sense of making CMake aware
that the findmodules repo has anything to do with git, of course.
Cheers,
Mirko.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJzi/4ACgkQYSSaITCTnKXOWgCfVFlHw77AcMViaZx8MXcF4CF5
hoUAn0ALEr1SsrtEuWIr7h6g0tzuuOb3
=IIHp
-----END PGP SIGNATURE-----
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
