different ebuild version same download package name?

[Thiemo]

Hi,

I am building an ebuild for Aqua Data Studio ( http://www.aquafold.com ) for two versions, 2.0.7 and 3.0. This, because 2.0.7 is free for any use, 3.0 only for personal and educational. My problem is, that the download package name of both is exactly the same such that someone who installed or downloaded one version cannot install the other one because in /usr/portage/distfiles is already a package with the correct name but of the wrong version. At least portage doesn't install it as the md5 number isn't correct.

Does anybody know how to work around this, but to provide the package on an own server?

Cheers,

Thiemo
_________________
root ist die wurzel allen uebels

[Pythonhead]

I can't see any way around this. But, how much of a problem is it unless someone tries to install the free and commercial version?

You could just put an 'einfo' line in the pkg_postinst function that warns them they'll have to delete (or rename) if they are switching versions.

[Thiemo]

I thought of this, but who's gonig to read this einfo? I know, at least I had provided the necessairy information. I'd prefer to rely on this solution as last resort.

BTW, I would have to provide the md5 sum for both versions with a trick. I guess that wouldn't be a great deal.

I might ask the folks at aquafold to change their package name.

Cheers,

Thiemo
_________________
root ist die wurzel allen uebels