Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: H.Lunke on January 27, 2012, 09:04:00 AM

Title: Extension naming conflict (mpc)
Post by: H.Lunke on January 27, 2012, 09:04:00 AM

Hi,

i'm new to TC, find it very interesting so first of all thanks for all the work..

I plan to use TC on a home pc music server, using the existing MPD (Music Player Daemon) extension. For controlling the server locally i installed MPC just to notice that this is not the "minimalist mpd client" that i expected but a library for complex numbers arithmetics.

So i built an extension "mpc-tc", leaving the binary as "mpc" as it is a dependency for other MPD clients out there. Shall i submit the extension that way, or should the naming be changed somehow?


[edit: added (mpc) to subject line for clarification]

Title: Re: Extension naming conflict
Post by: gerald_clark on January 27, 2012, 10:27:10 AM

This has been discussed before.
http://forum.tinycorelinux.net/index.php/topic,12129.msg64869.html#msg64869 (http://forum.tinycorelinux.net/index.php/topic,12129.msg64869.html#msg64869)

Title: Re: Extension naming conflict
Post by: H.Lunke on January 28, 2012, 11:26:31 AM

So the problem has been heard of, but what is the solution?

Installing mpc from 3.x might lead to problems with installed mpc from 4.x, maybe when it comes to removal/dependency checking of some other component.. am i wrong?

I think the math-thing should be renamed to 'libmpc' and the repository should be updated accordingly.

Title: Re: Extension naming conflict
Post by: Rich on January 28, 2012, 01:44:24 PM

Hi H.Lunke

Quote

I think the math-thing should be renamed to 'libmpc' and the repository should be updated accordingly

Personally I agree. The files in that extension are all named  libmpc  and the extension should be
named likewise. Not to mention that the new name breaks what seems to be a tradition of library
extension names beginning  lib. That said, it's really juanitos choice as it's his extension, though
the  submitqc  would have flagged that as problem had the original  mpc.tcz  already been in the
repository, which it wasn't.

Title: Re: Extension naming conflict
Post by: Juanito on January 28, 2012, 02:52:33 PM

I've always thought an extension should be named after the source package and the source for mpc is named mpc.

Maybe we could name MPC, mpc_music or similar?

Title: Re: Extension naming conflict
Post by: maro on January 29, 2012, 05:52:18 PM

Just to repeat what I wrote only a few weeks ago (http://forum.tinycorelinux.net/index.php/topic,12129.msg64869.html#msg64869): Please do not use case to differentiate extension names!!!

Why was it necessary to change the name of the extension for the library from 'libmpc.tcz' to 'mpc.tcz' (when comparing  the repositories of TC 3.x and 4.x)?? A quick check with a "bloated cousin" (i.e. Ubuntu) shows that they use pretty much the naming as we had in TC 3.x.

I'd therefore like to suggest to go back to the previous use of extension names (and hence change 'mpc.tcz' and 'mpc-dev.tcz' in TC 4.x back to 'libmpc.tcz' and 'libmpc-dev.tcz') to stay consistent with our own history (and broadly in sync which what users might be expecting).

Title: Re: Extension naming conflict
Post by: Rich on January 29, 2012, 08:55:46 PM

Quote

A quick check with a "bloated cousin" (i.e. Ubuntu) shows that they use pretty much the naming as we had in TC 3.x.

Not just Ubuntu
http://www.multiprecision.org/index.php?prog=mpc&page=packages (http://www.multiprecision.org/index.php?prog=mpc&page=packages)

Title: Re: Extension naming conflict (mpc)
Post by: Juanito on February 01, 2012, 03:08:36 AM

I don't agree with it, but mpc renamed libmpc (and mpc-dev renamed libmpc-dev)

Title: Re: Extension naming conflict (mpc)
Post by: Rich on February 01, 2012, 08:54:09 AM

Hi Juanito
Thank you for that, and for all your effort and hard work.

Title: Re: Extension naming conflict (mpc)
Post by: H.Lunke on February 01, 2012, 11:48:51 AM

That's good news, thanks Juanito.
I have asked the maintainers of the 3.x-mpc if they are going to build the current version for 4.x, otherwise i can do.

[edit: mpc V0.21 (and mpc-doc) are now in the 4.x repository]