Hey all,
I'm back with another question about patching a package for the Focal
release. My concern is about Boost 1.71, which now ships its own native
CMake config. Previously, FindBoost.cmake was a module supplied by
cmake-data, but now the one from Boost itself takes precedence (as it
should
I've met the problem with ~/profile.d patching and want to suggest a solution. There is a lot of scripts that requires manual patching of the profile file. Some of such tools like go requires manual patching to add GOPATH, others provide scripts for this (like nvm). This is dangerous
On Tuesday, April 19, 2011 06:23:28 AM James Page wrote:
Help/guidance/opinion much appreciated.
Debian has got the same problem since python3.2 is now the default there too.
I would recommend contacting the debian mod-wsgi maintainers and asking their
advice.
Scott K
--
downloaded, similar package to make the download
faster/using less bandwidth. A good patching algorithm isn't trivial
and could include extracting and re-assembling the package on the
client side.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de
On 13/01/2008, Evan [EMAIL PROTECTED] wrote:
Any change in this area is far too complex for a LTS, however for 8.10 we
have the opportunity to be innovative and create a new patching system
better than that being used by the competition:
An interesting discussion of these kinds of changes can
a new patching system
better than that being used by the competition:
An interesting discussion of these kinds of changes can be found here:
https://launchpad.net/ubuntu/+spec/succinct
https://wiki.ubuntu.com/apt-sync (the summary section contains links
to other patching ideas and outlines
