Hi all,
I have recognized an issue with dependencies in DevPaks. That being that
there should be a "provides" system, such that a package can provide
several (semi-colon separated?) services. And then the dependency
requirements for a package can be met by any other package that
"provides it", rather than the one "named" that.
The problems with going by name are evident with large multi-dependency
systems such as the ones I've created (see below) where they will ONLY
work with my DevPaks or other DevPaks named the same way as mine. This
is not good.
I've created DevPaks for the OpenSceneGraph system. They are my first
working attempt at it, so any feedback on their construction would be
welcome.
get them from:
http://www.fit.qut.edu.au/~streit/OSG/
--
Alexander Streit
PhD Candidate
Media R&D Group
Centre for IT Innovation
Queensland University of Technology
|