On Wed, 2015-02-18 at 12:49 +0100, Jean Delvare wrote: [...] > rpm-4.12.0.1 > rpm-4.12.0.1/beecrypt-4.1.2 > rpm-4.12.0.1/beecrypt -> beecrypt-4.1.2 > rpm-4.12.0.1/db-4.8.30 > rpm-4.12.0.1/db -> db-4.8.30 [...] > If we can no longer patch files through symbolic links, that means we > have to include the version number in all paths in such patches, and > update the patch whenever the version number changes. That would be a > maintenance pain as you can imagine, which is why we would like to > avoid it.
Or use -p, like this: pushd rpm-$rpm_version/beecrypt-$beecrypt_version # apply beecrypt patches patch -p2 -i ... popd pushd rpm-$rpm_version/db-$db_version # apply db patches patch -p2 -i ... popd Tim. */
signature.asc
Description: This is a digitally signed message part
