Hi
We are not changing the default behavior of Yocto but are instead using our
own custom class to handle IPK.
Since create_packages_dir is a function in rootfs.py, it would be
beneficial to add an option allowing users to select either the deploy
directory or oe-rootfs-repo. This would also save the copy time to
oe-rootfs when it is not required for their projects.
Currently, in create_packages_dir, the option to check whether to create
"oe-rootfs-repo" or use a symlink from "DEPLOY_DIR_IPK" to "oe-rootfs-repo"
is ineffective with filterbydependencies, as it is always set to True. Our
request is to add a configuration option for this behavior; otherwise, this
check serves no purpose when used with filterbydependencies.
if nodeps or not filterbydependencies:
for arch in d.getVar("ALL_MULTILIB_PACKAGE_ARCHS").split() +
d.getVar("ALL_MULTILIB_PACKAGE_ARCHS").replace("-", "_").split():
target = os.path.join(deploydir + "/" + arch)
if os.path.exists(target):
oe.path.symlink(target, subrepo_dir + "/" + arch, True)
return
This patch does not change the existing functionality. By default, it is
set to True (consistent with default Yocto behavior), but users can adjust
it as needed.
Thanks
Sreejith
On Mon, Oct 28, 2024 at 6:52 PM Alexander Kanavin <[email protected]>
wrote:
> On Fri, 25 Oct 2024 at 20:19, Sreejith Ravi <[email protected]>
> wrote:
> > We aim to use released IPK files from a previous release build instead
> of building from source. During package processing, we skip all build tasks
> for the package and copy it to the deploy directory, adjusting the feeds
> accordingly. With a customized opkg configuration, we can set the feeds
> either from a remote server or the deploy directory. Since we are using the
> released IPK files, there is no need to filter by dependencies, as this has
> already been handled during the release of the IPK.
> >
> > This patch provides an additional option to use the deploy directory as
> an IPK repository. By default, this option is disabled but can be enabled
> if needed.
>
> Unfortunately I am strongly against supporting this use case in
> openembedded core, and I think many will agree. OE's main feature is
> end to end builds from source that are also reproducible. Sstate is
> the way to rebuild only what's needed, and you need to further explain
> why it isn't being used instead. All code in rootfs creation assumes
> that packages used to compose an image are produced through the
> regular build process or come from sstate, and not imported from
> elsewhere.
>
> If you must do things differently then you need to implement your own
> set of classes (perhaps subclassing what's there), and set
> PACKAGES_CLASSES = "package_prebuilt_ipk" or similar.
>
> Alex
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#206941):
https://lists.openembedded.org/g/openembedded-core/message/206941
Mute This Topic: https://lists.openembedded.org/mt/109210754/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
