Mailinglist Archive: opensuse-packaging (267 mails)

< Previous Next >
Re: [opensuse-packaging] Is there a quick way to test all Requires are in factory?
  • From: Claudio Freire <klaussfreire@xxxxxxxxx>
  • Date: Sat, 24 Dec 2011 00:14:56 -0300
  • Message-id: <CAGTBQpYFoKO2hOqH6egba4wsp6P3Buk=TjMVBAhRkVtCjckqbg@mail.gmail.com>
On Fri, Dec 23, 2011 at 9:59 PM, David Haller <dnh@xxxxxxxxxxxx> wrote:
For example?

I've packaged _a lot_ of packages (a couple of hundred, most for my
ex-SUSE 6.2 over 10 years (ISTR >>500 RPMs of packages by me
installed), from small to quite a bunch like most of gnome). Usually,
there's _very_ little you need to explicitly have in Requires that is
not picked up automatically by "AutoReqProv" or via a require of the
corresponding -devel packages (which you need to have in
BuildRequires). And most if not all (well it should be all)
configure-scripts (and alike) will check for those executables to be
available for build, and so they'll get pulled into the Build and
usually picked up as a Require for the Package.

Then you've never packaged python apps.
You don't need any -devel stuff on python, you only need python itself
to generate bytecode.

It's also the case when there's any service you connect to by IPC,
like dbus, X.org, etc...

And no, libX is *not* X.org
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups