public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: Ignore a dependency
Date: Thu, 15 Sep 2022 11:35:35 +0200	[thread overview]
Message-ID: <20220915113535.03008e10@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO6TE_7xcw1mHuhA0FJwG6vwuwCMmN__jExung5kMXX7gA@mail.gmail.com>

Am Wed, 14 Sep 2022 20:42:25 +0200
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:

> Il Mer 14 Set 2022, 10:34 Henning Schild <henning.schild@siemens.com>
> ha scritto:
> 
> >
> > do_binary_patch[cleandirs] += "${WORKDIR}/blabla-package"
> > do_binary_patch() {
> >         sudo dpkg-deb -R ${WORKDIR}/blabla-package.deb
> > ${WORKDIR}/blabla-package
> >         # do something funny with the control file, i.e. sed -i -e
> > ... Depends
> >         sudo dpkg-deb -b ${WORKDIR}/blabla-package
> > }
> > addtask binary_patch after do_unpack before do_deploy_deb
> >  
> 
> Dear Henning,
> 
> you got the point. I did not twsted yet but it looks promising. In the
> meantime I made may way as explained here below:
> 
> > In brief, it does such a thing:  
> > >
> > > set the resolv.conf
> > > apt update
> > > apt download
> > > dpkg -x
> > > install
> > > rm all
> > >  
> >  
> 
> I am not particularly impressed by this way but for a sigle 3rd party
> package it can be acceptable. Your solution seems much more elegant.
> 
> However, I started to write a class for doing this job and it seems an
> over-engineered solution but it is very good to learn some internal
> about Isar and bitbake. Both are valuable tools, so it is not wasted
> time. I bet thsr your proposed solution will win.

They are powerful and allow all sorts of stuff. But nothing beats
getting in touch with the vendor of the broken package and get your
problem fixed there, so you can eventually drop your hooks.

Henning

> Cheers, R-
> 
> >  


  reply	other threads:[~2022-09-15  9:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 11:55 Roberto A. Foglietta
2022-09-13 12:53 ` Uladzimir Bely
2022-09-13 12:58   ` Roberto A. Foglietta
2022-09-13 13:09     ` Baurzhan Ismagulov
2022-09-13 13:09     ` Uladzimir Bely
2022-09-13 13:53     ` Henning Schild
2022-09-13 18:59       ` Roberto A. Foglietta
2022-09-14  8:34         ` Henning Schild
2022-09-14 18:42           ` Roberto A. Foglietta
2022-09-15  9:35             ` Henning Schild [this message]
2022-10-01 22:14           ` Roberto A. Foglietta
2022-10-01 23:10             ` Roberto A. Foglietta

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=20220915113535.03008e10@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=roberto.foglietta@gmail.com \
    --cc=ubely@ilbers.de \
    /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