From: "Michał Górny" <mgorny@gentoo.org>
To: Brian Dolbec <dolsen@gentoo.org>
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCHES] setup.py install for Portage
Date: Sun, 24 Aug 2014 23:19:36 +0200 [thread overview]
Message-ID: <20140824231936.74bd0b33@pomiot.lan> (raw)
In-Reply-To: <20140824124202.017bebea.dolsen@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
Dnia 2014-08-24, o godz. 12:42:02
Brian Dolbec <dolsen@gentoo.org> napisał(a):
> There is breakage in catalyst runs.
>
> [08:26] <iamben> 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 it's fine missing as long
as executables are where they're supposed to be ;).
> I did a search thru the catalyst code. It is hard-coded in only 1
> place:
>
> lines 35, 37 in stage1-controller.sh
>
> code snipit:
>
> clean)
> # Clean out man, info and doc files
> rm -rf usr/share/{man,doc,info}/*
> # Zap all .pyc and .pyo files
> find . -iname "*.py[co]" -exec rm -f {} \;
> # Cleanup all .a files except libgcc.a, *_nonshared.a and
> # /usr/lib/portage/bin/*.a
> find . -type f -iname "*.a" | grep -v 'libgcc.a' | \
> grep -v 'nonshared.a' | grep -v '/usr/lib/portage/bin/' | \
> grep -v 'libgcc_eh.a' | xargs rm -f
> ;;
>
> *)
>
> Michał can you supply me a patch to fix this in catalyst and I will apply it.
It should be enough to change that path to '/usr/lib/portage/'. Though
it would generally be better to pass additional tests to find rather
than playing with grep...
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next prev parent reply other threads:[~2014-08-24 21:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 20:19 [gentoo-portage-dev] [PATCHES] setup.py install for Portage Michał Górny
2014-08-21 20:19 ` [gentoo-portage-dev] [PATCH 1/6] self-update: Copy only relevant packages from PORTAGE_PYM_PATH Michał Górny
2014-08-22 21:47 ` Brian Dolbec
2014-08-21 20:19 ` [gentoo-portage-dev] [PATCH 2/6] portage.const: Make PORTAGE_PYM_PATH point to the real package tree Michał Górny
2014-08-21 20:19 ` [gentoo-portage-dev] [PATCH 3/6] tests: Append .py to files that need to be installed Michał Górny
2014-08-21 20:19 ` [gentoo-portage-dev] [PATCH 4/6] tests: Fix running on installed copy of Portage Michał Górny
2014-08-22 22:19 ` Brian Dolbec
2014-08-22 22:52 ` Michał Górny
2014-08-21 20:19 ` [gentoo-portage-dev] [PATCH 5/6] Install Python modules using setup.py Michał Górny
2014-08-22 22:30 ` Brian Dolbec
2014-08-22 22:55 ` Michał Górny
2014-08-23 20:30 ` [gentoo-portage-dev] [PATCH v2] Install Portage " Michał Górny
2014-08-23 21:56 ` Brian Dolbec
2014-08-29 17:08 ` Brian Dolbec
2014-08-29 23:30 ` Brian Dolbec
2014-09-05 6:58 ` [gentoo-portage-dev] [PATCH v3] " Michał Górny
2014-08-21 20:19 ` [gentoo-portage-dev] [PATCH 6/6] travis: Use setup.py for running tests Michał Górny
2014-08-21 20:22 ` [gentoo-portage-dev] [PATCHES] setup.py install for Portage Michał Górny
2014-08-21 20:25 ` Michał Górny
2014-08-22 22:32 ` Brian Dolbec
2014-08-24 19:42 ` Brian Dolbec
2014-08-24 21:19 ` Michał Górny [this message]
2014-09-12 7:17 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140824231936.74bd0b33@pomiot.lan \
--to=mgorny@gentoo.org \
--cc=dolsen@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox