Hallo! * J�rg Schaible <[EMAIL PROTECTED]> wrote: > Well this seems easy: When emergeing a plugin just generate a such a link > file for every installed version or if Eclipse is emerged, create one for > each already installed one.
Hm, still can't see the usecase for this: If it is the same PAI version (say 2.1.x), then I don't want to have 2.1.1 and 2.1.2 instaleld together. If not, then one of this will break. But thats teh case on debian, as I think that mostly a app is only available in one version, replacing a lower version. > Well I have. Some (newer) plugins work already (and only) with 3.x and some > won't at all. Additionally I try a new Milestone forst, before it gets my > default one. And if you get used to the new features of 3.x, you'll miss'em > immediately if you have to use the old 2.1.x because of some plugins ... True. Unformtunatelly the big API breakage chnages were made so late and now I have my exams coming up and won't really be able to repackage eclipse (want to have them in different source packages, build from CVS and with a different build system. debian... ) and so it will take some more time, until I touch the 3.0 packaging. > Yes, but it is the same for every application platform: We should already > handle EARs and WARs in a similar way. Looking at PHP, we have already a > lot of them supported in portage. And did I mension mono applications ... > ok, don't handle too much problems at the same time ;-) Do you actually have such 'applications' available as packages? I think there are no such packages in debian (but debian-java is anyway pretty small compared to jpackage or teh rest of debian) Jan -- [EMAIL PROTECTED] mailing list
