openSUSE Build Service September 2006

buildservice@lists.opensuse.org

44 participants
77 discussions

[opensuse-buildservice] more newby questions: project / package structure?

by Andreas Jellinghaus

Hi, how are projects and packages structured? is it a fixed "one name for the project and then one for the package" system, or are further subdirs possible? I wonder about this: recent discussions with rpm experts have shown me that merging several spec files into one only creates a horrible maintainence hell. also they have compelling arguments, that one rpm for all distributions was something they tried for years with lots of work, and it never worked well. so I see as best solution to have codenames (e.g. fc3,fc4,fc5, sles9, sles10, oss10.0, dapper, edgy, etch, sarge, ...) and for each distribution *.spec.$codename or *.diff.gz.$codename. but this would require work on the build system side, and I get the impression noone wants that. the alternative from my side would be per distro packages. e.g. instead of "openct" I could have packages "openct.fc" and "openct.os" and "openct.sles" and "openct.sarge" and so on, upload spec files for each. this wouldn't require changes in the code base, and give me the flexibility I need, so I can simply build new packages for my open source projects, with minimal changes to the last spec file the distribution provides. but that way the list of packages might grow very long. is it possible to structure projects/packages a different way (i.e. path mechanism, no flat one project, one package subdir structure)? Regards, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 2 months

[opensuse-buildservice] Please remove these projects

by Jigish Gohil

Could Build Service administrators delete these two projects created in root directory. libmetacity gset-compiz I apologise for the error. Thanks Jigish --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 3 months

[opensuse-buildservice] Proposal for project in root namespace: GNOME:*

by Stanislav Brabec

Hallo Build Service maintainers. We are just discussing on creating of Build Service projects for GNOME. Possible structure is: GNOME:GNOME-UNSTABLE GNOME:GNOME216 GNOME:EXTRAS Maybe there will be more projects or the final structure will be different. Please comment suggested letter case and use "-" or "_" - whether to use GNOME:216, GNOME:GNOME216, GNOME:Gnome216, GNOME:GNOME-2.16 or GNOME:GNOME_2_16 to conform naming scheme of other projects in the Build Service. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)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-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 3 months

[opensuse-buildservice] Proposal: move "cfengine" from home-project to "systemsmanagement:cfengine"

by Matthias G. Eckermann

Hi all, again me:-) any objections to move 'cfengine' to this more prominent place? so short MgE -- Voluminous documentation | Matthias G. Eckermann <mge(a)arcor.de> is part of the problem | Marienburger Str. 5A not part of the solution | 10405 Berlin (Tom DeMarco) | phone +49-30-44315730 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 3 months

[opensuse-buildservice] suggestion: limited trigger rebuild

by Andreas Jellinghaus

ok, I'm doing baby steps to get somewhere, and of course the first few versions of the spec file will be buggy. so I wonder: wouldn't it save resources on build.opensuse.org if I could first trigger a rebuild only on some plattform, wait if that succeeds, and only then trigger rebuild for other plattforms (e.g. the rest / all)? currently "trigger rebuild" will affect all build targets if I understand right and might be create a huge load on your system. Regards, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 3 months

[opensuse-buildservice] Announcement: New packages Beryl Project

by Jigish Gohil

I have been maintainging Compiz community packages on BS for a long time now. Recently the community has announced a fork of compiz - the Beryl Project, I would be maintaining those packages here at the build service. First packages should be released in couple of days. If anyone wants to test the 'preview' the packages are here: http://software.opensuse.org/download/home:/cyberorg/ Once released they would be available from here: http://software.opensuse.org/download/Compiz-Quinn/ You would require beryl-* and emerald packages to run beryl. Launch it with 'beryl-manager'. Cheers! Jigish -- CyberOrg Info Novell & IBM Partner 7 FF Unad Deep, Tower A Susen Tarsali Road Vadodara 390 009 T. +91 265 3042956 M +91 9898092956 Web. http://www.cyberorg.info --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 3 months

[opensuse-buildservice] Announcement: Beryl 0.1.0 release

by Jigish Gohil

Hello community, Yesterday we announced release of Beryl 0.1.0. Beryl is a fork of compiz maintained by the community at www.beryl-project.org. Beryl and Compiz gives the bling to your desktop making it fun to use. The packages are available for SUSE 10.1/SLE10 and openSUSE Factory/10.2. Here are the links to the packages. 10.1/SLE10: http://software.opensuse.org/download/X11:/XGL/SUSE_Linux_10.1/ 10.2/Factory: http://software.opensuse.org/download/X11:/XGL/SUSE_Factory/ 10.1/SLE10 running xorg7: http://software.opensuse.org/download/X11:/XGL:/10.1xorg7/10.1xorg7/ Apart from the Beryl packages the repository also contains upto date Compiz packages from Freedesktop git which can now use gnome themes and gnome-theme-manager. Compiz/Beryl can be run without XGL or AIGLX on xorg 7.1 and NVIDIA's new beta drivers. Install all the beryl packages including emerald and emerald-themes, launch by running beryl-manager. More information would be available here: http://forum.beryl-project.org/topic-4853-beryl-suse-packages File bugs/suggestions etc here: http://bugs.beryl-project.org/ Enjoy! -J ______________ CyberOrg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 3 months

[opensuse-buildservice] Re: can't build a kmp -- %flavors_to_build undefined?

by Leon Freitag

Seems that the problem occurs only on current factory 10.1 builds are fine -- will the schema of building kernel modules change in 10.2 (yet) again? Leon

15 years, 3 months

[opensuse-buildservice] Probelm with UFO:AI (cmake version)

by Dominique Leuenberger

Hi List, I'm just trying to build the packages for UFO:AI. Version 2.0rc5 was released 2 days ago. I uploaded the source to the BuildService and created the spec file. The nescessary patch to compile it was also made (I also need that patch on my local install). unfortunately, the BuildService only offers cmake 2.4.0, which lacks some features used in the cmakfilelist.txt used by UFO, namely the LIST APPEND commands. I have cmake 2.4.2 (from Guru) installed on my workstation and thus did not have this problem. How can I get a more recent version of CMake inside the BuildService? Or any other ways to build this package otherwise? Thanks for your appreciated help, Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 3 months

Re: [opensuse-buildservice] Yet Another Project

by Cameron Seader

When you say Gnome People who would this be? Please let me know who i am too coordinate with. Thanks, Cameron On Sun, 2006-09-24 at 10:45 +0200, Adrian Schröter wrote: > Hi Cameron, > > Am Saturday 23 September 2006 03:59 schrieb Cameron Seader: > > Greetings, > > I would like to create another project for creating rpms for the latest > > banshee with podcast support on SLED 10 and SUSE Linux 10.1 > > can you coordinate this with our Gnome people ? They are just about to put it > into the build service. > > bye > adrian >

15 years, 3 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service September 2006