Re: Install debian packages from other sources

[Henning Schild <henning.schild@siemens.com>]

Am Thu, 19 Apr 2018 11:07:53 +0200
schrieb Francesco <fdprnd@dave.eu>:

> Thanks for the example provided.
> 
> I have now created a custom image file on another layer. Inside this 
> image I set the IMAGE_PREINSTALL variable with other packages I want
> to install on my final target image.
> 
> At the end of the building process I noticed that the version of the 
> packages does not correspond to the version of the packages of my
> added repo, but it is instead that from the original repo.
> 
> I also would like to ask another thing. I tried to write a recipe to 
> install a custom application in .deb format. The deb file is this
> time fetched from the host fs.
> 
> My custom image inherits from the isar-base-image, and I would like
> to simply execute dpkg -i mypackage from the target rootfs. How am I 
> supposed to write a recipe for this?

"dpkg -i" is evil and not supported

The best way to do that is to write a recipe:

foobar_4.1.2.bb

> inherit dpkg-base
> SRC_URI="file://${P}.deb;unpack=false"
> dpkg_runbuild() {
>     true
> }

And put foobar_4.1.2.deb into the FILESDIR of the recipe.
Or use FILESPATH =. "/dir/to/drop/location/" to fetch with file:// from
outside your layer.

Finally add
IMAGE_INSTALL += "foobar"
to your image.

Now the .deb will be put into the isar-apt repository and be installed
with apt-get from that repo.

Henning

> Thanks
> 
> Frank
> 
> 
> On 19/04/2018 09:10, Claudius Heine wrote:
> > Hi,
> >
> > On 2018-04-18 20:26, Henning Schild wrote:  
> >> Hi,
> >>
> >> you can do two things. You can actually go ahead and just
> >> fetch .deb files from somewhere in a package-recipe. Or you could
> >> derive and image-recipe from isar-image-base where you add another
> >> sources.list file to DISTRO_APT_SOURCES.  
> >
> > Yes 'DISTRO_APT_SOURCES' is the right variable, but setting it in
> > an image recipe doesn't do anything. You have to expand it in a
> > *.conf file or in a isar-bootstrap.bbappend file.
> >
> > Personally I would create a new configs like this:
> >
> >   conf/distro/custom.conf:
> >     require conf/distro/debian-stretch.conf
> >     DISTRO_APT_SOURCES += "conf/distro/custom.list"
> >
> >   conf/distro/custom.list:
> >     deb http://url/to/repo suite component
> >
> >   conf/multiconfig/custom-config.conf:
> >     require conf/multiconfig/qemuamd64-stretch.conf
> >     DISTRO = "custom"
> >
> > For just testing you could also put
> > 'DISTRO_APT_SOURCES_append = " conf/distro/custom.list"'
> > in the local.conf, you will also need the custom.list at the right
> > place.
> >
> > Cheers,
> > Claudius
> >  
> >> We still lack an example for that, but Claudius might have one. >
> >> If we are talking about a proper repo and not some random
> >> drop-location for .debs the latter would be the way to go.
> >>
> >> Henning
> >>
> >> Am Wed, 18 Apr 2018 18:12:31 +0200
> >> schrieb Francesco <fdprnd@dave.eu>:
> >>  
> >>> Hello again,
> >>>
> >>> I would like to fetch debian packages from other repositories and
> >>> then install them into the rootfs.
> >>>
> >>> Which is the right way to achieve this?
> >>>
> >>> Thanks
> >>>
> >>> Frank
> >>>
> >>>  
> >>  
> >  
>