Re: Re: Idea: embed patch in .info

David R Morrison said:
>> not only a wait to combine them, but the seperate them too for when 
>> maintainers are making the next release.
>
>Sure.  That's what I meant about needing tools.  If we had a little tool
>for developers to use to bundle the .info and .patch file into a text
>archive (maybe with the shar format), and another tool to unbundle them 
>again, we'd be in great shape.  (Presumably fink would use the unbundling 
>tool, too.)

Something like 'fink package' and 'fink unpackage'...? The former would
take a .info and optional .patch (make sure .info passes 'fink validate')
and hang the .patch onto the end of .info after some NoParse token (or
better yet, combine them into some third file but keep the same
.info+"NoParse"+.patch structure so 'fink index' can still process it).  
The latter pulls the two apart and puts them into the current or a
user-specified directory. So if 'fink build' decides that it's using this
combined file, it would run unpackage to put .info/.patch into some temp
space and set %a to this temp spot instead of the finkinfo dir in the
dists tree.

dan

-- 
Daniel Macks
dmacks@xxxxxxxxxxxx
http://www.netspace.org/~dmacks



-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1