* Custom python location on target #python
@ 2021-02-22 12:22 felixn1996
2021-02-22 12:56 ` [yocto] " Josef Holzmayr
0 siblings, 1 reply; 5+ messages in thread
From: felixn1996 @ 2021-02-22 12:22 UTC (permalink / raw
To: yocto
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Hello!
I'm new to the Yocto Project. It is my first time posting a Yocto related question. If this is the wrong place, I apologize in advance.
I need to change the python installation location on my target from /usr/bin and /usr/lib to somewhere under /media.
I have searched around online and tried looking in the recipe: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/recipes-devtools/python/python3_3.9.1.bb
But I have not made any progress so far.
Any help would be super appreciated!
Best regards,
Felix
[-- Attachment #2: Type: text/html, Size: 698 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [yocto] Custom python location on target #python
2021-02-22 12:22 Custom python location on target #python felixn1996
@ 2021-02-22 12:56 ` Josef Holzmayr
2021-02-22 13:42 ` felixn1996
[not found] ` <21611.1614000938061206077@lists.yoctoproject.org>
0 siblings, 2 replies; 5+ messages in thread
From: Josef Holzmayr @ 2021-02-22 12:56 UTC (permalink / raw
To: felixn1996; +Cc: Yocto-mailing-list
Howdy!
Am Mo., 22. Feb. 2021 um 13:22 Uhr schrieb <felixn1996@gmail.com>:
> I'm new to the Yocto Project. It is my first time posting a Yocto related question. If this is the wrong place, I apologize in advance.
No problem, welcome on board!
> I need to change the python installation location on my target from /usr/bin and /usr/lib to somewhere under /media.
> I have searched around online and tried looking in the recipe: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/recipes-devtools/python/python3_3.9.1.bb
Whats the reasoning behind this? If its meant to be a work-around for
"my custom software totally wants it in that location", then you're
probably better off fixing your custom software to stick to canonical
paths. If its about partitioning schemes, other techniques might
apply. If its about being able to upgrade/modify python independently
from the system, then you probably want some root-in-root or container
build. But randomly picing a complex package that has system-wide
implications and saying "I want it here, screw the FHS" is not a good
idea usually.
Greetz
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Custom python location on target #python
2021-02-22 12:56 ` [yocto] " Josef Holzmayr
@ 2021-02-22 13:42 ` felixn1996
[not found] ` <21611.1614000938061206077@lists.yoctoproject.org>
1 sibling, 0 replies; 5+ messages in thread
From: felixn1996 @ 2021-02-22 13:42 UTC (permalink / raw
To: yocto
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Mon, Feb 22, 2021 at 04:57 AM, Josef Holzmayr wrote:
>
> Whats the reasoning behind this? If its meant to be a work-around for
> "my custom software totally wants it in that location", then you're
> probably better off fixing your custom software to stick to canonical
> paths. If its about partitioning schemes, other techniques might
> apply. If its about being able to upgrade/modify python independently
> from the system, then you probably want some root-in-root or container
> build. But randomly picing a complex package that has system-wide
> implications and saying "I want it here, screw the FHS" is not a good
> idea usually.
Hi
I am aware that what I am asking for is a bit ugly.
The reason is that I have a small amount of memory at my disposal. I'm working with a setup with two partitions, a root-fs and an overlayed application file system. None of them has enough space for python.
Therefore I want to install it on the eMMC, which has plenty of space.
So instead of /usr which is on the root/app file system, I would install it under /media/<somewhere> on the mounted eMMC.
But maybe there exists a more elegant solution?
Kind regards,
Felix
[-- Attachment #2: Type: text/html, Size: 1405 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Private: Re: [yocto] Custom python location on target #python
[not found] ` <21611.1614000938061206077@lists.yoctoproject.org>
@ 2021-02-22 13:43 ` Josef Holzmayr
2021-02-22 13:58 ` felixn1996
0 siblings, 1 reply; 5+ messages in thread
From: Josef Holzmayr @ 2021-02-22 13:43 UTC (permalink / raw
To: felixn1996, Yocto-mailing-list
(re-adding list as this certainly does not contain sensitive
information - others might add other opinions and hints, as well as my
answer should be available for everyone to find it.)
Am Mo., 22. Feb. 2021 um 14:35 Uhr schrieb <felixn1996@gmail.com>:
>
> On Mon, Feb 22, 2021 at 04:57 AM, Josef Holzmayr wrote:
>
> Whats the reasoning behind this? If its meant to be a work-around for
> "my custom software totally wants it in that location", then you're
> probably better off fixing your custom software to stick to canonical
> paths. If its about partitioning schemes, other techniques might
> apply. If its about being able to upgrade/modify python independently
> from the system, then you probably want some root-in-root or container
> build. But randomly picing a complex package that has system-wide
> implications and saying "I want it here, screw the FHS" is not a good
> idea usually.
>
> Hi
> I am aware that what I am asking for is a bit ugly.
>
> The reason is that I have a small amount of memory at my disposal. I'm working with a setup with two partitions, a root-fs and an overlayed application file system. None of them has enough space for python.
> Therefore I want to install it on the eMMC, which has plenty of space.
> So instead of /usr which is on the root/app file system, I would install it under /media/<somewhere> on the mounted eMMC.
>
> But maybe there exists a more elegant solution?
I personally would probably go with a build-in-build, and put some
form of application rootfs on the emmc - this could either be a simple
chroot or some more advanced form of container. This avoids nasty
breakages and update problems when the filesystems go out of version
sync. Other techniques might also apply depending on your software
rollout process, like an addtional overlay fs, or a pivot-root with
initrd, or.... it depends. But ripping out random packages and
rearranging them at random locations certainly isn't a good idea. It
already hurts when I think of the mount-and-deploy magic one would
need for this to roll out in production.
My $.02
Greetz
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [yocto] Custom python location on target #python
2021-02-22 13:43 ` Private: Re: [yocto] " Josef Holzmayr
@ 2021-02-22 13:58 ` felixn1996
0 siblings, 0 replies; 5+ messages in thread
From: felixn1996 @ 2021-02-22 13:58 UTC (permalink / raw
To: yocto
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Mon, Feb 22, 2021 at 05:44 AM, Josef Holzmayr wrote:
>
> I personally would probably go with a build-in-build, and put some
> form of application rootfs on the emmc - this could either be a simple
> chroot or some more advanced form of container. This avoids nasty
> breakages and update problems when the filesystems go out of version
> sync. Other techniques might also apply depending on your software
> rollout process, like an addtional overlay fs, or a pivot-root with
> initrd, or.... it depends. But ripping out random packages and
> rearranging them at random locations certainly isn't a good idea. It
> already hurts when I think of the mount-and-deploy magic one would
> need for this to roll out in production.
>
> My $.02
Okay, that makes sense!
I'll look for a better solution.
KR,
Felix
[-- Attachment #2: Type: text/html, Size: 903 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-02-22 13:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-02-22 12:22 Custom python location on target #python felixn1996
2021-02-22 12:56 ` [yocto] " Josef Holzmayr
2021-02-22 13:42 ` felixn1996
[not found] ` <21611.1614000938061206077@lists.yoctoproject.org>
2021-02-22 13:43 ` Private: Re: [yocto] " Josef Holzmayr
2021-02-22 13:58 ` felixn1996
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.