On Sat, 27 Dec 2008, Damien Miller wrote: > Hi, > > This (large) diff updates and garbage collects all three Python > ports: > > 2.4.4 => 2.4.8 > 2.5.2 => 2.5.4 > 2.6 => 2.6.1 > > Python 2.4 and 2.5 lose their build knobs to match 2.6. > > Removes no longer needed Python 2.5 security patches backported > from the release25-maint SVN branch. > > Remove the -bz2 subpackage from all three versions. It is silly > to make a subpackage to avoid depending on something tiny and > compatibly licensed. > > Python 2.4 loses its -expat subpackage; expat has been in base for > some time. > > Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, > compatibly licensed and is depended upon by more and more > applications. This brings it into line with the 2.6 version. > > Rework all three version's handling of setup.py. Rather than regex > replacing LOCALBASE and X11BASE into setup.py post-configure, these > are passed in though environment variables. Will save hours of > frustrated cursing familiar to anyone who has accidently used the > update-patches target after configure and had to go back and redo > all the substitutions. > > Rework the patching of setup.py for 2.4 and 2.5 to be more like > what we do for 2.6. I.e. keep the diff minimal and avoid deleting > huge blocks of code, so the diff has a chance of applying without > massive hand-editing each patch release. > > I'll commit this in a couple of days unless there are objections. > There is a separate diff (coming shortly) to remove dependencies > from other ports on python-expat, python-bz2 and python-sqlite
Shouldn't the removed subpackages need a @conflict marker to be added to the PLISTs? -- Antoine
