Re: virtualenv and make DESTDIR=

2022-03-06 Thread Barry
> On 6 Mar 2022, at 16:53, Peter J. Holzer wrote: > > On 2022-03-05 17:59:48 +0100, Marco Sulla wrote: >>> On Sat, 5 Mar 2022 at 17:36, Barry Scott wrote: >>> Note: you usually cannot use pip when building an RPM with mock as the >>> network is disabled inside the build for >>> security reas

Re: virtualenv and make DESTDIR=

2022-03-06 Thread Peter J. Holzer
On 2022-03-05 17:59:48 +0100, Marco Sulla wrote: > On Sat, 5 Mar 2022 at 17:36, Barry Scott wrote: > > Note: you usually cannot use pip when building an RPM with mock as the > > network is disabled inside the build for > > security reasons. > > Can't he previously download the packages and run p

Re: virtualenv and make DESTDIR=

2022-03-06 Thread Barry Scott
> On 5 Mar 2022, at 19:56, Hartmut Goebel wrote: > > Am 05.03.22 um 17:34 schrieb Barry Scott: >> Have the RPM install all the pythone code and dependencies and also install >> a short script that >> sets up PYTHONPATH, LD_LIBRARY_PATH, etc and execs the python3 .py. > The scripts are already

Re: virtualenv and make DESTDIR=

2022-03-05 Thread Barry Scott
> On 5 Mar 2022, at 19:56, Hartmut Goebel wrote: > > Am 05.03.22 um 17:34 schrieb Barry Scott: >> Have the RPM install all the pythone code and dependencies and also install >> a short script that >> sets up PYTHONPATH, LD_LIBRARY_PATH, etc and execs the python3 .py. > The scripts are already

Re: virtualenv and make DESTDIR=

2022-03-05 Thread Barry Scott
> On 5 Mar 2022, at 19:56, Hartmut Goebel wrote: > > Am 05.03.22 um 17:34 schrieb Barry Scott: >> Have the RPM install all the pythone code and dependencies and also install >> a short script that >> sets up PYTHONPATH, LD_LIBRARY_PATH, etc and execs the python3 .py. > The scripts are already

Re: virtualenv and make DESTDIR=

2022-03-05 Thread Hartmut Goebel
Am 05.03.22 um 17:34 schrieb Barry Scott: Have the RPM install all the pythone code and dependencies and also install a short script that sets up PYTHONPATH, LD_LIBRARY_PATH, etc and execs the python3 .py. The scripts are already created by entry-points. So basically this means to reinvent th

Re: virtualenv and make DESTDIR=

2022-03-05 Thread Kirill Ratkin
Hi, As far I know there is tool rpmvenv (https://github.com/kevinconway/rpmvenv). Try it, maybe ot helps. 04.03.2022 16:03, Hartmut Goebel wrote: Hi, How can I make installing a virtual environment honor DESTDIR? How can I install a virtual environment in $(DESTDIR)$(PREFIX), which behaves

Re: virtualenv and make DESTDIR=

2022-03-05 Thread Barry Scott
> On 5 Mar 2022, at 16:59, Marco Sulla wrote: > > On Sat, 5 Mar 2022 at 17:36, Barry Scott wrote: >> Note: you usually cannot use pip when building an RPM with mock as the >> network is disabled inside the build for >> security reasons. > > Can't he previously download the packages and run

Re: virtualenv and make DESTDIR=

2022-03-05 Thread Marco Sulla
On Sat, 5 Mar 2022 at 17:36, Barry Scott wrote: > Note: you usually cannot use pip when building an RPM with mock as the > network is disabled inside the build for > security reasons. Can't he previously download the packages and run pip on the local packages? -- https://mail.python.org/mailman

Re: virtualenv and make DESTDIR=

2022-03-05 Thread Barry Scott
> On 4 Mar 2022, at 13:03, Hartmut Goebel wrote: > > Hi, > > How can I make installing a virtual environment honor DESTDIR? How can I > install a virtual environment in $(DESTDIR)$(PREFIX), which behaves as being > set-up in $(PREFIX)? (Of course, this virtual environment can not be used. My

virtualenv and make DESTDIR=

2022-03-04 Thread Hartmut Goebel
Hi, How can I make installing a virtual environment honor DESTDIR? How can I install a virtual environment in $(DESTDIR)$(PREFIX), which behaves as being set-up in $(PREFIX)? (Of course, this virtual environment can not be used. My aim is to ship it as part of a rpm package) In Makefiles is