On Sat, Jul 8, 2017 at 8:27 PM, Walter Dnes <waltd...@waltdnes.org> wrote: > > Let's say I try to do this as a meta package. So in my overlay I > create a category "meta-set" and a file "meta-set/pmbuild-0.ebuild" > > EAPI=5 > SLOT="0" > KEYWORDS="amd64 x86" > DEPEND=" > >=app-arch/zip-2.3 > >=dev-lang/perl-5.6 > >=dev-lang/python-2.7.3 > >=dev-lang/yasm-1.0.1 > >=dev-libs/glib-2.24 > dev-vcs/git > media-libs/fontconfig > >=media-libs/freetype-2.1.0 > media-libs/mesa > =sys-devel/autoconf-2.13 > sys-devel/gcc > <=x11-libs/gtk+-3.0 > x11-libs/libXt > x11-themes/hicolor-icon-theme" > > Does each entry have to be detailed with configure, install, etc, > stuff, or is this sufficient? >
Setting aside QA stuff like description/etc (which wouldn't matter if you're just doing this in your own overlay) this should work fine. If you install this it would pull in all the other stuff, and then do nothing. If you intend for this stuff to stick around you probably want to put it in RDEPEND, otherwise it will just get cleaned at first opportunity. Ebuilds specify their dependencies, they don't have to replicate the ebuilds of those dependencies. If portage needs to install git it will go read the git ebuild and figure out how to install it. Most of the stuff under /usr/portage/virtual should give you a sense of what can be done. Virtuals are really only different from meta-packages in how they're used, not how they work. It is slightly more cruft than a set, but honestly not a great deal so. -- Rich
