On Fri, 2007-02-09 at 07:46 -0500, Jason Corley wrote:
Without any pointers to what some issues references how is anyone
supposed to provide useful commentary on this and other patches?
Reverting instead of fixing seems an odd choice.
If I remember correctly perldeps was only turned on briefly
Not really, in JPackage we've phased out PreReq in favor of
Requires(pre) (though we most certainly have not finished that for all
packages). So can Requires(pre) only exist if a %pre scriptlet
exists? Otherwise I don't see the need for yet another namespace
that's been marked as remove for
On 2/9/07, James Olin Oden [EMAIL PROTECTED] wrote:
snip
As I said this is meant as a merge of mostly functional changes, and I
want to look at the underlying methodologies individually, as such major
reworking getOutputFrom was beyond the scope of this patchset. My
prefered approach to
On piątek, 9 lutego 2007, James Olin Oden wrote:
Unfortunately, I do build the world type builds, so I probably was not
seeing the sort problems others were. If anyone did have a build
system that was doing those sort of builds, I would be more than happy
to add fixes to this script.
This
On 2/9/07, Michael Schroeder [EMAIL PROTECTED] wrote:
On Fri, Feb 09, 2007 at 08:11:48AM -0500, Peter Bowen wrote:
PreReq is a hint that can be used to get better package ordering when
you are left with little else. For example:
Package A requires B and C
Package B requires A
Package C
On Fri, 2007-02-09 at 08:43 -0500, James Olin Oden wrote:
snip
As I said this is meant as a merge of mostly functional changes, and I
want to look at the underlying methodologies individually, as such major
reworking getOutputFrom was beyond the scope of this patchset. My
prefered
James Olin wrote:
On 2/9/07, Stanislav Brabec [EMAIL PROTECTED] wrote:
Unfortunately though, I just realized I might be misled, because
there is no way that I know to deal with autogenerated deps in this
way.
You are true, but at least partially it is possible.
Yes, it is a overkill,
On Fri, 2007-02-09 at 15:23 +0100, Stanislav Brabec wrote:
So I guess, that %configure should set HOST_CFLAGS and HOST_CXXFLAGS,
too.
It can be defined to the same values as CFLAGS resp. CXXFLAGS, or
better, rpm should discriminate between build and target optflags.
For compatibility,
On Fri, 2007-02-09 at 14:51 +0100, Stanislav Brabec wrote:
And finally, why %preuntrans and %postuntrans don't exist at all?
There is no such thing as an untransaction, we don't do different types
of transaction, merely a transaction that contains different operations
on packages. Imagine a
Paul Nasrat wrote:
On Fri, 2007-02-09 at 14:51 +0100, Stanislav Brabec wrote:
And finally, why %preuntrans and %postuntrans don't exist at all?
There is no such thing as an untransaction, we don't do different types
of transaction, merely a transaction that contains different operations
10 matches
Mail list logo
