spec draft for cross-compile support in future EAPI (EAPI-5)
On Tue, 19 Jun 2012 23:07:01 +0200
Thomas Sachau <tommy@gentoo.org> wrote:
> Do you prefer having everything hardcoded in PMS or can you accept
> outsourcing bigger code pieces into some sort of eclass (i am thinking
> about some external code base, which can be duplicated by the package
> manager with internal code, but has to be used, if the external eclass
> has a newer version/revision then the duplicated internal code)?
The package manager mustn't require any particular eclass to be
present, and there mustn't be duplication between eclasses and the
package manager.
> I am especially thinking about the setup of the environment and the
> code details for the wrappers for binaries and headers, hardcoding
> those details into PMS makes it hard to change/fix issues later on.
Sounds like you haven't really got a clean design then.
--
Ciaran McCreesh
06-20-2012, 07:40 AM
Luca Barbato
spec draft for cross-compile support in future EAPI (EAPI-5)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/19/2012 08:14 PM, Thomas Sachau wrote:
>> and possibly split RDEPEND/DEPEND to have HDEPEND to list build
>> dependencies that need to be run on host.
>
> What should the difference between DEPEND and HDEPEND be?
Not library but program that have to run. Think about generators.
spec draft for cross-compile support in future EAPI (EAPI-5)
