On 07:13 Tue 05 Feb , Ciaran McCreesh wrote:
On Mon, 4 Feb 2008 23:05:18 -0800
Donnie Berkholz [EMAIL PROTECTED] wrote:
What happens if the make process changes directories?
In a different process? It's pretty unlikely make will ever become a
shell builtin...
You're absolutely right.
The KDE list was created to be used in a near future for patches and
so on, but the moment is not ripe yet. Once we need it, we'll contact
you or fill in a bug to regain RW access.
Thanks :)
On Feb 4, 2008 11:51 PM, Robin H. Johnson [EMAIL PROTECTED] wrote:
On Mon, Feb 04, 2008 at 02:38:57PM
On Feb 5, 2008 4:21 AM, Ryan Hill [EMAIL PROTECTED] wrote:
Heath N. Caldwell wrote:
On 2008-02-04 14:51, Ryan Hill wrote:
Can someone provide a tool that given a package name simply prints the
category or cat/pkg, or if ambiguous, prints the multiple cat/pkgs or
returns an error code? I
On Tue, 5 Feb 2008 08:43:55 +0100
Christian Faulhammer [EMAIL PROTECTED] wrote:
This will let package managers use a format other than VDB. A well
designed replacement can shave a minute off cold cache command
times.
How much gain can be expected?
There're two common operations that're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
* Modify built_with_use so that it calls native_built_with_use if such
a function exists, and falls back to its own implementation otherwise.
* Allow package managers that implement native_built_with_use to sandbox
off vdb
On Sat, 2008-02-02 at 08:54 +0100, Luca Barbato wrote:
William L. Thomson Jr. wrote:
http://www.gentoo.org/proj/en/java/getting-involved.xml
Maybe could we get it moved on the top level?
Sure, there is some Java specific stuff in there. Likely need to remove
that first, but is a pretty
Zac Medico wrote:
If the package manager exposes a slightly lower level interface to
the USE flags then build_with_use can use that instead, and the
package manager won't have to implement the full build_with_use
interface. For example, portageq currently supports a metadata
command that can be
Ciaran McCreesh kirjoitti:
Incidentally, if anyone is still thinking that built_with_use is
fine... It doesn't handle IUSE defaults, which means package managers
have to store a hacked version of IUSE in VDB for EAPI 1. This isn't
documented anywhere and is highly unobvious.
I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vlastimil Babka wrote:
Zac Medico wrote:
If the package manager exposes a slightly lower level interface to
the USE flags then build_with_use can use that instead, and the
package manager won't have to implement the full build_with_use
interface.