Comments on: Use flags http://mwh.geek.nz/2008/01/19/use-flags/ Wed, 04 Apr 2012 21:27:55 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Jonas http://mwh.geek.nz/2008/01/19/use-flags/comment-page-1/#comment-5 Jonas Wed, 30 Nov -0001 00:00:00 +0000 #comment-5 Never thought of that - that dependencies are included in chroot and almost always autodetected. That would mean that the recipe doesn't need that much (or any at all) changes for most applications. Never thought of that – that dependencies are included in chroot and almost always autodetected. That would mean that the recipe doesn’t need that much (or any at all) changes for most applications.

]]> By: Michael http://mwh.geek.nz/2008/01/19/use-flags/comment-page-1/#comment-6 Michael Wed, 30 Nov -0001 00:00:00 +0000 #comment-6 Yeah, that's what I meant during the meeting when I said merging ChrootCompile in would make flags much easier to implement. Having to specify configure flags to <strong>dis</strong>able functionality would mean a lot more overhead within the recipe as well - I think that was what your objection was back when I brought it up on the list, although I only just realised it now. Anything that <em>can</em> be done automatically I want to have by magic, and as non-redundantly as possible. Most recipes should only need to specify flags once, in Dependencies, and get everything else for free. Yeah, that’s what I meant during the meeting when I said merging ChrootCompile in would make flags much easier to implement.

Having to specify configure flags to disable functionality would mean a lot more overhead within the recipe as well – I think that was what your objection was back when I brought it up on the list, although I only just realised it now.

Anything that can be done automatically I want to have by magic, and as non-redundantly as possible. Most recipes should only need to specify flags once, in Dependencies, and get everything else for free.

]]> By: Anonymous http://mwh.geek.nz/2008/01/19/use-flags/comment-page-1/#comment-7 Anonymous Wed, 30 Nov -0001 00:00:00 +0000 #comment-7 I doubt default flags are going to be required at all to start with. Let them be added with time instead. As of now the dependencies tree acts like a virtual USEFLAG. For example, if you want to remove a dependency, fx esound, you will blacklist that dependency and then tweak compile options (if at all required). I doubt default flags are going to be required at all to start with. Let them be added with time instead.

As of now the dependencies tree acts like a virtual USEFLAG. For example, if you want to remove a dependency, fx esound, you will blacklist that dependency and then tweak compile options (if at all required).

]]>