|
From: Eduardo P. H. <eha...@co...> - 2005-04-08 13:41:15
|
On Fri, Apr 08, 2005 at 01:52:07PM +0200, svn...@op... wrote:
<snip>
> =09
> - if (!g_file_test(filename, G_FILE_TEST_IS_REGULAR) || g_file_test(file=
name, G_FILE_TEST_IS_SYMLINK) || g_pattern_match_simple("*lib.la", filename=
) || !g_pattern_match_simple("*.la", filename)) {
> + if (!g_file_test(filename, G_FILE_TEST_IS_REGULAR) || g_file_test(file=
name, G_FILE_TEST_IS_SYMLINK) || g_pattern_match_simple("*lib.la", filename=
) || g_pattern_match_simple("*.la", filename)) {
> g_free(filename);
> continue;
> }
Do we really need this *lib.la stuff? We are using the filename to
separate files and create a new namespace. Isn't it what directories
are supposed to do? If a *lib.la file isn't a plugin, so why is it on
the plugins directory?
It can be confusing: i.e. a developer write a plugin that has the
main feature of using the 'foobarlib' to access the data used by other
software using foobarlib, and calls his plugin: foobarlib. Then it won't
load. (okay, bad example, but the main point is: if the module isn't a
plugin, why is it inside the plugins directory?)
Why not create a directory called 'pluginlib', 'modules', 'lib', or any
other name, for these files?
--=20
Eduardo
|