[pacman-dev] CVS update of pacman-lib/scripts (repo-add)
Date: Tuesday, March 13, 2007 @ 11:01:15 Author: aaron Path: /home/cvs-pacman/pacman-lib/scripts Modified: repo-add (1.5 -> 1.6) * Sebastian Sareyko Fix repo-add filename addition (use basename) ----------+ repo-add | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: pacman-lib/scripts/repo-add diff -u pacman-lib/scripts/repo-add:1.5 pacman-lib/scripts/repo-add:1.6 --- pacman-lib/scripts/repo-add:1.5 Thu Feb 22 20:29:14 2007 +++ pacman-lib/scripts/repo-add Tue Mar 13 11:01:15 2007 @@ -148,7 +148,7 @@ # create desc entry echo ":: creating 'desc' db entry" - echo -e "%FILENAME%\n$1\n" >> desc + echo -e "%FILENAME%\n$(basename $1)\n" >> desc echo -e "%NAME%\n$pkgname\n" >>desc echo -e "%VERSION%\n$pkgver\n" >>desc if [ -n "$pkgdesc" ]; then
On 3/13/07, Aaron Griffin <aaron@archlinux.org> wrote:
Date: Tuesday, March 13, 2007 @ 11:01:15 Author: aaron Path: /home/cvs-pacman/pacman-lib/scripts
Modified: repo-add (1.5 -> 1.6)
* Sebastian Sareyko Fix repo-add filename addition (use basename)
----------+ repo-add | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Index: pacman-lib/scripts/repo-add diff -u pacman-lib/scripts/repo-add:1.5 pacman-lib/scripts/repo-add:1.6 --- pacman-lib/scripts/repo-add:1.5 Thu Feb 22 20:29:14 2007 +++ pacman-lib/scripts/repo-add Tue Mar 13 11:01:15 2007 @@ -148,7 +148,7 @@
# create desc entry echo ":: creating 'desc' db entry" - echo -e "%FILENAME%\n$1\n" >> desc + echo -e "%FILENAME%\n$(basename $1)\n" >> desc echo -e "%NAME%\n$pkgname\n" >>desc echo -e "%VERSION%\n$pkgver\n" >>desc if [ -n "$pkgdesc" ]; then
This fix works as long as we assume that the DB is always located in the same directory as the pkg.tar.gz files, which I believe is the current assumption. We may need to change this behavior later but it works for a 3.0 release. -Dan
On 3/13/07, Dan McGee <dpmcgee@gmail.com> wrote:
This fix works as long as we assume that the DB is always located in the same directory as the pkg.tar.gz files, which I believe is the current assumption. We may need to change this behavior later but it works for a 3.0 release.
Aye, but that's pretty much enforced right now. As it stands, current.db.tar.gz is always at the same directory level as the db.
participants (3)
-
Aaron Griffin
-
Aaron Griffin
-
Dan McGee