From: John S. <lzr...@gm...> - 2013-02-13 02:50:52
|
Actually, symlinks take up *very* little space. The biggest problem with that, IMO, is that it sticks us with another system that is not friendly to project portability and sharing. On Tue, Feb 12, 2013 at 8:19 PM, Dave Peterson <da...@ki...> wrote: > I'll chime in with a different viewpoint. I do alot of my composition > while traveling so use a netbook with limited disk space. I'd much > prefer not to be forced to install my VSTs in multiple places on my > machine if that could be helped. Why not simply make a config option > for locating the root VST plugin folder and default it to something > within the LMMS install? That way people like me can point it as a > common install location if we want to and we can still use relative > paths when saving in a project? > > -- Dave > > On 2013.02.13 10:28, oeai wrote: > > On 13.02.2013 03:17, Mike Choi wrote: > >> Hi, > >> I think it would be good to agree on a general way how those relative > >> paths should be handled (If this is not done already). I would say its > >> not good idea e.g. to search for VST plugins in more common folders, > >> to avoid version conflicts, but maybe someone has better idea? > >> > >> > > Maybe you can create a vst folder inside main app directory, so all > > needed dll's of common folders will be symlinked to that folder and all > > unusual copies can be found by users in search trees and after user pick > > will be added as symlinks into that folder too? > > > > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > LMMS-devel mailing list > LMM...@li... > https://lists.sourceforge.net/lists/listinfo/lmms-devel > -- Johnny |