Description of problem:
Install of RHEL5 Server adds an icon for evolution to the
menu strip but evolution is not included in distribution
Install RHEL5 Server.
No evolution icon in menu strip.
*** This bug has been marked as a duplicate of 214879 ***
Warren, I'm tossing this your way. Shout if you think that's the wrong thing to do.
Own package, I agree is a good idea. However I don't think mail clients should
Is moving it to its own package possible for RHEL5 at this point?
Argh! This reminds me, launchmail's icon definition has regressed. It should
be labeled "Mail" and not "Evolution", because it really runs an arbitrary mail
client chosen in "Preferred Applications" and not evolution.
I have a list of other bug fixes needed for launchmail... but I just haven't had
a chance to do it yet. =(
Well the whole point is, you don't add it to comps and rely on the mail clients
to pull it in via dependencies.
If there aren't any mail clients installed then it won't get pulled in and the
TryExec=/usr/bin/launchmail will fail so the icon will get hidden.
It can be done simpler than this.
[warren@caprica ~]$ rpm -ql htmlview
[warren@caprica ~]$ ls -l /usr/share/applications/redhat-email.desktop
lrwxrwxrwx 1 root root 52 Nov 9 12:46
Those .desktop files provided in htmlview are only a symlink to the actual
.desktop file from the redhat-menus package.
launchmail (independent package) can own the /usr/bin/launchmail script and this
symlink. Then comps can refer to htmlview and launchmail as needed... RHEL5
Client but not server for example.
I can split the package and apply other fixes that I wanted in lauchmail. But
is it still possible to do so for RHEL5 at this late date?
1. launchmail becomes its own package containing the script and symlink.
2. Adding launchmail to comps in the appropriate products where a mail client is
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Does this affect both Client and Server?
Client ships with both web browser and e-mail clients.
Server ships with only web browser.
So this is a problem for only Server. For consistency sake however, it should
be split and comps pulls in where it is needed in the respective products.
What other option do we have without splitting it?
unconditionally install evolution?
Remove the Email launcher from the top panel of RHEL5 Server GNOME. This
launcher currently does nothing.
Implications of Splitting:
htmlview has possible dependencies from existing user profiles (from RHEL3 or
RHEL4) and maybe programs in RHEL5. But that is OK, because htmlview would
remain in both RHEL5 Server and Client.
htmlview does not require launchmail, and vice versa.
launchmail was used *only* by the .desktop launcher on the default GNOME panel.
Nothing else pointed at it or required it.
1) Split htmlview into separate htmlview and launchmail packages.
2) RHEL5 Client comps pulls in htmlview and launchmail.
3) RHEL5 Server comps pulls in only htmlview.
Good lord this is ugly, but pretty much required, otherwise Server will have a
desktop icon which doesn't work. QE ack for RHEL5. Needs to be done as soon as
I will get this done before 5PM Thursday, Dec 14th.
htmlview-4.0.0-1.el5 is currently building.
launchmail has been checked into /cvs/dist branch devel, needs branching to
RHEL-5. Please advise?
I am doing a little more testing of both packages now.
- launchmail-4.0.0-1.el5 is built.
- included in dist-5E
- comps pulls in launchmail only in RHEL5 Client (dgregor)
One possible issue...
Upgrading from RHEL4 to RHEL5.
RHEL4 had only htmlview.
RHEL5 has both htmlview and launchmail.
Will launchmail being in base-x group of comps be enough for an anaconda upgrade
to pull in launchmail for a RHEL5 Client upgrade?
(In reply to comment #19)
> Will launchmail being in base-x group of comps be enough for an anaconda upgrade
> to pull in launchmail for a RHEL5 Client upgrade?
No. We don't consider comps for upgrades as it's a bit fuzzy what that even means.
You need to have some package requiring it
There is no logical package to require launchmail. Nothing actually uses
launchmail. Adding a Requires from anywhere like evolution or thunderbird would
only be a hack.
Is adding a hack acceptable?
The options are really:
a) add a hack
b) lose the functionality on upgrade.
OK, we can add the hack for RHEL5.
But does this not point to a hole in our upgrade functionality? This is similar
to the scim-qtimm upgrade problem. Nothing logically required scim-qtimm so it
would not be installed during an upgrade, however the desktop actually did need
it if KDE is installed.
it's not really a hack, it's what I mentioned here:
is just another way of saying
If you like that better you could add a virtual provides...
launchmail is done.
Bug #219883 filed for evolution.
Bug #219884 filed for thunderbird.
Should I go ahead and just rebuild those packages, or should the two respective
maintainers do it?
Wait... why is this requires in the mailers? Shouldn't this requires be in
gnome-panel if its just a panel launcher?
evolution and thunderbird have been rebuilt. moving to MODIFIED
Chris, the requires has to be in the mailers so that the launcher is retained
during an upgrade but is not installed on a clean system with no mailers.
Additionally, gnome-panel is on RHEL5 Server but there exists no mail clients there.
Verified in a clean RHEL5-Server-20061226.nightly system, there is no both
evolution and thunderbird icon in menu, but in a upgrade system (EL4U4 -> EL5),
there is still thunderbird icon in menu, evolution icon has been moved.
I'm a bit confused. We didn't ship a thunderbird icon in the default RHEL4
install did we?
1) is thunderbird *installed* after this upgrade?
2) was this a new user in RHEL4, or one who had explicitly added a thunderbird
icon before doing the upgrade?
Thunderbird is installed by default in RHEL4U4. I did nothing and just upgraded
the clean RHEL4U4 to RHEL5-Server-20061226.nightly.
Ray, it is totally unclear to me what is left to do here. Can you clarify that ?
Warren what did you end up doing, what's left?
I'm confused. Didn't we split this package in the last minute before 5.0GA? I
don't know why this bug is still open.
I cannot say for certain however. I haven't used 5.0 GNOME for a long time.
I plan on doing Bug #311401 for 5.2.
Warren, this bug was yours. Can you investigate what you did, and if anything
left is needed (adding Requires: launchmail to the mail clients?)
Respectfully, I did the desktop team a favor by fixing the original problem here
of splitting the package. As far as I am concerned, this is fixed. It would be
desktop team's decision to add requires from other packages or not. I will not
be touching those other packages.
well, who does any remaining work is an orthogonal issue. I'm asking you to
summarize what work is already done, and what work you think needs to be done still.
If you think that you've fixed this issue already, and no more work is needed,
If you don't know what changes you made, or how much of the problem you
addressed, say so, and we can investigate ourselves.
The original problem of installing RHEL5 Server and seeing a non-functional
launcher is supposed to be fixed by what I did prior to 5.0GA.
You may want to test the following:
1) Is it actually fixed? (No mail launcher icon on panel of fresh install of
2) What happens in an upgrade from RHEL4 to RHEL5 server? Is there anything
that can be done about old launcher icons (probably not).