pcp
[Top] [All Lists]

Re: packaging infrastructure

To: mtw@xxxxxxxxxxxxxx
Subject: Re: packaging infrastructure
From: Max Matveev <makc@xxxxxxx>
Date: Mon, 16 Jan 2006 23:51:18 +1100
Cc: pcp@xxxxxxxxxxx
In-reply-to: <Pine.GSO.4.60.0601160311331.1062@corp.theblr.com>
References: <Pine.GSO.4.60.0601160311331.1062@corp.theblr.com>
Sender: pcp-bounce@xxxxxxxxxxx
>>>>> "mtw" == Michael Werner <mtw@xxxxxxxxxxxxxx> writes:

 mtw> Currently, SGI's needs are met via the Makepkgs script, which deposits
 mtw> RPMs into the build subdirectory.  Does it only do RPM's, or can it
 mtw> also create Irix inst packages in some way that is not immediately
 mtw> obvious to me?

The Irix packaging is done by another script which is maintained by
people who do official Irix build. There is also more stuff in the
Irix version of pcp then it is in the open source (there are various
reasons for that) so we deliberately omitted Irix packing script from
the open source version.

 mtw> The recent patches I sent in added a Macpkg script, vaguely similar
 mtw> to Makepkgs, for creating MacOS packages. There is also a new subdir
 mtw> of ancillary packaging/installer files.  Additional OSs will require
 mtw> similar additional infrastructure.

AFAIR, Makepkgs was added when we started doing linux builds. The idea
behind it was to give a developer an easy recipe for producing an
OS-dependent package by automating the necessary steps of autoconf,
configure, make, make pack-pcp. The last step is driven by passing
variables like "PACKAGE_MAKER=Y" to enable OS-specific packaging.  So
in theory your Macpkg could be folded into Makepkgs.

max

<Prev in Thread] Current Thread [Next in Thread>