Date: Tue, 7 Jun 2005 12:50:13 -0700 From: "Loren M. Lang" <lorenl@alzatex.com> To: freebsd-ports@freebsd.org Subject: Breaking up a monolithic patch Message-ID: <20050607195013.GA26626@alzatex.com>
next in thread | raw e-mail | index | archive | help
I have been working on porting Cinelerra to freebsd and I currently have one large monolithic patch that will make cinelerra compile and run on freebsd. Now I am trying to figure out how to break it up. It looks like the simplest method would be to break it up for each file that's modified, then I could use the existing update-patches framework to maintain it. But I think the better solution would be to break it up functionally, though it's harder to maintain. I could make a series of patches to be applied in order, where one patch would modify cinelerra to have a customizable prefix, another would disable the linux firewire support. This approach would make several patches that will overlap some and touch some of the same files, but it would be more useful in the long run. It would be easy to see what was modified to disable firewire and figure out how to update it to use the freebsd firewire support instead of disabling it. If I do this though, I'll probably need to spend some time making a script to help generate the patches appropriately. -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050607195013.GA26626>