On Tuesday, December 12, 2023 at 10:38:08 AM UTC+5:30 Jan Kiszka wrote:

On 12.12.23 05:55, Srinuvasan Arjunan wrote: 
> 
> 
> On Friday, December 8, 2023 at 7:45:06 PM UTC+5:30 Jan Kiszka wrote: 
> 
> On 28.11.23 08:14, Srinuvasan Arjunan wrote: 
> > From: Srinuvasan A <srinuv...@siemens.com> 
> > 
> > In present implementation we are using sbuild/schroot to build the 
> > packages, this schroot created via sessions during package build, and 
> > immediatley vanish once build the packages. 
> > 
> > Some of the downstream projects uses this chroot at many 
> > places for doing some postprocessing the meta data based on the 
> chroot 
> > path, but unfortunately we cannot refer this path due to creating the 
> > chroot via session. 
> 
> Can you be more specific in the use cases? 
> 
> 
>    In our case we need to install the custom packages in buildchroot, 
>    once we installed the isar-apt packages, later we refer those and do 
some 
>    postprocessing before image creation. 
> 
> 
>    ISAR provides the provision to pre-install the  upstream packages 
>    not custom packages and this chroot will be used as a base chroot to 
>     build the packages or imager_run, hence SBUILD_FLAVOR would not be 
>    helpful atleast for my scenario. 
> 
> 
>    SBUILD_CHROOT_PREINSTALL_EXTRA variable directly install the upstream  
>    packages in rootfs not custom packages. 
> 

Understood the use case now - but then why not fixing/enhancing the 
existing mechanism? We likely need some SBUILD_CHROOT_INSTALL_EXTRA that 
establishes the recipe dependency, and then a custom sbuild should also 
be able to pull packages from isar-apt. Did you consider this already?


    Hmm, Understood, but so far i didn't tried this method , i meant pull 
isar-apt packages in custom sbuild  (SBUILD_FLAVOR), i hope this
   will work for my scenario,  Let me try one use cases and update the 
patch ASAP.



Jan 

-- 
Siemens AG, Technology 
Linux Expert Center