9:28 a.m.
Hello,
recent java-packages (ant*, xerces*, ...) have scriptlets like
| $ rpm -q --scripts servletapi5-javadoc
| postinstall scriptlet (using /bin/sh):
| rm -f /usr/share/javadoc/servletapi5
| rm -f /usr/share/javadoc/jsp-api
| ln -s servletapi5-5.0.18 /usr/share/javadoc/servletapi5
| ln -s jsp-api-5.0.18 /usr/share/javadoc/jsp-api
This is really bad code because it does not make sense in an rpm-world
and causes problems in combination with the %_netsharedpath feature.
E.g. when the /usr/share filesystem is shared between several hosts you
can:
* manage (add, remove, modify) files on this filesystem on exactly one
host, and
* mount this filesystem (e.g. over NFS) as read-only on the other hosts
and add it to rpm's %_netsharedpath. E.g.
| # cat /proc/mounts | grep /usr/share
| morden:/usr/share /usr/share nfs ro,...
|
| # rpm --showrc | grep netsha
| -14: _netsharedpath ...:/usr/share:...
Then, rpm will assume the files under /usr/share as existing and does
not touch them:
| $ rpm -qs servletapi5-javadoc
| net shared /usr/share/javadoc/jsp-api-5.0.18
| net shared /usr/share/javadoc/jsp-api-5.0.18/JAVADOC.PLACEHOLDER
| net shared /usr/share/javadoc/servletapi5-5.0.18
| net shared /usr/share/javadoc/servletapi5-5.0.18/JAVADOC.PLACEHOLDER
In such a scenario, scriptlets like above will fail horribly
| Preparing... ########################################### [100%]
| 1:servletapi5-javadoc ########################################### [ 50%]
| rm: cannot remove `/usr/share/javadoc/servletapi5': Read-only file system
| rm: cannot remove `/usr/share/javadoc/jsp-api': Read-only file system
| ln: creating symbolic link `/usr/share/javadoc/servletapi5/servletapi5-5.0.18' to
`servletapi5-5.0.18': Read-only file system
| ln: creating symbolic link `/usr/share/javadoc/jsp-api/jsp-api-5.0.18' to
`jsp-api-5.0.18': Read-only file system
| error: %post(servletapi5-javadoc-5.0.18-1jpp_3fc) scriptlet failed, exit status 1
As already said, this does not make sense in an rpm-world. There, the
'jsp-api' symlink should be created in the %install stage and packaged
as an ordinary file. Then, rpm will unpack it correctly (inclusive
honoring the %_netsharedpath) and no %post scriptlet is needed.
Enrico
9:51 a.m.
Le mardi 07 décembre 2004 à 16:28 +0100, Enrico Scholz a écrit :
Hello,
recent java-packages (ant*, xerces*, ...) have scriptlets like
| $ rpm -q --scripts servletapi5-javadoc
| postinstall scriptlet (using /bin/sh):
| rm -f /usr/share/javadoc/servletapi5
| rm -f /usr/share/javadoc/jsp-api
| ln -s servletapi5-5.0.18 /usr/share/javadoc/servletapi5
| ln -s jsp-api-5.0.18 /usr/share/javadoc/jsp-api
This is really bad code because it does not make sense in an rpm-world
and causes problems in combination with the %_netsharedpath feature.
This is one of the last raw areas on JPackage 1.6.
To this date no one has found a satisfactory way to build & install
interlinked javadocs (I think you'll find several threads on this
problem in list archives). The current solution is Ville's (I think) and
he publicly stated he didn't like it.
If you're interested by the problem feel free to review specs and
propose solutions on jpackage-discuss(a)zarb.org. JPackage enhancements
will end up in rawhide then FC/RHEL (and given your heavy Fedora
involvement I can't imagine you not getting direct repo commit access if
you asked for it)
Regards,
--
Nicolas Mailhot
8:05 p.m.
Nicolas.Mailhot(a)laPoste.net (Nicolas Mailhot) writes:
> recent java-packages (ant*, xerces*, ...) have scriptlets like
>
> | $ rpm -q --scripts servletapi5-javadoc
> | postinstall scriptlet (using /bin/sh):
> | rm -f /usr/share/javadoc/servletapi5
> | rm -f /usr/share/javadoc/jsp-api
> | ln -s servletapi5-5.0.18 /usr/share/javadoc/servletapi5
> | ln -s jsp-api-5.0.18 /usr/share/javadoc/jsp-api
>
>
> This is really bad code because it does not make sense in an rpm-world
> and causes problems in combination with the %_netsharedpath feature.
...
If you're interested by the problem feel free to review specs and
propose solutions on jpackage-discuss(a)zarb.org.
I fear that my preferred solution (%macro magic) will conflict with
policies of jpackage. The feature that every /etc/rpm/macros.* file will
be read by rpm is relatively new and might not exist on all jpackage
platforms.
Missing backward-compatibility will not be a problem on FC so it could
be used there.
Enrico
2:16 a.m.
Le mercredi 08 décembre 2004 à 03:05 +0100, Enrico Scholz a écrit :
Nicolas.Mailhot(a)laPoste.net (Nicolas Mailhot) writes:
>> recent java-packages (ant*, xerces*, ...) have scriptlets like
>>
>> | $ rpm -q --scripts servletapi5-javadoc
>> | postinstall scriptlet (using /bin/sh):
>> | rm -f /usr/share/javadoc/servletapi5
>> | rm -f /usr/share/javadoc/jsp-api
>> | ln -s servletapi5-5.0.18 /usr/share/javadoc/servletapi5
>> | ln -s jsp-api-5.0.18 /usr/share/javadoc/jsp-api
>>
>>
>> This is really bad code because it does not make sense in an rpm-world
>> and causes problems in combination with the %_netsharedpath feature.
> ...
> If you're interested by the problem feel free to review specs and
> propose solutions on jpackage-discuss(a)zarb.org.
I fear that my preferred solution (%macro magic) will conflict with
policies of jpackage. The feature that every /etc/rpm/macros.* file will
be read by rpm is relatively new and might not exist on all jpackage
platforms.
Good excuse but... we've been depending on our own sets of macros
forever. So we already have a macro file + all the plumbing to get it
deployed on every platform we target;)
Regards,
--
Nicolas Mailhot
1:41 a.m.
On Tue, 2004-12-07 at 16:51 +0100, Nicolas Mailhot wrote:
Le mardi 07 décembre 2004 à 16:28 +0100, Enrico Scholz a écrit :
> Hello,
>
> recent java-packages (ant*, xerces*, ...) have scriptlets like
>
> | $ rpm -q --scripts servletapi5-javadoc
> | postinstall scriptlet (using /bin/sh):
> | rm -f /usr/share/javadoc/servletapi5
> | rm -f /usr/share/javadoc/jsp-api
> | ln -s servletapi5-5.0.18 /usr/share/javadoc/servletapi5
> | ln -s jsp-api-5.0.18 /usr/share/javadoc/jsp-api
>
>
> This is really bad code because it does not make sense in an rpm-world
> and causes problems in combination with the %_netsharedpath feature.
This is one of the last raw areas on JPackage 1.6.
To this date no one has found a satisfactory way to build & install
interlinked javadocs (I think you'll find several threads on this
problem in list archives). The current solution is Ville's (I think) and
he publicly stated he didn't like it.
Actually that basic "solution" predates me in JPackage. And "didn't
like" is a understatement, that's seriously ugly stuff and needs work.
The basic requirements, IMO in order of importance are that: it needs to
work, it needs to provide something unversioned (for bookmarking, IDE
config, javadoc crosslinking etc), and it must be possible to install
several versions of the same javadoc package in parallel. Currently #1
fails in certain situations.
7080
days inactive
7082
days old
4 comments
3 participants
participants (3)
-
Enrico Scholz -
Nicolas Mailhot -
Ville Skyttä