Jeff Johnson wrote:
Oooh, nice & clean.
Could you add to rpmpopt.in on HEAD? I think its time to start
collecting examples of alternative build recipe representations,
the rubyforge YAML is very aesthetically pleasing.
Unfortunately you get indentation errors with non-trivial files.
(could be
On Sep 8, 2008, at 1:00 AM, Alexey Tourbin wrote:
So, right, the best thing you can do is set up nesting limit.
However,
to me, the fact that manifests can include manifests is not the least
surprising thing.
Does that statement mean that nested manifests are the most surprising
thing, o
On Sun, 2008-09-07 at 14:30 -0400, Jeff Johnson wrote:
> On Sep 7, 2008, at 2:19 PM, Alexey Tourbin wrote:
>
> > On Sun, Sep 07, 2008 at 12:10:18PM -0400, Jeff Johnson wrote:
> >> There's a class of infinite recursion problems with manifests used
> >> on the rpm CLI that I don't know to fix.
> >>
On Monday 08 September 2008 00:01:27 Jeff Johnson wrote:
> Yes I hear how hard spec files are to write on a daily basis.
Ok, let me tell you the opposite then. ;)
The main reason why we picked rpm over dpkg or the likes when we
started Ark Linux was that spec files are so much easier to write (a
On Sep 8, 2008, at 1:13 PM, Bernhard Rosenkraenzer wrote:
On Monday 08 September 2008 00:01:27 Jeff Johnson wrote:
Yes I hear how hard spec files are to write on a daily basis.
Ok, let me tell you the opposite then. ;)
;-)
The main reason why we picked rpm over dpkg or the likes when we
In regard to: Re: Converting *.spec to Makefiles, Jeff Johnson said (at...:
make has the advantage that its universal, and one can take a Makefile
and run it.
That's probably true if you're talking about Linux, where every
distribution uses some recent version of GNU Make. It's not as true
wh
