[Bug 667] New: <patch> element support for download and uncompression

Neven Has haski at sezampro.yu
Wed Sep 24 12:38:48 PDT 2003

On Wed, Sep 24, 2003 at 12:13:58PM -0700, Kevin P. Fleming wrote:
> >>The other option is to do as James suggested and just have one set of 
> >>source for each handler, and let the handler itself check the version 
> >>and act appropriately. I'm beginning to think that's a better option.
> >
> >Yeah, it solves the naming problem completely and hides the versioning
> >mess from the average user.  And with the use of macros, we can still
> >exclude the parts of the handler.
> That's definitely the direction I'll be going as I rework the build system. 
> However, that means that once the new build system is ready (which will 
> take at least a week), then the CVS nALFS may be unusable until all the 
> handlers get converted to this new style.

Can you post one handler as an example, using that system?  I'm
curious about handler_name, handler_syntax_versions etc. variables and
what you plan to do with them?


More information about the alfs-log mailing list