Quote:
Really... in about one year no one would remember this thread. This is something really rare but has the possibility to delete existing files from other packages. Just because of that i would welcome something like a warning... i would simply check if LINKGOESIN/LINKNAMEIS does exist in the package while creating the doinst.sh script. If not something went wrong. Just a reminder to the developers. Then they can decide what to do. This would not break anything... My scripts will simply throw out a warning for now so i don't get hit by that anymore, no matter how the developers or makepkg will handle that in the future. |
Quote:
|
Quote:
Quote:
|
Quote:
|
Quote:
Quote:
|
Quote:
Can't see anything in the POSIX spec that suggests that a symlink specified as a command-line parameter should be treated as anything other than a file (whether or not it has a / on the end) and unlink()ed Also, a quick test on my OpenBSD box and it doesn't display this brain-dead behaviour. This seems to be something the GNU guys have dreamed up, but didn't bother documenting. No wonder I was caught by surprise on that one. |
If these kinds of improvements and fixes are something that is being considered, then now might be a good time to introduce them to -current following the recent release of 14.1, so as to give the maximum time to find any issues prior to the next Slackware release.
|
Quote:
Quote:
For the affected package i solved this issue a while ago by simply not using symlinks at all. This will take some more diskspace but would also speed uppackage handling. Anyway... solved. |
All times are GMT -5. The time now is 03:26 AM. |