Tiny Core Linux

Tiny Core Extensions => TCE Q&A Forum => Topic started by: TaoTePuh on August 26, 2010, 05:27:11 PM

Title: naming convention (meta extension - gmpc)
Post by: TaoTePuh on August 26, 2010, 05:27:11 PM
I have built gmpc (Gnome Music Player Client) and some plugins (currently 3 - there are at least twice as many).

I would like to offer a meta extension (as the compiletc) which will include all these gmpc extensions.

How should I name it?

gmpc-meta
gmpc-all
gmpc-tc
???
Title: Re: naming convention (meta extension - gmpc)
Post by: Arslan S. on August 26, 2010, 09:17:35 PM
I would say gmpc-full
Title: Re: naming convention (meta extension - gmpc)
Post by: Jason W on August 26, 2010, 09:39:16 PM
Seconded.
Title: Re: naming convention (meta extension - gmpc)
Post by: SamK on August 30, 2010, 04:58:07 AM
Quote from: TaoTePuh on August 26, 2010, 05:27:11 PM
I have built gmpc (Gnome Music Player Client) and some plugins (currently 3 - there are at least twice as many).

I would like to offer a meta extension (as the compiletc) which will include all these gmpc extensions.
This is really good news, I look forward to trying it.  Many thanks.

A question about the use of a meta-package; would this allow the plug-ins to be individually uninstalled via the normal Control Panel method or would this result in the removal of (GMPC).  If the plug-ins cannot be removed individually would you consider producing them as separate extensions?  I realise this is not what you originally intended but it would increase user choice.

Once again many thanks for your efforts.
 
Title: Re: naming convention (meta extension - gmpc)
Post by: TaoTePuh on September 02, 2010, 07:18:50 PM
I have just sent gmpc and its plugins to the maintainer of the repo.

Each plugin has its own extension and can be added (download/install) or deleted as individual.

The extension gmpc-full will download/install gmpc and all its plugins.

You can use gmpc-full to DOWNLOAD all stuff and then delete unneeded plugins manually.

But if you INSTALL gmpc-full, you may not delete any plugins - otherwise you get an error message on loading.
Title: Re: naming convention (meta extension - gmpc)
Post by: Jason W on September 02, 2010, 07:57:39 PM
Great.  I will get to this and the others on Saturday, as I am out of town on very limited bandwidth.
Title: Re: naming convention (meta extension - gmpc)
Post by: SamK on September 03, 2010, 01:41:27 PM
Quote from: TaoTePuh on September 02, 2010, 07:18:50 PM
Each plugin has its own extension and can be added (download/install) or deleted as individual.
Many thanks.
Title: Re: naming convention (meta extension - gmpc)
Post by: SamK on September 10, 2010, 11:53:39 AM
I've just taken GMPC for a trial spin, it works well - congratulations.

When installing gmpc.tcz a plug-in (gmpc-dynamic-playlist.tcz) is also installed by default.  Is this simply an error?  I understood the intention is to have a basic installation to which the user then adds their choice of plug-ins?
 
Title: Re: naming convention (meta extension - gmpc)
Post by: TaoTePuh on September 10, 2010, 02:09:52 PM
Quote from: SamK on September 10, 2010, 11:53:39 AM
When installing gmpc.tcz a plug-in (gmpc-dynamic-playlist.tcz) is also installed by default.  Is this simply an error?  

If so, then it is an error. But if this is so, then gmpc-dynamic-playlist.tcz would have to be a dependency, and it is not:

Code: [Select]
$ cat gmpc.tcz.dep
libmpd.tcz
libsoup.tcz
librsvg.tcz
libglade.tcz
sqlite3.tcz
gdk-pixbuf.tcz
hicolor-icon-theme.tcz
xdg-utils.tcz

I have just tested the following:


and I get the following result:

Code: [Select]
$ ls -1 `cat /opt/.tce_dir`/optional/gmpc*
/mnt/sda3/tce/optional/gmpc.tcz
/mnt/sda3/tce/optional/gmpc.tcz.dep
/mnt/sda3/tce/optional/gmpc.tcz.md5.txt

There is no gmpc-dynamic-playlist.tcz ?
Title: Re: naming convention (meta extension - gmpc)
Post by: SamK on September 10, 2010, 04:12:37 PM
I also have again installed GMPC on a separate Cloud Mode TC3.  Only GMPC was installed not the plug-in.

I cannot explain why it was installed earlier today.  Operator error seems the most plausible explanation, however I am conviced I did not request the download/installation of the plug-in, especially as it was I that requested the ability to install the basic app without plug-ins.

Thanks for your investigation.