I am not sure if it's a bug ...
anyway, at least on AMD64 you have removed MSN protocol.
Right now I am avoiding an upgrade because the flag has been marked as not usable.
emerge -vp net-im/pidgin
[ebuild R ] net-im/pidgin-2.0.2 USE="crypt dbus eds gstreamer gtk ncurses nls perl spell tcl tk -avahi -bonjour -debug -doc -gadu -gnutls -groupwise -meanwhile -networkmanager -prediction -qq -sasl -silc -startup-notification -xscreensaver -zephyr (-msn%*) (-ssl%*)" 7,655 kB
Steps to Reproduce:
1. emerge -vp net-im/pidgin
MSN support is just always enabled from now on. Test it
what you mean when you say: "test it"
Right now, I did a sync of portage and the situation is still the same.
Do you mean, that this situation will be fixed within a day (just the time to replicate all the mirrors?)
To sync portage I am using: rsync.europe.gentoo.org
No; it's no longer optional. Read the fine ChangeLog.
ok ... sorry If I am not that smart today :)
What does it means? I have read changelog before opening this bug.
But in my opinion it's wrong what 'emerge -vp' reports.
If I see (-msn%*) and as far as I know it means that you are removing the protocol.
(should I leave the bug closed to communicate with you??)
no I reopen it because, if it's true what you say, IMHO is wrong the: (-msn%*)
It should be: (+msn%*)
(In reply to comment #4)
> If I see (-msn%*) and as far as I know it means that you are removing the
That's why have have ChangeLogs. Emerge doesn't know whether the feature was removed or just no longer optional.
Please, read man emerge and leave this bug alone.
- prefix = not enabled (either disabled or removed)
from man emerge I understand that there is not a '+' symbol, but this is a problem
If you write '-' (minus) people can understand only minus and not the opposite.
well ... perhaps it's a issue with emerge, but it should be: (+msn%*) and not
mmmhh .... Jakub, don't tell me that this is correct ....
Re-read Comment #6; and *please* stop this bugspam already.
sorry, but I completely disagree.
You should tell me to file a bug over emerge and not tell me that eveything is right.
(-msn%) makes no sense.
(In reply to comment #10)
> (-msn%) makes no sense.
Of course it does make sense. The flag was *removed* (man emerge). You shouldn't file any bugs about emerge, because it's not a bug. Portage has zero knowledge about pidgin internal build system and *cannot* tell you whether the feature was completely removed or just enabled by default. Read the ChangeLog.
but people will continue seeing this (-msn%) and will understand what you say?
What you understand when reading (-msn%) ?
Or better, what you understand when reading '-' (minus)? Do you understand MINUS, or do you understand READ_CHANGELOG?
(In reply to comment #12)
> but people will continue seeing this (-msn%) and will understand what you say?
> What you understand when reading (-msn%) ?
> Or better, what you understand when reading '-' (minus)? Do you understand
> MINUS, or do you understand READ_CHANGELOG?
I understand that the not enabled msn USE flag has been removed from the ebuild. You cannot tell Portage in any way that the features switched with an USE flag has been enabled or not.
uff .... I am trying to speak the same language of the end user and the '-' is misleading for end user. It's a comsetic issue, but it's still an issue.
Please explain me the difference between (on amd64):
emerge -vp skype (qt-static)
emerge -vp pidgin (-msn%)
the question is that we are speaking about same version. Pidgin is not going to be updated to a new release.
If I see all other protocols and I can't see msn, I *MAY* understand that msn doesn't work.
(In reply to comment #14)
> uff .... I am trying to speak the same language of the end user and the '-' is
> misleading for end user. It's a comsetic issue, but it's still an issue.
We are trying to tell you what the facts are. This colourful syntax for USE flags just tells you what has been removed from the ebuild it has nothing to do with the internal functionality and so there is really no need/possibility in whatever way to tell the user something about it.
What Portage does is compare the USE flags the package has been merged with
IUSE="server X -msn -yahoo"
with the USE flags in the new ebuild
IUSE="server X -yahoo"
And now, you should tell me how Portage can determine what happened between the two states. If you can, please implement it, too.
ok ... I understand that.
the question is that "disabled" and "removed" cannot be really the same thing.
It misleads ... until MSN flag exists on the distro, people may understand that this software doesn't have MSN on it.
I also understand that this is a transiction, because maybe you don't want to deal with all those "useless" flag (99.0% of people will use flag like: icq, yahoo and msn when they install a messenger).
Is this the reason? Did you get tired to deal thousands of flags? That's acceptable and you can do it.
Otherwise, if this was not the case, it's not written anywhere that this flag is incorporated .... oh, yes I know it is in the Changelog, and I have read it before filing this bug, but come on ... that's not the point.
In this case, you should do like skype, i.e.: emerge pidgin (msn) (yahoo) (icq) spell tcl tk -avahi -bonjour ... and so far and so on ... and you should not delete/remove the flag in the way you did.
Licq still uses msn flag .... so I user may understand that licq is the only software supporting MSN.
*** Bug 186306 has been marked as a duplicate of this bug. ***
(In reply to comment #16)
> ok ... I understand that.
> the question is that "disabled" and "removed" cannot be really the same thing.
> It misleads ... until MSN flag exists on the distro, people may understand that
> this software doesn't have MSN on it.
> I also understand that this is a transiction, because maybe you don't want to
> deal with all those "useless" flag (99.0% of people will use flag like: icq,
> yahoo and msn when they install a messenger).
> Is this the reason? Did you get tired to deal thousands of flags? That's
> acceptable and you can do it.
I am not maintainer of pidgin and I would not care handling so many USE flags as they are no real hassle. The reason is different.
> Licq still uses msn flag .... so I user may understand that licq is the only
> software supporting MSN.
Normally people read about a software "Oh, wow, Pidgin supports all the protocols I want!". Then emerge it if it is available. They expect all those protocols to work if there is no special USE flag about it.
The Pidgin developers asked us to include all protocols that don't need a special library (as gadu), so they have less "bug" reports from Gentoo users that did not find MSN in the protocol list. Anyway, the change seems to provoke "bug" reports on our side. Now enough bug spam, any more questions go to gentoo-users mailing list or to /dev/null
*** Bug 187566 has been marked as a duplicate of this bug. ***