On Monday, 2013-09-09, Pali Rohár wrote: > On Monday 09 September 2013 20:52:37 Kevin Krammer wrote: > > On Monday, 2013-09-09, Pali Rohár wrote: > > > On Monday 09 September 2013 20:26:27 Thomas Lübking wrote: > > > > On Montag, 9. September 2013 12:55:47 CEST, Pali Rohár > > wrote: > > > > > And my question is what do you think about searching for > > > > > plugins in "./plugins/" directory (instead ".") and in > > > > > $SOME_ENV_PATH directory? It is acceptable? > > > > > > > > $SOME_ENV_PATH seems reasonable (Qt allows envs to control > > > > plugin paths) and imo completely supersedes "./plugins/" > > > > (ie. that is no more a necessity because you can add it > > > > to the environment) which i would however not add by > > > > default (since including "./*" is usually plain wrong) > > > > > > > > Just my 2¢, though - you still need Jans Ok ;-) > > > > > > Ok, but how to load plugins when trojita is started from > > > build tree, (without installing) if you do not want to > > > include "./" or "./plugins/"? Solution to start trojita > > > with $ENV is not good. > > > > Wouldn't an env variable make this very easy? E.g. something > > like SOME_ENV_VAR=$(pwd)/plugins ./trojita > > And you want to start trojita with writing all these chars (after > compiling and not installed to system - when you want to test)?
Most likely one letter and one arrow press on a developer's shell. And that is for a deverloper without test setup, which, given the importance of elektronic communication data, is highly unlikely for anyone working on an email client, no? Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
