[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: An experimental patching framework...
- To: tech_(_at_)_openbsd_(_dot_)_org
- Subject: Re: An experimental patching framework...
- From: Jacob Meuser <jakemsr_(_at_)_clipper_(_dot_)_net>
- Date: Fri, 27 Jul 2001 01:38:44 -0700
On Fri, Jul 27, 2001 at 04:22:58PM +1000, Ian McWilliam wrote:
> At 3:47 PM +1000 2001/07/27, Adrian Close wrote:
> >> Now matter how this is done, A lot of grunt work will be needed to
> >> initially set up a binary patch just like there is with producing an
> >> initial port.
> >If you're talking about individual patches, I don't agree.
I do. LIB_DEPENDS, RUN_DEPENDS, etc, etc are very important. AFAIK,
no one has really mapped out a dependency tree of the base system.
This is important when libraries get updated, as the instructions
at the top of the fts patch would imply. (I don't see these provisions
in your Makefile.)
What would be keen, would be a way to apply a patch to a codebase,
and have a program/script that would make a Makefile that would rebuild
not only the programs whose sources were changed, but any other program
that also needs to be rebuilt as a result of the patch. A dependency
tree would be nice for this.
As I am interested in a way to create easy to apply patches, and of
course always interested in learning more about OpenBSD ;), I think
my next project will be mapping out the afore mentioned tree. If this
has been done, somebody please stop me from reinventing the wheel. If
this has not been done, I am open to any suggestions on how to accomplish
this or if someone has tried and run into something that made such a
thing 'impossible', I would like to hear that also.
<jakemsr_(_at_)_clipper_(_dot_)_net> -> http://www.jakemsr.com/openbsd/binpat/
PS Since this is not yet a part of OpenBSD, it probably doesn't belong
on tech@, but I could be wrong.
Visit your host, monkey.org