[packman] y2pmbuild

[Marcus Rueckert]

On 2006-03-30 20:07:49 +0200, Peter Czanik wrote:
> > where is your problem with y2pmbuild?
> >   
> 
> Actually, as Pascal already pointed out: my real problems are the spec
> files :-( y2pmbuild works fine, as long as spec files are created with a
> clean chrooted environment in mind. But about half of them are not,
> that's why I was sending so many diffs. And there are already some, I
> could not fix to compile with y2pmbuild, like transcode, and now
> kaffeine. I'm spending my second full day with fighting non y2pmbuild
> compliant PackMan packages...

ah that is what i expected ... please be accurate in your statements.
it is not y2pmbuild that is driving you insane ... it are the packages
not being specified properly.

using y2pmbuild for building your packages will make sure you can easily
recreate the build environment. unlike with building in your running
systems or full fledged chroots.

> BTW: the kaffeine problem might be not PackMan specific, as I had this
> earlier with SUSE packages too:
> 
> 100 packages to install
> unresolvable dependencies:
> *** Conflicts ***
> Name: avahi-compat-mDNSResponder
> Edition: 0.6.5-15
> Referers: kdelibs3-3.5.1-32 requires libdns_sd.so, kdelibs3-3.5.1-32
> requires libdns_sd.so
> Conflicts-With: avahi-compat-mDNSResponder-0.6.5-15 conflicts with
> mDNSResponder, avahi-compat-mDNSResponder-0.6.5-15 conflicts with
> mDNSResponder
> Remove-To-Solve-Conflict: kdebase3-devel, kdelibs3-devel, mDNSResponder

that can be easily solved by using the correct buildrequires line.

> Some other typical mistakes are leaving out:
> update-desktop-files
> xorg-x11-devel
> pkgconfig

:)

those can be definitely pain. but with the y2pmbuild/build from 10.1 you can
minimize the spec files quite a lot. it will discover the transient
depedencies. e.g. pulling in kdedevel will automatically pull in
xorg-x11-devel. :)

> I would be really glad, if PackMan package maintainers outside SuSE
> would also compile their packages with y2pmbuild, as my life would be a
> lot more simple... Bye,

agreed especially with the new y2pmbuild. :)

you can just take the factory src rpm of y2pmbuild and rebuild it on 10.0 btw.
hope this helps

darix

-- 
           openSUSE - SUSE Linux is my linux
               openSUSE is good for you
                   www.opensuse.org