Ok, I'll make them arch dependant. Thanks! Martin 2006/10/3, Michael Schroeder :

On Mon, Oct 02, 2006 at 09:49:03PM +0200, Martin Vuk wrote:

...

while buildnig noarch packages like systemmanagement:misc/puppet only the x86_64 variant is available in the repo after the build is finished. The build report says both are build, but I guess x86_64 packages just overrides the i586 in noarch dir. The problem is that x86_64 uses /usr/lib64/ruby which is not in ruby libpath on i586 system. So obviously i568 and x86_64 packages differ, althow they suppose to be arch independant.

If they differ the package is not arch independant -> this is not a noarch package.

Cheers, Michael.

-- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On 2006-10-04 16:48:27 +0200, Martin Vuk wrote:

One sidenote which probobally aims at ruby packagers.

Why is ruby sitelibdir (/usr/lib(64)/ruby/site_ruby/ ) arch specific? Is there a reason for packages containing only ruby source code to be architecture dependant?

because you cant create a noarch and arch dependent package in the same spec file. and i dont see the need in 2 spec files for that atm. while we are at it: for 10.2 i applied a patch that adds vendor_ruby to the lists of supported directories. the patch is already active in the ruby project in the buildservice. add "-rvendor-specific" to the cmdline, when calling extconf.rb/setup.rb/install.rb. for examples see the ruby project. additionally ... if your ruby library is provided as gem, you should package it as gem. (see rubygem-* packages) mostlikely another gem will depend on it. so having it as rubygem-* rpm makes it possible to use it from gems and use it directly from other libraries/scripts. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On 2006-10-05 12:43:44 +0200, Martin Vuk wrote:

...

additionally ... if your ruby library is provided as gem, you should package it as gem. (see rubygem-* packages) mostlikely another gem will depend on it. so having it as rubygem-* rpm makes it possible to use it from gems and use it directly from other libraries/scripts. I agree. I don't think the library is used at the moment by other gems, but it might be in the future. The problem is that the gems don't install the binaries, initscripts and such. So now I have two

2006/10/4, Marcus Rueckert : packages

puppet.rpm which provides library and binaries for the client and puppet-server.rpm providing the server part

So what do you suggest? Should I split the library part in gemruby-puppet.rpm and daemons, binaries and other stuff to puppet.rpm and puppet-server.rpm?

packaging a gem like that is ... hard to impossible. than lets stick to the old way. :) darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org