On Mon, Sep 8, 2008 at 1:56 PM, Vaeth <[EMAIL PROTECTED]> wrote: > Santiago M. Mola wrote: >> Vaeth <[EMAIL PROTECTED]> wrote: >> > >> > [...] The suggestion violates in an extreme way the golden design >> > rule that small changes in effect should require small changes in source. > [...] > >> Yes, you're right. That would be really tedious and stupid... but >> we're lucky, and EAPI-2 introduced the 'default' function. So if you >> need to do a small change not covered by this method, you just define >> the phase, make the little change, and then call the 'default' >> function. Clean and simple. > > How does this "little change" look like if you have to call ./autogen.sh > instead of ./configure?
Most of the time you don't call autogen.sh, but eautoreconf. And when you have to call ./autogen.sh you usually do it in src_unpack (or src_prepare if it's introduced in EAPI-2). > Or if you want to call a second ./configure > in some subdirectory with the same options but one option changed? This is not a "small change" that happens on any package too often (if ever). For such cases you can define a custom src_configure/src_compile which fits your needs. > > These are just some examples, I hope that the point becomes clear: > You simply cannot cover all natural modifications which might be > necessary unless you really can access the commands themselves; You can access the commands themselves,I think no one said ever in this thread that use_with, use_enable or econf are going to be deprecated. Regards, -- Santiago M. Mola Jabber ID: [EMAIL PROTECTED]
