I already tried this solution, but the line :
delete ${destroot}${prefix}/share/info/dir
is not in the portfile. There is a loop, which deletes a bunch of files and directories. They seem to be created dynamically. So when i remove the line, nothing is deleted anymore. It seems that you have to insert a delete command, which ignores errors. 2007/8/15, Ryan Schmidt <ryandesign@macports.org>:
On Aug 14, 2007, at 10:59, Thomas Schober wrote:
2007/8/14, Thomas Schober:
2007/8/14, Ryan Schmidt:
On Aug 14, 2007, at 02:57, Thomas Schober wrote:
2007/8/14, Ryan Schmidt:
On Aug 14, 2007, at 02:25, Thomas Schober wrote:
> 2007/8/14, Ryan Schmidt: > >> On Aug 14, 2007, at 01:41, Thomas Schober wrote: >> >>> # $Id: Portfile 22478 2007-03-02 05:16:40Z >>> pipping@macports.org $ >>> >>> PortSystem 1.0 >>> name readline-5 >>> set shortname readline >>> version 5.0.005 >> >> [snip] >> >> Oh. Your readline port is very out of date. Probably all your >> other >> ports are too. You need to get into the habit of running >> "sudo port >> sync" before you begin installing ports on a given day, to >> pull the >> new port definitions from our server. readline is currently at >> version 5.2.001, not 5.0.005. Sync, then try installing readline >> again. Presumably this problem has already been fixed. Also >> run "port >> outdated" to see what other ports you may need to update now. >> Also do >> "sudo port selfupdate" occasionally to make sure you have the >> latest >> version of MacPorts base. > > Ok, i will try this when i am at home today evening. I synced > about > 2 weeks ago and made a selfupdate about 2 weeks ago. Update > Frequency seems to be very high :)
Oh. I'm sorry. I misread. You're not installing readline, you're installing readline-5. readline was updated to 5.2.001 way back on 2007-03-19, but readline-5 is still at 5.0.005.
Why are you installing readline-5 instead of readline? It looks like the only port that depends on readline-5 is ghc, and that only on Mac OS X 10.3.x. But you said you're running 10.4.10. Are you trying to install ghc?
No i am trying to install subversion and readline is a dependency of it. I don't know if i need 5.2, the only thig i did is :
sudo port install readline
I don't really care which version of readline i get. But thats all automatic by MacPorts.
Ah yes, subversion depends on apr-util, which depends on sqlite3, which depends on readline. It does not depend on readline-5, and readline-5 would not satisfy the readline dependency. So we're back to my previous suggestions regarding potential changes to the readline port you could try:
http://lists.macosforge.org/pipermail/macports-users/2007-August/ 005009.html
The Problem is, that this line :
delete ${destroot}${prefix}/share/info/dir
is not in the portfile. there is a generall line inside, which goes over all /share/info/*.
I tried to delete this line, but the same problem as before.
Either you are looking at the wrong portfile, or your portfiles are months out of date. The relevant line has been that way since February 2007, as per this changeset:
http://trac.macosforge.org/projects/macports/changeset/22017
This is the file we're talking about:
http://trac.macosforge.org/projects/macports/browser/trunk/dports/ devel/readline/Portfile?rev=26187
It is located at the path devel/readline/Portfile within your ports tree.
Line 41.
What is the first line of your readline portfile -- what is the output of this command?
port file readline | xargs head -n 1
On my system, it is as follows:
# $Id: Portfile 26187 2007-06-15 10:36:51Z ryandesign@macports.org $
And this is what you should see, too, if your ports tree is up to date.
ok, i fixed the problem:
i just created
/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel _readline/work/destroot/opt/local/share/info/dir
this directory was missing
It sounds like you worked around the problem, rather than fixing it. You may have succeeded in installing the port today, but if you ever need to reinstall it, I see no reason why the same problem would not occur again. It would be beneficial to discover why the problem occurred in the first place. Maybe a change needs to be made to the portfile. We won't know until someone who's experiencing the problem (you) tries out the changes suggested above to see if they help or not.
Another possibility would be to explicitly write the code so that the file is only deleted if it exists, similar to this:
http://trac.macosforge.org/projects/macports/changeset/27782