RPM Community Forums

Mailing List Message of <rpm-users>

Re: Single RPM database, multiple platforms

From: Jeff Johnson <n3npq@mac.com>
Date: Wed 04 Mar 2009 - 10:11:17 CET
Message-id: <699A6F70-0FC1-4597-BB3E-CA70BAF9FF4F@mac.com>

On Mar 4, 2009, at 2:52 AM, Jeff Putsch wrote:
>>>
>
> Right. So with "%_dbpath /var/lib/%{_target_cpu}-%{_target_os}",  
> where does the DB for noarch packages go? Do I end up with one per % 
> {_target_os} in /var/lib/noarch-%{_target_os}? My initial testing  
> says yes.
>

There are no "noarch" platforms.

I.e. You have no instances of platforms you wish to manage
that identify as either "noarch" or "noos", and so you will
have no paths in your NFS rpmdb store that include "noarch".

You will never need or use
	--target noarch
and nparch packages will reside where they've always resided.

OTOH, you also can create platforms as you wish, and populate
%_target_cpu or %_target_or or %whatever as needed.

The only trick is to use a macro expansion in the path to
an rpmdb to use multiple databases easily and transparently.

73 de Jeff
Received on Wed Mar 4 10:11:33 2009
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.