Re: [opensuse-gnome] Pidgin
Can you keep replies on-list please?
what's the name of the pidgin package? i just made a quick search on the webpin project website, and it returned no results, and did you make it so it can automatically update gaim-unstable?
It's called pidgin. Is there some latency on webpin perhaps? Haven't made it automatically update yet but I intend to once I'm satisfied it's relatively stable (seems to be so far). -- James Ogley james@usr-local-bin.org http://usr-local-bin.org GNOME for openSUSE: http://software.opensuse.org/download/GNOME:/ Help end poverty: http://oxfam.org.uk/in -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
Pidgin 2.0.0 final is due tomorrow, would it be okay to make it replace gaim as well as gaim-unstable in GNOME:Community with a view to it going into Factory for 10.3? -- James Ogley james@usr-local-bin.org http://usr-local-bin.org GNOME for openSUSE: http://software.opensuse.org/download/GNOME:/ Help end poverty: http://oxfam.org.uk/in -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Wed, 2007-05-02 at 21:39 +0100, James Ogley wrote:
Pidgin 2.0.0 final is due tomorrow, would it be okay to make it replace gaim as well as gaim-unstable in GNOME:Community with a view to it going into Factory for 10.3?
Sounds good to me, worst that happens is we don't move it into Factory.
-JP
--
JP Rosevear
Sounds good to me, worst that happens is we don't move it into Factory.
Is the best way to do this to add something like this to the spec file: Provides: gaim = %version-%release Obsoletes: gaim Or is there some spec-file-foo for saying it upgrades a differently named package that I'm not aware of? -- James Ogley james@usr-local-bin.org http://usr-local-bin.org GNOME for openSUSE: http://software.opensuse.org/download/GNOME:/ Help end poverty: http://oxfam.org.uk/in -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Thu, 2007-05-03 at 08:37 +0100, James Ogley wrote:
Sounds good to me, worst that happens is we don't move it into Factory.
Is the best way to do this to add something like this to the spec file:
Provides: gaim = %version-%release Obsoletes: gaim
Or is there some spec-file-foo for saying it upgrades a differently named package that I'm not aware of?
Nope, that should be it. See ekiga for an example.
-JP
--
JP Rosevear
Hi,
On 5/3/07, JP Rosevear
On Thu, 2007-05-03 at 08:37 +0100, James Ogley wrote:
Sounds good to me, worst that happens is we don't move it into Factory.
Is the best way to do this to add something like this to the spec file:
Provides: gaim = %version-%release Obsoletes: gaim
Or is there some spec-file-foo for saying it upgrades a differently named package that I'm not aware of?
Nope, that should be it. See ekiga for an example.
It might also be a good idea to add "Conflicts: gaim < [some version]" so that you can't also install an older version of gaim, which would probably fail because of file conflicts at install-time. Joe -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
It might also be a good idea to add "Conflicts: gaim < [some version]" so that you can't also install an older version of gaim, which would probably fail because of file conflicts at install-time.
Okay, pidgin 2.0.0 (final) is now in G:C (2.0.0-39.1 for distro versions 10.1 and upwards to Factory) and it *should*, all being well, automagically upgrade gaim to itself. -- James Ogley james@usr-local-bin.org http://usr-local-bin.org GNOME for openSUSE: http://software.opensuse.org/download/GNOME:/ Help end poverty: http://oxfam.org.uk/in -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
Joe Shaw wrote:
It might also be a good idea to add "Conflicts: gaim < [some version]" so that you can't also install an older version of gaim, which would probably fail because of file conflicts at install-time.
No. If you use Obsoletes, Conflict is not needed. Obsoletes means: install this package and remove obsoleted package. And when it is used improperly (not this case) in combination with Provides, it's easy to create a package, which conflicts with itself. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
Hi,
On 5/7/07, Stanislav Brabec
No. If you use Obsoletes, Conflict is not needed. Obsoletes means: install this package and remove obsoleted package.
That's correct, it does mean this, but without Conflicts, you can have this situation: (1) gaim installed (2) install pidgin; because of Obsoletes, gaim is removed. (3) install gaim; because there is no Conflicts, it will attempt to install. If there are file conflicts, you get them at install-time rather than a sane error at dep solve-time. Otherwise, it will isntall and you have both. There are lots of reasons why (3) could happen: solving dependencies for another package, the user didn't know that gaim and pidgin were the same thing, etc. As for the package which conflicts with itself, I think this is the reason to have the versioned Conflicts. Ie, you provide pidgin = %{version} and gaim =%{version} and conflict gaim < 2.0.0. Joe -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
participants (4)
-
James Ogley -
Joe Shaw -
JP Rosevear -
Stanislav Brabec