Tiny Core Extensions > TCE Talk

metapackages ?

(1/2) > >>

helander:
Other distros supports what some of them call metapackages. A "metapackage" is a package that lists a number of other (real- or meta-) packages and if you install the metapackage all of the listed packages will be intstalled.

To me this could easily be achieved using a .dep file and my question is:

    is it enough with the "metapackagename.dep" file or do I also have to have a "metapackagename.tce" ?

    in the latter case what is the minimal required content of the .tce file ?


Kind Regards

/Lars

Jason W:
We have not made a metaextension yet, but it has been discussed.  It would need at least one file in a .tce, not just a dep file.  Say for instance /usr/local/share/extension.readme.  That way there is a tce to extract.  The deps would have to be real extensions though, as dependency resolution is not recursive.  A GNU type of extension to replace busybox is one such metaextension that may eventually come into being.

helander:
Thank you very much for the info.

Kind Regards

/Lars

tobiaus:
you (that is, anyone that makes extensions) could make one right now though, couldn't you? just make a "tce" with a file, then write the .dep list. nothing modified to the usual system, it will install a file and then download all the "deps." voila metapackage. you could say in the info file: "contains no packages itself, but loads... (a list of the extensions it loads)"

helander:
Yes, I had that in mind. It would be great if TC would support to load extensions recursively based on the .dep files, then the metapackages would be much simpler (not so much to create as to maintain).

/Lars

Navigation

[0] Message Index

[#] Next page