-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This check was added to epatch all of a sudden breaking all working patches in the tree, although defending those patches having absolute paths, we as Java team had several bugs filed due to that. Maybe the tree should be scanned for those and fixed.
Diego 'Flameeyes' Pettenò yazmış: > I ask it here as a favour, please avoid using absolute paths in the > filenames of patched files. This mean avoid having stuff like > > --- foobar/foo.c > +++ /tmp/foobar/foobar.c > > This tends to break from time to time, and I had to fix at least three > packages since I started my treewide build for these problems. I already > asked Zac about adding such a check on repoman, but in the mean time I'd > like to ask here for people to verify their packages. > > I actually am culprit of doing this some time ago but I learnt my lesson > the hard way :P My suggestion for everybody else is to use quilt when > you need to write patches. > > And if you have patches with the filenames like I shown above, you can > change it the git way so that it becomes: > > --- a/foobar/foo.c > +++ b/foobar/foo.c > > and the problem is usually solved. > > Thanks, - -- Sincerely, Serkan KABA Gentoo/Java -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkhxhgACgkQRh6X64ivZaK4wwCeIUCZ6BIqWvo7tiFXpXa+Njpe AL4An2E5N+yGaIfv1kPaV4Gc9W8DG3M3 =2nhY -----END PGP SIGNATURE-----
