[CMake] open source project for CMake ports?

[Philip Lowman]

On Mon, Feb 16, 2009 at 4:36 PM, Alexander Neundorf <a.neundorf-work at gmx.net
> wrote:

>  > Since many of the dependencies overlap, is there general interest in
> this
> > kind of a thing from the VTK perspective or from others?
> >
> > The goal would be to create an open-source project (hosted probably at a
> > neutral site like SF.net or Google Code) where the ports could be stored,
> > baselined, etc. and then released so that anyone could download whichever
> > are needed and incorporate them into their own projects?  Export/Install
>
>
> You suggest to keep a whole copy of these projects there, not only the
> build
> files, right ?
> A problem is how to keep this current, i.e. they will more or less quickly
> become out-of-date (happened to me with python).


I think the entire release would be CM'd along with the CMakeLists.txt.  One
way to do this would be via a tarball + patch stored within CM (to make
baselining easier).  If this approach was adopted then on a release you
could untar + apply patch and zip it up.

You would have to have volunteers who would subscribe to each project's
announce mailing list and on a release examine the diff for new/old files or
anything of interest and tweak the CMakeLists.txt files.

Honestly, I don't think it would be that much work provided it's done
properly.  Obviously there would have to be criteria for new projects being
added to the repository.  Here are a few ideas (not set in stone by any
means), just random thoughts popping out of my head. =)

1.) The library would need to have a volunteer to rebase it
2.) The library would need to be binary ABI stable or have a volunteer
willing to handle DLL filename versioning
3.) Ideally the library would have little or no dependencies

-- 
Philip Lowman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20090217/f1e8b41a/attachment.htm>