Pascal Bleser ha scritto:
Andrea Florio wrote:
Hi, i'm ANDREA FLORIO, user Anubisg1, member of the italian wiki translation team and manteiner of anubisg1-repository
Ciao Andrea
http://en.opensuse.org/Additional_YaST_Package_Repositories#Anubisg1 I have a request to make, I would like to see my repository in the list showed by yast, that's why:
We should really keep that list quite short though. If there are too many in that list, people won't know which ones to add and which ones not, etc.., could be a little confusing.
1 My repository have only hard testing packages by users, all of that working 2 In a single repository i'm trying to include all instant messagin programs and others tools not included in OSS or packman repository
Mmm.. not sure, see below ;)
3 My repository is the only one the includes:
## aMSN-0.97-RC1 and aMSN-0.97-SVN (with amsn-skins and amsn-plugins) http://www.amsn-project.net/;
I maintain amsn packages in the Packman repository (not bleeding edge SVN snapshots though, I don't like to do that), and I even splitted out some tcl dependencies into their own package: tclsoap, ...).
It could be moved to the Build Service though.
## openC6 http://openc6.sourceforge.net/ (italian C6-messenger clone); ## KMess http://www.kmess.org/; ## Emesene http://www.emesene.org;
Why not move those 3 into a proper repository in the Buildservice ? The home: repositories are really just to play around with. If the packages are stable, you should move them to server:messaging (yeah, "server", I know, will be fixed soon).
## AcetoneISO2 http://www.acetoneteam.org/central.html; ## AcetoneISO2-SVN http://www.acetoneteam.org/central.html; ## MoioSMS-2.13
http://www.moioli.net/Progetti___1/MoioSMS___Messaggi_GRATIS_da_Internet____...;
## Ueagle-data-firmware (and soon ueagle-atm-drivers) www.eagle-usb.org/ ## A working version of GRUB-GFXboot
http://www.kde-look.org/content/show.php/Grub+gfxboot+splash+openSUSE?conten...
## LiVES http://lives.sourceforge.net/ (I have to upgrade to last version)
Doesn't lives use problematic dependencies ? (ffmpeg, ... ?) How about maintaining that in the Packman repository ?
And more i have: ## Pidgin (ever the last version, it exit befor of Gnome:Community) http://www.pidgin.im/;
Having yet another build of pidgin won't really help though, it would be better to contact the GNOME:STABLE or GNOME:Community maintainers to have it there.
Although personally, I think it belongs into server:messaging and not into GNOME:*
That applies equally to sdrahn though, he also has pidgin 2.2.1 in his home: repository.
## Amule-cvs (it's present in packman but mine have some little bigfix more, like menù entry)
You should really send an email to the Packman team then, not silently make yet another build of it somewhere else :)
Think about the end users. If it's provided by several repositories, it means that they have to add more repos and that they don't know which one to use.
## Amule-Adunanza ## Ekiga
Webpin tells me * ekiga: A Gnome based SIP/H323 teleconferencing application - 2.0.3 [suse-update | BS::openSUSE:/10.2] - 2.0.11 [packman] - 2.0.9 [BS::GNOME:/STABLE] - 2.0.2 [BS::home:/StefanBruens]
Packman already has 2.0.11.
## Licq
Webpin says: * licq: Linux ICQ Client - 1.3.4.9.1 [BS::home:/anubisg1 | BS::home:/lmich | BS::KDE:/Backports] - 1.3.4 [BS::home:/anubisg1 | BS::openSUSE:/10.2] - 1.3.4_20070909 [BS::home:/queden]
Means there are *three* repos providing licq-1.3.4.9.1 (for 10.2). Looks like it should rather be moved from KDE:Backports to KDE:Community and maintained there.
## Various libraries like libqt4 (imported from KDE:Qt project because needed for building and use acetoneISO, SLES/SLED users likes it)
You could see any packages and libraries from here:
http://en.opensuse.org/User:Anubisg1#News_Repository_Anubisg1
Andrea, you and all of us should really think about consolidating and avoiding to have the same packages in many repositories. The drawbacks are: - duplicating other people's work - no communication between packagers (=> why didn't you send your fixes/additions to the Packman packager for amule ? People who will use the amule package from Packman won't benefit from those) - *very* confusing for the end users
Heck, I'm moving my hundreds of packages to Packman and the Build Service mostly to give end-users a better experience (one repository less, no conflicts, sharing work), there shouldn't be more splitting happening now in the other repos.
Don't get me wrong, it's great you put work into packaging those things, but we should really think about consolidating first, which means: - avoid duplicating packages - don't consider home:* repositories as something the end-users should use - package things that cannot be in the Build Service in the Packman repository (it's not a closed team, people can join)
Looking forward to your feedback :)
cheers
To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org