Building a metapackage

Building a metapackage

[David Welch]

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

Hi,

Is it possible to build a meta packages whose sole purpose is to bring in
dependencies?

Suppose I have package-1.deb, package-2.deb and package-3.deb.  I would
like add a .bb file to build a metapackage for those three packages.  I
have tried the following but it didn't work:

SUMMARY = "Package"
DESCRIPTION = ""
LICENSE = "CLOSED"
DEPENDS = " \
package-1 package-2 package-3 \
"
inherit meta

My use case is a series of voices by different manufactures which need to
be installed on a per-manufacturer basis.  So all the voices from
manufacture1 would need to be installed on one machine and all the voices
from manufacturer2 need to go on another machine.  There are about 50-100
voice packages per manufacturer.

Thanks,
David

[-- Attachment #2: Type: text/html, Size: 1011 bytes --]

Re: Building a metapackage

[Burton, Ross]

On 14 March 2014 16:34, David Welch <djwelch666@gmail.com> wrote:
> Is it possible to build a meta packages whose sole purpose is to bring in
> dependencies?

You've just described a package group - have a look at anything called
packagegroup-*.bb in oe-core, and packagegroup.bbclass.

Ross

Re: Building a metapackage

[Gary Thomas]

On 2014-03-14 10:34, David Welch wrote:
> Hi,
> 
> Is it possible to build a meta packages whose sole purpose is to bring in dependencies?
> 
> Suppose I have package-1.deb, package-2.deb and package-3.deb.  I would like add a .bb file to build a metapackage for those three packages.  I have tried the following but it
> didn't work:
> 
> SUMMARY = "Package"
> DESCRIPTION = ""
> LICENSE = "CLOSED"
> DEPENDS = " \
> package-1 package-2 package-3 \
> "
> inherit meta
> 
> My use case is a series of voices by different manufactures which need to be installed on a per-manufacturer basis.  So all the voices from manufacture1 would need to be installed
> on one machine and all the voices from manufacturer2 need to go on another machine.  There are about 50-100 voice packages per manufacturer.

I think packagegroups (previously known as tasks) are what you are looking for.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Building a metapackage

[David Welch]

[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]

Thanks for your quick reponses, that works.


On Fri, Mar 14, 2014 at 4:45 PM, Gary Thomas <gary@mlbassoc.com> wrote:

> On 2014-03-14 10:34, David Welch wrote:
> > Hi,
> >
> > Is it possible to build a meta packages whose sole purpose is to bring
> in dependencies?
> >
> > Suppose I have package-1.deb, package-2.deb and package-3.deb.  I would
> like add a .bb file to build a metapackage for those three packages.  I
> have tried the following but it
> > didn't work:
> >
> > SUMMARY = "Package"
> > DESCRIPTION = ""
> > LICENSE = "CLOSED"
> > DEPENDS = " \
> > package-1 package-2 package-3 \
> > "
> > inherit meta
> >
> > My use case is a series of voices by different manufactures which need
> to be installed on a per-manufacturer basis.  So all the voices from
> manufacture1 would need to be installed
> > on one machine and all the voices from manufacturer2 need to go on
> another machine.  There are about 50-100 voice packages per manufacturer.
>
> I think packagegroups (previously known as tasks) are what you are looking
> for.
>
> --
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 2128 bytes --]