public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Sinan Kaya <okaya@kernel.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [meta-oe][PATCH v4] iproute2: split ip to individual package
Date: Thu, 17 Dec 2020 01:20:44 +0000	[thread overview]
Message-ID: <c3075328cf4d45ecb2ae76bdbeeae4cc@XBOX03.axis.com> (raw)
In-Reply-To: <998de3f5-13a8-6a77-903b-172d4c542309@kernel.org>

> -----Original Message-----
> From: Sinan Kaya <okaya@kernel.org>
> Sent: den 17 december 2020 01:31
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [meta-oe][PATCH v4] iproute2: split ip to
> individual package
> 
> On 12/16/2020 6:19 PM, Peter Kjellerstedt wrote:
> >>
> >> -PACKAGES =+ "\
> >> +IPROUTE2_PACKAGES =+ "\
> >>      ${PN}-devlink \
> >>      ${PN}-genl \
> >>      ${PN}-ifstat \
> >> +    ${PN}-ip \
> >>      ${PN}-lnstat \
> >>      ${PN}-nstat \
> >>      ${PN}-rtacct \
> >> @@ -58,12 +59,16 @@ PACKAGES =+ "\
> >>      ${PN}-tipc \
> >>  "
> >>
> >> +PACKAGE_BEFORE_PN = "${IPROUTE2_PACKAGES}"
> >> +RDEPENDS_${PN} += "${IPROUTE2_PACKAGES}"
> >
> > This breaks backwards compatibility. The iproute2 package today
> > does not bring in all the sub-packages.
> >
> 
> OK, Let me fix this.
> 
> >> +
> >>  FILES_${PN}-tc = "${base_sbindir}/tc* \
> >>                    ${libdir}/tc/*.so"
> >>  FILES_${PN}-lnstat = "${base_sbindir}/lnstat \
> >>                        ${base_sbindir}/ctstat \
> >>                        ${base_sbindir}/rtstat"
> >>  FILES_${PN}-ifstat = "${base_sbindir}/ifstat"
> >> +FILES_${PN}-ip = "${base_sbindir}/ip.${PN} ${sysconfdir}/iproute2"
> >>  FILES_${PN}-genl = "${base_sbindir}/genl"
> >>  FILES_${PN}-rtacct = "${base_sbindir}/rtacct"
> >>  FILES_${PN}-nstat = "${base_sbindir}/nstat"
> >> @@ -71,7 +76,7 @@ FILES_${PN}-ss = "${base_sbindir}/ss"
> >>  FILES_${PN}-tipc = "${base_sbindir}/tipc"
> >>  FILES_${PN}-devlink = "${base_sbindir}/devlink"
> >>
> >> -ALTERNATIVE_${PN} = "ip"
> >> +ALTERNATIVE_${PN}-ip = "ip"
> >>  ALTERNATIVE_TARGET[ip] = "${base_sbindir}/ip.${BPN}"
> >>  ALTERNATIVE_LINK_NAME[ip] = "${base_sbindir}/ip"
> >>  ALTERNATIVE_PRIORITY = "100"
> >> --
> >> 2.17.1
> >
> > If you are this space constrained, I would suggest adding bbappend
> files
> > to your own layer for these recipes instead. That is what we do so we
> can
> > control exactly what files we want or not. E.g., this is what we have
> in
> > our iproute2_%.bbappend:
> >
> > EXTRA_OEMAKE += "SUBDIRS='lib tc ip'"
> >
> > do_install_append() {
> >         # Remove unused files
> >         rm -f ${D}${base_sbindir}/ifcfg
> >         rm -f ${D}${base_sbindir}/rtmon
> >         rm -f ${D}${base_sbindir}/routef
> >         rm -f ${D}${base_sbindir}/routel
> >         rm -f ${D}${base_sbindir}/rtpr
> > }
> >
> > With the above bbappend, the only binary left in the iproute2 package
> is in
> > fact "ip".
> 
> I do something very similar in my bbappend now. On the other hand, we
> have an upstream first principle in the company. I would rather try to
> find an upstream friendly solution that works for everybody without
> breaking existing users before falling back to bbappend route that I
> need to maintain forever.

Well, the problem as I see it is that some of these changes are pretty 
invasive to the recipes. And when most seem fine with them as they are 
(based on the fact that there has not been any push to split any of 
them before AFAIK), the value of these changes are questionable, given 
that more complicated recipes increase the maintenance burden. 

> > //Peter

//Peter


  reply	other threads:[~2020-12-17  1:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 17:50 [meta-oe][PATCH v4] iproute2: split ip to individual package Sinan Kaya
2020-12-16 23:19 ` [OE-core] " Peter Kjellerstedt
2020-12-17  0:30   ` Sinan Kaya
2020-12-17  1:20     ` Peter Kjellerstedt [this message]
2020-12-17  1:58       ` Sinan Kaya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c3075328cf4d45ecb2ae76bdbeeae4cc@XBOX03.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=okaya@kernel.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox