I guess the simple start will be to use example A:
Ex 1: PkgA - single fileset with no requisites
----------------------------------------------
Directory Structure:
/tmp/packages
/tmp/packages/usr/doc/PkgA/README
/tmp/packages/usr/PkgA/bin/acommand
Template File:
Package Name: aix.apache
Package VRMF: 2.2.14.0
Update: N
Fileset
Fileset Name: aix.apache2.rte
Fileset VRMF: 2.2.14.0
Fileset Description: Apache runtime fileset
Bosboot required: N
License agreement acceptance required: N
Include license files in this package: N
Requisites:
USRFiles
/usr/doc/PkgA
/usr/doc/PkgA/README
/usr/PkgA
/usr/PkgA/bin
/usr/PkgA/bin/acommand
EOUSRFiles
ROOT Part: N
ROOTFiles
EOROOTFiles
EOFileset
=====
So, what do I need to do with the .spec file, if anything, to create a
/tmp/packing area. I was thinking, as an initial test, to jst creating a
symbolic link from /usr/local to /tmp/package and seeing what the contents
are - and package those. Or am I being much too simple minded?
Or, not having looked at it yet - should I be focusing on a replacement for
rpmbuild (assuming it is a script)?
Michael
On Wed, Oct 7, 2009 at 10:33 PM, Michael Felt <mamf...@gmail.com> wrote:
> And then some links into IBM:
>
> http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.install/doc/insgdrf/sw_pkg_creation.htm
>
> http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mkinstallp.htm
>
> And the example file mentioned is attached (
> /usr/lpp/bos/README.MKINSTALLP)
>
>
> On Wed, Oct 7, 2009 at 10:02 PM, Michael Felt <mamf...@gmail.com> wrote:
>
>> A sample of instructions I would follow are here:
>> http://pware.hvcc.edu/PwarePackagingGuide.pdf. I just do not intend to
>> call it pware.* but something different. Naming is so hard!
>>
>>
>> On Wed, Oct 7, 2009 at 9:56 PM, Michael Felt <mamf...@gmail.com> wrote:
>>
>>> I'll have to look into the exact format of the files to make it something
>>> the AIX installer can work with - these are extra files.
>>>
>>> bff stands for backup file format. rather than being a tarball it is a
>>> file created by backup (backupbyfilename).
>>>
>>> a rough approximation of how the file would be created is:
>>> cd ${SOME_ROOTDIR}
>>> find . | backup -if <PackageName>.bff
>>>
>>> ## "backup -i" means read standard inout for the names of files to
>>> backup.
>>>
>>>
>>> On Wed, Oct 7, 2009 at 9:49 PM, Graham Leggett <minf...@sharp.fm> wrote:
>>>
>>>> Michael Felt wrote:
>>>>
>>>> > New question: that will mean homework I suspect.
>>>> >
>>>> > As I mentioned before, I am interested in creating a build that other
>>>> > people could install. Having one is the only way to see how big a
>>>> need,
>>>> > if any exists, for a prebuilt AIX opensource httpd server.
>>>> >
>>>> > I suppose I could go for a RPM build - maybe all I need is on AIX by
>>>> > default, and perhaos it is the first step to learning what needs to be
>>>> > done.
>>>> >
>>>> > My preference is to create a .bff (or installp) format.
>>>> >
>>>> > I have found the build/rpm directory, and what seems to be the actual
>>>> > file intended: ./httpd.spec
>>>> >
>>>> > Question is: How do I use this file, and maybe modify it, to create a
>>>> > specification for an AIX binary distribution?
>>>>
>>>> The basic pattern for rpm is that if a file called <tarballname>.spec
>>>> exists in the tarball, then that spec file is used as a recipe to build
>>>> the RPM when you go rpmbuild -tb <tarball>.tar.bz2.
>>>>
>>>> The recipe contains three things, metadata about the package (name,
>>>> version, description, other stuff), scripts used to build the package
>>>> and perform pre and post installation, and a list of files in the rpm.
>>>>
>>>> The buildconf script builds the httpd.spec file from httpd.spec.in,
>>>> inserting the version number and other details into the file. The result
>>>> is that when a tarball is rolled, a file called httpd.spec exists in the
>>>> right place containing the right names, MMNs and version numbers.
>>>>
>>>> Do you have an example of how a .bff file is built?
>>>>
>>>> Regards,
>>>> Graham
>>>> --
>>>>
>>>
>>>
>>
>
