Summary: | konqueror opening links to files inside tarfile | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Unknown <null> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | wishlist | CC: | finex, jonas.vejlin |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: |
Description
Dirk Hohndel
2000-10-25 20:05:03 UTC
David Faure wrote:
>
> Hello Dirk
>
> On Wednesday 25 October 2000 20:05 hohndel@suse.de wrote:
> > Package: konqueror
> > Version: Konqueror 1.9.8 as of KDE Release 2.0
> > Severity: wishlist
> > Installed from: SuSE RPMs
> >
> > I use konqueror to open a tar.gz for browsing
> > (say /tmp/t.tar.gz)
> > and that tar file contains an html file and a symbolic
> > link to that html file.
> > If I then click on that symbolic link to an html filei
> > nside that tar.gz file konqueror tries to access that
> > document but failes with
> > "The file or directory /tmp/target.html does not exist".
> > I.e. it takes the link relative to the file system
> > and not relative to the tar file.
> > I admit this is a subtle point...
>
> The link should be a relative link then.
>
> It's just the same as when you mount a filesystem into another partition
> or use NFS. Only relative symlinks work in that case.
>
I understood the bug report in a way that link.html pointing
to target.html are resolved within the directory the tarball
is in not in the tarball itself. Which could be argued as
bug - but a subtle as Dirk says :)
Greetings Stephan
--
Frauen und Maenner passen vielleicht nicht zusammen aber meine
allerschoensten Schrammen habe ich mir bei diesem Duell geholt.
-- Reinhard Mey
Hello Dirk On Wednesday 25 October 2000 20:05 hohndel@suse.de wrote: > Package: konqueror > Version: Konqueror 1.9.8 as of KDE Release 2.0 > Severity: wishlist > Installed from: SuSE RPMs >=20 > I use konqueror to open a tar.gz for browsing > (say /tmp/t.tar.gz) > and that tar file contains an html file and a symbolic > link to that html file. > If I then click on that symbolic link to an html filei > nside that tar.gz file konqueror tries to access that > document but failes with=20 > "The file or directory /tmp/target.html does not exist". > I.e. it takes the link relative to the file system=20 > and not relative to the tar file. > I admit this is a subtle point... The link should be a relative link then. It's just the same as when you mount a filesystem into another partition or use NFS. Only relative symlinks work in that case. I'm not too sure this should be hacked into the tar-file support... It could be but : imagine you then give that tar file to someone else who will untar it into a directory of his. An absolute link won't work whereas a relative link would. --=20 David FAURE david@mandrakesoft.com faure@kde.org http://www.mandrakesoft.com/~david/ http://www.konqueror.org/ KDE Making The Future of Computing Available Today See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2 On Wednesday 25 October 2000 20:43 Stephan Kulow wrote: > David Faure wrote: > >=20 > > Hello Dirk > >=20 > > On Wednesday 25 October 2000 20:05 hohndel@suse.de wrote: > > > Package: konqueror > > > Version: Konqueror 1.9.8 as of KDE Release 2.0 > > > Severity: wishlist > > > Installed from: SuSE RPMs > > > > > > I use konqueror to open a tar.gz for browsing > > > (say /tmp/t.tar.gz) > > > and that tar file contains an html file and a symbolic > > > link to that html file. > > > If I then click on that symbolic link to an html filei > > > nside that tar.gz file konqueror tries to access that > > > document but failes with > > > "The file or directory /tmp/target.html does not exist". > > > I.e. it takes the link relative to the file system > > > and not relative to the tar file. > > > I admit this is a subtle point... > >=20 > > The link should be a relative link then. > >=20 > > It's just the same as when you mount a filesystem into another partitio= n > > or use NFS. Only relative symlinks work in that case. > >=20 > I understood the bug report in a way that link.html pointing > to target.html are resolved within the directory the tarball > is in not in the tarball itself. Which could be argued as > bug - but a subtle as Dirk says :) Nope I tested that and it works just fine. I tested blah/ blah/test.html blah/link.html where link.html -> test.html This works the link is resolved ok. --=20 David FAURE david@mandrakesoft.com faure@kde.org http://www.mandrakesoft.com/~david/ http://www.konqueror.org/ KDE Making The Future of Computing Available Today See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2 Hi David On Wed 25 Oct David Faure wrote: > > The link should be a relative link then. > > It's just the same as when you mount a filesystem into another partition > or use NFS. Only relative symlinks work in that case. It is a hardlink in this case which should be recognizable as "contained inside the tar file". > I'm not too sure this should be hacked into the tar-file support... Neither am I as this is not exactly an important issue I just happened to run into it and wanted to report it. > It could be but : imagine you then give that tar file to someone else > who will untar it into a directory of his. An absolute link won't work > whereas a relative link would. And so would the hardlink that I have in this case Dirk Replaced hohndel@suse.de with null@kde.org due to bounces by reporter is this stil valid wish for konq 4.2.4? All reports about file management mode reported against KDE 3 (konqueror) has been closed: konqueror in KDE 3 is no more developed and mantained. All bugs and wishes which could be interesting for Dolphin in KDE 4 (the new KDE file manager) has been collected into a specific list. Please try the new file manager before request new features and report bugs. Before submitting new reports check carefully the already opened KDE/Dolphin reports in order to don't add duplicates. Many thanks. |