| Summary: | kdelibs cvs create sandbox warnings | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Yannick Koehler (RETIRED) <ykoehler> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Yannick Koehler (RETIRED)
2003-06-27 10:55:14 UTC
The cvs ebuilds are not supported Weird... Originally I thought kde/qt stuff only tried to write a .lock file into that dir ($QTDIR/etc/settings) if the dir already existed. Now it tries to create that dir too. Maybe we should create the dir in the qt ebuild? (And then the code in kde.eclass will make that dir sandbox-writeable.) The cvs ebuilds aren't supported (by gentoo), but the kde code will make its way into release stuff. We should prepare beforehand, that's why the cvs ebuilds exist in the first place. What also works if the file is not really needed is addpredict. It is used some times in the openoffice ebuilds, and just disables the error. I forgot to mention that I knew the ebuilds weren't officially supported. I also forgot to mention that I actually did some grep/search stuff to try to figure out why and where this was created without success. I would happily try to understand what's going on, who create those folders (ebuild/makefile) but I need more pointers as to where to look. Paul, I do not understand your last comment about addpredict, what is that? a gentoo ebuild command? What is the syntax and purpose of it? Dan, could you help me out trying to understand who and where inside the kdelibs stuff this is actually created, investigation of install.sh and Makefile really got me confused as I couldn't found any /etc/settings reference in them. |