syck-python vs. python-syck?

[Nicolas Mailhot]

Le Ven 10 mars 2006 10:43, Paul Howarth a écrit :

> Isn't the rule of thumb for this that applications use their own names
> regardless of language, but supporting libraries/modules use their own
> namespace?

It's not as clear cut as this.

Perl is a very bad example because most perl modules are released at CPAN
and follow cpan-conventions. At one point packagers started using perl-foo
as a synonym for cpan-foo. It's ok you know perl- means part of cpan most
of the times.

Other langages like java are a lot less centralised. You don't have one
project in charge of FOSS java. You can pretend there is unity by slapping
a single namespace on packages but truth is there are more common
conventions between a C++ and java package released by the same apache
subproject than between an apache java package and one released by some
other java player.

(Sun is the only entity which had a chance of uniting java, they botched
it by being greedy and alienating parters to various degrees - as
evidenced by Eclipse success. The FOSS java field is still recomposing
around Jakarta, Eclipse, Harmony and other centers of gravity)

You'll note that while Gnome and KDE are both built around C/C++/gcc their
components do not share a common namespace either.

Regards,

-- 
Nicolas Mailhot