FS#9187 - makepkg -p can't read from pipe

Attached to Project: Pacman
Opened by Jáchym Barvínek (kamahl) - Sunday, 13 January 2008, 10:57 GMT
Last edited by Dan McGee (toofishes) - Saturday, 01 November 2008, 01:00 GMT
Task Type Feature Request
Category makepkg
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version 3.3.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
makepkg -p pipe
shows:
==> ERROR: /dev/stdin does not exist.

But it may be sometimes comfortable to paste PKGBUILD to /dev/stdin for example.

Additional info:
makepkg --version
makepkg (pacman) 3.1.0


Steps to reproduce:
e.g.:
makepkg -p /dev/stdin
This task depends upon

Closed by  Dan McGee (toofishes)
Saturday, 01 November 2008, 01:00 GMT
Reason for closing:  Fixed
Additional comments about closing:  http://projects.archlinux.org/?p=pacman. git;a=commitdiff;h=8d33dcb81c464f5e42d83 078472bc509e087dd62
http://projects.archlinux.org/?p=pacman. git;a=commitdiff;h=c4b9991258fb360e0d140 a84efe7803eb633df79
Comment by Dan McGee (toofishes) - Wednesday, 06 February 2008, 02:31 GMT
Well we have a bigger issue here. Does /dev/stdin even exist on your box? I sure don't have it on Arch here, so of course makepkg is going to spit this error.
Comment by Jáchym Barvínek (kamahl) - Wednesday, 06 February 2008, 15:12 GMT
Re: Dan McGee
What!? Sure it exists, since I installed my Arch. I often use it. It's a symlink to /proc/self/fd/0

ls /dev|grep std
stderr
stdin
stdout
Comment by Xavier (shining) - Wednesday, 06 February 2008, 15:29 GMT
I have them here too.
But I don't really get the point of that feature request, and I don't see how it would work.
Comment by Dan McGee (toofishes) - Wednesday, 06 February 2008, 15:51 GMT
Well it begins to work here- if you would like to begin fixing some of the assumptions of makepkg that will come up in this problem, then go right ahead.

$ makepkg -p /proc/self/fd/0 < /var/abs/local/pacman-git/PKGBUILD
==> Determining latest git revision...
-> Version found: 20080206
sed: can't read .//proc/self/fd/0: No such file or directory
Comment by Gavin Bisesi (Daenyth) - Friday, 13 June 2008, 19:50 GMT
That looks like it's trying to find a filename inside $PWD. Perhaps a check is needed to see if the filename is an absolute path? I haven't looked at the code though, so I could be wrong.
Comment by Allan McRae (Allan) - Tuesday, 28 October 2008, 11:07 GMT
My testing indicates that this works fine when using a non-SCM based PKGBUILDs.
Comment by Allan McRae (Allan) - Tuesday, 28 October 2008, 11:37 GMT
And here is the issue. We try updating the pkgver in the PKGBUILD:

sed -i "s/^pkgver=[^ ]*/pkgver=$newpkgver/" ./$BUILDSCRIPT

which of course fails...

Loading...