On Sat, Apr 14, 2012 at 12:44 PM, Herbert Graeber <[email protected]> wrote: > Am Samstag, 14. April 2012, 01:09:25 schrieb Cristian Morales Vega: >> I got this list from the output of zypper. It does not include >> packages with different names in openSUSE and Packman, but... >> Any idea about why they are in Packman? libmms is there because the >> 32bit package is needed by gstreamer-0_10-plugins-bad-32bit. The >> others, no idea... > > But some some packages may get updates later and therefore may become newer > than the 12.1 ones in future. For those packages it may be better to keep them > enabled even when they have identical contents as packages from 12.1. Else our > users are forced to hop between repos with vendor changes all the time.
Those packages are present in openSUSE-factory, then, right? Should they be linked to the factory version rather than being stand-alone packages? >> google-perftools >> google-perftools-devel >> libetpan-devel >> libmms0 >> libmms-devel >> libqwt5 >> libwavpack1 >> libwavpack1-32bit >> licq >> licq-devel >> licq-kde4-gui >> licq-qt4-gui >> licq-qt4-gui-data >> linphone >> linphone-applet >> linphone-devel >> perl-AnyEvent >> perl-Class-Factory-Util >> perl-Class-Singleton >> perl-Config-Tiny >> perl-DateTime >> perl-DateTime-Format-Builder >> perl-DateTime-Format-Strptime >> perl-DateTime-Locale >> perl-Devel-Cycle >> perl-Digest-CRC >> perl-File-Find-Rule >> perl-JSON-XS >> perl-libintl-perl >> perl-Number-Compare >> perl-PadWalker >> perl-Switch >> perl-Test-Fatal >> perl-Test-Memory-Cycle >> perl-Test-Simple >> perl-Text-Glob >> perl-Try-Tiny >> portaudio-devel >> python-distribute >> python-pyparsing >> python-pyparsing-doc >> python-Sphinx >> python-Sphinx-doc >> python-xdg >> qwt-designer >> qwt-devel >> qwt-devel-doc >> qwt-examples >> ripit >> wavpack >> wavpack-devel >> xine-ui _______________________________________________ Packman mailing list [email protected] http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
