Was a decision ever made about the JSR1.4 package? It still requires you
to download the source yourself and toss it into /sw/src. Judging from
the comments, this is against policy. Does the package submission need to
be rejected or is there still some grey area about it?
Daniel
--
"The most
On Jan 28, 2005, at 1:31 AM, Daniel Macks wrote:
If we ever rework our patchfile system, we could give
percent-expansions to the filenames and then only define those % keys
if the file actually existed.
Yes, we ought to do that. As an ugly hack in the meantime, why not read
STDERR and look for the
I'm not able to compile this package and can't figure out why.
Can you point me in the right direction?
I've included fink's output below.
tia,
Tony Donley
--
Package manager version: 0.23.5
Distribution version: 0.7.1.rsync
Mac OS X version: 10.3.7
December 2001 Developer Tools
gcc version: 3.
Tony Donley wrote:
I'm not able to compile this package and can't figure out why.
Can you point me in the right direction?
Have a look at the same thread from 2 months ago:
http://sourceforge.net/mailarchive/message.php?msg_id=10059196
--
Martin
Dave Vasilevsky wrote:
Yes, we ought to do that. As an ugly hack in the meantime, why not read
STDERR and look for the string '.patch: No such file or directory' ?
An easier hack would be to feed STDERR to patch. It will choke when
there is an error:
sed 's|@PREFIX@|%p|g' %a/%n.patch 2>&1 | pa
