On Tue, 2010-06-08 at 18:32 +0200, Pierre Schmitz wrote:
On Tue, 08 Jun 2010 17:43:47 +1000, Allan McRae <allan@archlinux.org> wrote:
$startdir will not be removed. The error printed for $startdir usage was always there so I did not change that. For install files, once 3.4 is released, you can put them in the source array without any issues and
then adjust them in $srcdir.
This patch was mainly to check for $startdir/pkg which will not be the same as $pkgdir from 3.5 onwards (i.e. two releases away). This is already true for split packages, but will become true for unsplit ones too. A lot of packages are affected but we have been telling people not to use $startdir/pkg for more that a year, maybe even two years...
No problem then. Maybe we could "sed" all $startdir/{pkg,src} usage in trunk for the remaining packages. This way startdir will be gone sooner or later.
Is this same advise applicable to AUR PKGBUILDs? If I read it correctly, $startdir/pkg is wrong, $pkgdir is correct, and $startdir is correct.