|
From: Armin B. <arm...@de...> - 2005-04-08 16:12:48
|
Eduardo Pereira Habkost wrote:
> On Fri, Apr 08, 2005 at 05:15:47PM +0200, Armin Bauer wrote:
> <snip>
>
>>!g_file_test(filename, G_FILE_TEST_IS_REGULAR) || g_file_test(filename,
>>G_FILE_TEST_IS_SYMLINK) || !g_pattern_match_simple("*.so", filename) ||
>>g_pattern_match_simple("*lib.so", filename)
>>
>>the lib.so test is there so we dont load files that end with *lib.so
>>which are library plugins (like the kdepim_sync.so and kdepim_lib.so files)
>
>
> This is exactly what I am arguing about: this implicit rule about file
> names ending with "lib". If the *lib.so files aren't plugins, why are
> they inside the plugins directory?
>
> If it was a more explicit name, like "*_auxfile.so", I wouldn't think it
> was too bad (althought I would still prefer to putting these auxiliary
> files on another directory, as they aren't plugins). But I think that
> "*lib" can be a bit confusing.
>
ok. i really would like to keep them as close to the plugins as possible
and not branch out into yet another directory. but renaming them to a
more meaningfull name is ok for me. any suggestions? (i think auxfile is
not more explicit than lib :)
|