My 2p, 1. Compilers and related files are usually system and not user based.
2. Yes. Newer is often better, so I'd assume that the reason for side by side installation is to retain old behaviour for specific projects. That could include dependency on past bindings, good or bad. Regards, Michael On 27 Aug 2011, at 17:10, Carl <[email protected]> wrote: > Hello, > > I'm working on releasing vala 0.13.3 (plus other improvements :) for Windows > and I'm facing an issue with side by side execution. > > I have to test many flavors of minor releases (0.13.1, 0.13.2, 0.13.3) and > all have the vapi files installed in the vala-0.14 folder of a user > directory (well for Windows it's C:\Documents and Settings\All > Users\Application Data\vala-0.14). > > The folder being named after the major version (and not the complete version > ie 0.13.3) , the vapis get overwritten each time I install a new release of > Vala. > To the point I'm no sure which vapi files I run :) > So I can't have 0.13.1 and 0.13.3 running by side by side because the two > releases share the same vapi files. > > Am I the only one experiencing this ? > > Regarding this matter, I have two questions : > > 1) Are the vapi meant to be located in a user related folder ? They didn't > strike me as being configuration, nor personal to the user. Am I missing > something ? > > 2) Couldn't we enable side by side execution for minor releases (for > example, by naming the vapi folder "vala-0.13.3" instead of "vala-0-14", or > by having it in the application folder, not shared in the user folder) ? > What do you think about it ? > > Cheers, > Carl > _______________________________________________ > vala-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/vala-list _______________________________________________ vala-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/vala-list
