On Fri, 04 Aug 2006 07:09:38 +0200, Hisham Muhammad <[EMAIL PROTECTED]>
wrote:
On 8/3/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
On Thu, 03 Aug 2006 23:22:10 +0200, Hisham Muhammad
<[EMAIL PROTECTED]>
wrote:
> On 8/3/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> <[EMAIL PROTECTED]>
>> > On 8/3/06, Dan <[EMAIL PROTECTED]> wrote:
>> >> That's a really good question. Unless someone has an objection, I
>> >> also vote for
>> >>
>> >> recipe_type=autoconf
>> >
>> > I don't have a definite vote for this, but I'd be leaning between
>> > autoconf or autotools.
>> >
>> Yes, autotools were among my alternatives but I thought that autoconf
>> were
>> better and beat the former.
>
> Lucas has a good point about non-autoconf configure scripts that are
> currently supported, though. That made me think about using configure
> again.
>
As it's a quite big change in recipe specs I'm not commiting this until
the rest of the Compile tools are considered stable, so we can make a
release quite soon after the commit. This to prevent the new recipe type
to be created by the new tools, before there is a stable release.
Cool. I haven't actually Compile'd a lot these last few days, so I
don't feel very confident this time to make the call about when it's
okay to pack the release. Still, in general the CheckDependencies
addition seems to have gone in fairly smoothly after some tweaks.
Maybe we let Compile stand in CVS for a few more days (while you use
the patched version locally) to see if something shows up and then we
merge and release next week?
Sounds like a good idea.
I've attached a generated patch for the changes I have made, so that you
can review them. I have named the compileprogram type to configure,
while
until we decide on the name.
Looks good. Looking at the patch I only suggest one change:
In RecipeLint, move the if [ ! "$recipe_type" ] test up, right after
source Recipe, and after the WARN, add the 'backwards compatibility
fix' section like in Compile, to avoid "false positive errors" in the
other tests that were changed to use recipe_type instead of is_
variables.
Ok, that's a better way than I did it, where I included the old tests with
the is_ variables.
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
