llvm-devel / dragonegg new ports

[Bradley Giesbrecht]

On Aug 7, 2011, at 5:24 AM, vincent habchi wrote:

> Grüß Gott Rainer,
> 
>> Having dragonegg-devel installing libraries and dragonegg as a metaport would not match existing ports. Usually foo installs the latest stable version, while foo-devel installs a beta, release candidate or development snapshot.
>> 
>> What would be the plan once dragonegg becomes stable?
> 
> You’re right, the choice was not very clever.
> 
> What about dragonegg-svn for the svn port, and dragonegg-devel for the metaport?

How about:
dragonegg-meta-devel # meta port for dragonegg-devel  and llvm-devel
dragonegg-devel # dragonegg sources from svn


This meta port does not resolve your original issue, that someone can upgrade llvm-devel without upgrading dragonegg-devel.

Use a message (port notes) in the dragonegg-devel port explaining to the user they need to upgrade llvm-devel and dragonegg-devel at the same time.

Dragonegg as a variant of llvm-devel is a more sure way of attaining your desired results.


Regards,
Bradley Giesbrecht (pixilla)