Dnia 2014-08-21, o godz. 22:19:38
Michał Górny napisał(a):
> Here is a rebase of my recent work on bringing setup.py install for
> Portage.
This one's committed in the ultimate newest version :).
--
Best regards,
Michał Górny
signature.asc
Description: PGP signature
Dnia 2014-08-24, o godz. 12:42:02
Brian Dolbec napisał(a):
> There is breakage in catalyst runs.
>
> [08:26] has anyone tried mgorny's new portage ebuild? after
> portage is emerged for stage1, it's missing /usr/lib/portage/bin/
> altogether, for me
Well, that directory is no longer used, so
On Thu, 21 Aug 2014 22:19:38 +0200
Michał Górny wrote:
> In particular, tools that want to play with Portage internals need to
> export proper PORTAGE_BIN_PATH and PORTAGE_PYM_PATH before spawning
> them. The correct values can be obtained using portageq:
>
> $ portageq envvar PORTAGE_BIN_PAT
On Thu, 21 Aug 2014 22:19:38 +0200
Michał Górny wrote:
> Hello, everyone.
>
> Here is a rebase of my recent work on bringing setup.py install for
> Portage.
>
>
> About the patches:
>
> (1) teaches the self-update function to deal with PORTAGE_PYM_PATH
> that contains more packages than Porta
Dnia 2014-08-21, o godz. 22:22:30
Michał Górny napisał(a):
> # symlink compatibility /usr/lib/portage/bin
> dosym "${EPYTHON}" /usr/lib/portage/bin
I'm also wondering about removing this. Since the scripts won't work
without setting PORTAGE_PYM_PATH correctly, people can obtain
PORTA
Dnia 2014-08-21, o godz. 22:19:38
Michał Górny napisał(a):
> I will follow this thread with updated ebuild.
And here's the ebuild. You can also find it in ::mgorny.
One minor note: after applying the distutils-r1 patch I submitted to
gentoo-dev@ today, the following diff can be applied to impro
Hello, everyone.
Here is a rebase of my recent work on bringing setup.py install for
Portage.
About the patches:
(1) teaches the self-update function to deal with PORTAGE_PYM_PATH that
contains more packages than Portage itself. In particular, it makes it
copy packages of Portage only rather th
