You are viewing a plain text version of this content. The canonical link for it is here.
Posted to packagers@httpd.apache.org by Michael Felt <ma...@gmail.com> on 2012/02/01 19:08:22 UTC
test message: still not received a message from the list
testing after 20+ hours
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
Initially I have been using the embedded apr. My next thought was to look
at using having apr external.
So, I'll look into that 'earlier', rather than later.
On Mon, Feb 6, 2012 at 5:18 PM, Graham Leggett <mi...@sharp.fm> wrote:
> On 06 Feb 2012, at 4:51 PM, Michael Felt wrote:
>
> > I have used the same files for two builds (2.2.22 and 2.4.0).
> >
> > For some reason, 2.2.22 will not install to TEMPDIR without the build
> being installed in the "normal" area first.
> > With 2.4.0 the "make install TEMPDIR" command works, but I am getting
> several errors.
>
> Am I right in assuming that you're trying to build srclib/apr and
> srclib/apr-util inside the tree?
>
> If so, it probably won't work - both APR and APR-Util would need their own
> packaging, and would be installed first independently of httpd. I suspect
> this is where the install is going wrong.
>
> If you create similar build scripts for the APR and APR-Util projects
> following the same structure (you'll recognise a similar build directory),
> I can get those committed for you.
>
> Regards,
> Graham
> --
>
>
Re: AIX packaging
Posted by Graham Leggett <mi...@sharp.fm>.
On 06 Feb 2012, at 4:51 PM, Michael Felt wrote:
> I have used the same files for two builds (2.2.22 and 2.4.0).
>
> For some reason, 2.2.22 will not install to TEMPDIR without the build being installed in the "normal" area first.
> With 2.4.0 the "make install TEMPDIR" command works, but I am getting several errors.
Am I right in assuming that you're trying to build srclib/apr and srclib/apr-util inside the tree?
If so, it probably won't work - both APR and APR-Util would need their own packaging, and would be installed first independently of httpd. I suspect this is where the install is going wrong.
If you create similar build scripts for the APR and APR-Util projects following the same structure (you'll recognise a similar build directory), I can get those committed for you.
Regards,
Graham
--
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
I have used the same files for two builds (2.2.22 and 2.4.0).
For some reason, 2.2.22 will not install to TEMPDIR without the build being
installed in the "normal" area first.
With 2.4.0 the "make install TEMPDIR" command works, but I am getting
several errors.
Other difference between the two, largely because of code changes I expect:
So, for the same files to work on both versions:
2.2.22 and 2.4.0 require zlib and zlib-dev AIXToolbox, or equivalent
"Both" work better with coreutils installed (for /opt/freeware/bin/install)
2.4.0 requires that pcre-dev is installed.
With these installed no zlib-dir or pcre-dir options are required.
Current files are attached in a tar file.
On Mon, Feb 6, 2012 at 10:25 AM, Michael Felt <ma...@gmail.com> wrote:
> I had a similiar problem with the 2.3.16.beta distribution that was
> 'fixed' by instaling coreutils (and using the install from that instead
> (/opt/freeware/bin/install) of the AIX install (/usr/bin/install)
>
> I'll start the tests of 2.4.0 packaging directly - note I had different
> configure commands for both - so I'll be looking for a common one asap.
>
> messages - concise -
> + make > build/aix/make.out
> + make install DESTDIR=/var/tmp/root/httpd > build/aix/install.out
> mkdir /var/tmp/root/httpd
> mkdir /var/tmp/root/httpd/opt
> mkdir /var/tmp/root/httpd/opt/httpd
> mkdir /var/tmp/root/httpd/opt/httpd/lib
> mkdir /var/tmp/root/httpd/opt/httpd/bin
> mkdir /var/tmp/root/httpd/var
> mkdir /var/tmp/root/httpd/var/httpd
> mkdir /var/tmp/root/httpd/var/httpd/build
> mkdir /var/tmp/root/httpd/opt/httpd/lib/pkgconfig
> mkdir /var/tmp/root/httpd/opt/httpd/include
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/lib'
> libtool: install: warning: remember to run `libtool --finish
> /opt/httpd/lib'
> libtool: install: warning: relinking `libaprutil-1.la'
> cc: 1501-228 input file /opt/httpd/lib/libexpat.a not found
> cc: 1501-228 input file /opt/httpd/lib/libapr-1.so not found
> libtool: install: error: relink `libaprutil-1.la' with the above command
> before installing it
> make: 1254-004 The error code from the last command is 1.
>
>
> Stop.
> make: 1254-004 The error code from the last command is 1.
>
>
> Stop.
> make: 1254-004 The error code from the last command is 1.
>
>
> Stop.
> =====
> The missing files are available:
> find . | grep libexpat
> ./srclib/apr-util/xml/expat/libexpat.la
> ./srclib/apr-util/xml/expat/.libs/libexpat.exp
> ./srclib/apr-util/xml/expat/.libs/libexpat.so.0
> ./srclib/apr-util/xml/expat/.libs/libexpat.a
> ./srclib/apr-util/xml/expat/.libs/libexpat.lai
> ./srclib/apr-util/xml/expat/.libs/libexpat.la
> root@x105:[/data/prj/httpd-2.2.22]find . | grep libapr
> ./srclib/apr-util/libaprutil.dsp
> ./srclib/apr-util/libaprutil.rc
> ./srclib/apr-util/.libs/libaprutil-1.exp
> ./srclib/apr-util/.libs/libaprutil-1.so.0
> ./srclib/apr-util/.libs/libaprutil-1.so
> ./srclib/apr-util/.libs/libaprutil-1.a
> ./srclib/apr-util/.libs/libaprutil-1.lai
> ./srclib/apr-util/.libs/libaprutil-1.la
> ./srclib/apr-util/.libs/libaprutil-1.so.0.4.1
> ./srclib/apr-util/libaprutil-1.la
> ./srclib/apr/libapr.mak
> ./srclib/apr/libapr.dep
> ./srclib/apr/libapr.dsp
> ./srclib/apr/libapr.rc
> ./srclib/apr/build/libaprapp.dsp
> ./srclib/apr/build/libaprapp.dep
> ./srclib/apr/build/libaprapp.mak
> ./srclib/apr/build/prelibaprapp.dsp
> ./srclib/apr/.libs/libapr-1.exp
> ./srclib/apr/.libs/libapr-1.so.0.4.5
> ./srclib/apr/.libs/libapr-1.so.0
> ./srclib/apr/.libs/libapr-1.so
> ./srclib/apr/.libs/libapr-1.a
> ./srclib/apr/.libs/libapr-1.lai
> ./srclib/apr/.libs/libapr-1.la
> ./srclib/apr/libapr-1.la
>
>
>
> On Mon, Feb 6, 2012 at 9:48 AM, Michael Felt <ma...@gmail.com> wrote:
>
>> Yes, that was concern as well - unwelcome surprises.
>>
>>
>> On Mon, Feb 6, 2012 at 9:29 AM, Graham Leggett <mi...@sharp.fm> wrote:
>>
>>> On 06 Feb 2012, at 9:47 AM, Michael Felt wrote:
>>>
>>> > I am still not happy with having to run "make install" twice, as the
>>> make
>>> > install to TEMPDIR fails when it cannot find one of the libraries
>>> (looking
>>> > in /opt/httpd/lib - which might not be there)
>>>
>>> Can you confirm which libraries you're referring to? Libraries (like APR
>>> and friends) should be packaged separately from httpd, otherwise problems
>>> like this result. In this current case, one side effect of building the
>>> package is that the files get installed onto the build machine itself,
>>> without actually installing the package, and that is likely to surprise a
>>> lot of people.
>>>
>>> Regards,
>>> Graham
>>> --
>>>
>>>
>>
>
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
I had a similiar problem with the 2.3.16.beta distribution that was 'fixed'
by instaling coreutils (and using the install from that instead
(/opt/freeware/bin/install) of the AIX install (/usr/bin/install)
I'll start the tests of 2.4.0 packaging directly - note I had different
configure commands for both - so I'll be looking for a common one asap.
messages - concise -
+ make > build/aix/make.out
+ make install DESTDIR=/var/tmp/root/httpd > build/aix/install.out
mkdir /var/tmp/root/httpd
mkdir /var/tmp/root/httpd/opt
mkdir /var/tmp/root/httpd/opt/httpd
mkdir /var/tmp/root/httpd/opt/httpd/lib
mkdir /var/tmp/root/httpd/opt/httpd/bin
mkdir /var/tmp/root/httpd/var
mkdir /var/tmp/root/httpd/var/httpd
mkdir /var/tmp/root/httpd/var/httpd/build
mkdir /var/tmp/root/httpd/opt/httpd/lib/pkgconfig
mkdir /var/tmp/root/httpd/opt/httpd/include
libtool: install: warning: remember to run `libtool --finish /opt/httpd/lib'
libtool: install: warning: remember to run `libtool --finish /opt/httpd/lib'
libtool: install: warning: relinking `libaprutil-1.la'
cc: 1501-228 input file /opt/httpd/lib/libexpat.a not found
cc: 1501-228 input file /opt/httpd/lib/libapr-1.so not found
libtool: install: error: relink `libaprutil-1.la' with the above command
before installing it
make: 1254-004 The error code from the last command is 1.
Stop.
make: 1254-004 The error code from the last command is 1.
Stop.
make: 1254-004 The error code from the last command is 1.
Stop.
=====
The missing files are available:
find . | grep libexpat
./srclib/apr-util/xml/expat/libexpat.la
./srclib/apr-util/xml/expat/.libs/libexpat.exp
./srclib/apr-util/xml/expat/.libs/libexpat.so.0
./srclib/apr-util/xml/expat/.libs/libexpat.a
./srclib/apr-util/xml/expat/.libs/libexpat.lai
./srclib/apr-util/xml/expat/.libs/libexpat.la
root@x105:[/data/prj/httpd-2.2.22]find . | grep libapr
./srclib/apr-util/libaprutil.dsp
./srclib/apr-util/libaprutil.rc
./srclib/apr-util/.libs/libaprutil-1.exp
./srclib/apr-util/.libs/libaprutil-1.so.0
./srclib/apr-util/.libs/libaprutil-1.so
./srclib/apr-util/.libs/libaprutil-1.a
./srclib/apr-util/.libs/libaprutil-1.lai
./srclib/apr-util/.libs/libaprutil-1.la
./srclib/apr-util/.libs/libaprutil-1.so.0.4.1
./srclib/apr-util/libaprutil-1.la
./srclib/apr/libapr.mak
./srclib/apr/libapr.dep
./srclib/apr/libapr.dsp
./srclib/apr/libapr.rc
./srclib/apr/build/libaprapp.dsp
./srclib/apr/build/libaprapp.dep
./srclib/apr/build/libaprapp.mak
./srclib/apr/build/prelibaprapp.dsp
./srclib/apr/.libs/libapr-1.exp
./srclib/apr/.libs/libapr-1.so.0.4.5
./srclib/apr/.libs/libapr-1.so.0
./srclib/apr/.libs/libapr-1.so
./srclib/apr/.libs/libapr-1.a
./srclib/apr/.libs/libapr-1.lai
./srclib/apr/.libs/libapr-1.la
./srclib/apr/libapr-1.la
On Mon, Feb 6, 2012 at 9:48 AM, Michael Felt <ma...@gmail.com> wrote:
> Yes, that was concern as well - unwelcome surprises.
>
>
> On Mon, Feb 6, 2012 at 9:29 AM, Graham Leggett <mi...@sharp.fm> wrote:
>
>> On 06 Feb 2012, at 9:47 AM, Michael Felt wrote:
>>
>> > I am still not happy with having to run "make install" twice, as the
>> make
>> > install to TEMPDIR fails when it cannot find one of the libraries
>> (looking
>> > in /opt/httpd/lib - which might not be there)
>>
>> Can you confirm which libraries you're referring to? Libraries (like APR
>> and friends) should be packaged separately from httpd, otherwise problems
>> like this result. In this current case, one side effect of building the
>> package is that the files get installed onto the build machine itself,
>> without actually installing the package, and that is likely to surprise a
>> lot of people.
>>
>> Regards,
>> Graham
>> --
>>
>>
>
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
Yes, that was concern as well - unwelcome surprises.
On Mon, Feb 6, 2012 at 9:29 AM, Graham Leggett <mi...@sharp.fm> wrote:
> On 06 Feb 2012, at 9:47 AM, Michael Felt wrote:
>
> > I am still not happy with having to run "make install" twice, as the make
> > install to TEMPDIR fails when it cannot find one of the libraries
> (looking
> > in /opt/httpd/lib - which might not be there)
>
> Can you confirm which libraries you're referring to? Libraries (like APR
> and friends) should be packaged separately from httpd, otherwise problems
> like this result. In this current case, one side effect of building the
> package is that the files get installed onto the build machine itself,
> without actually installing the package, and that is likely to surprise a
> lot of people.
>
> Regards,
> Graham
> --
>
>
Re: AIX packaging
Posted by Graham Leggett <mi...@sharp.fm>.
On 06 Feb 2012, at 9:47 AM, Michael Felt wrote:
> I am still not happy with having to run "make install" twice, as the make
> install to TEMPDIR fails when it cannot find one of the libraries (looking
> in /opt/httpd/lib - which might not be there)
Can you confirm which libraries you're referring to? Libraries (like APR and friends) should be packaged separately from httpd, otherwise problems like this result. In this current case, one side effect of building the package is that the files get installed onto the build machine itself, without actually installing the package, and that is likely to surprise a lot of people.
Regards,
Graham
--
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
Hi,
I do not know how to download a r* update (yet), so personal patching was
the best alternative for me.
Also, I had found some 'shortcomings' in my previous scripts (when
'reusing' TEMPDIR rather than remaking it each time).
I also added a check for the AIX fileset needed, - do not start unless it
is there already :)
I am still not happy with having to run "make install" twice, as the make
install to TEMPDIR fails when it cannot find one of the libraries (looking
in /opt/httpd/lib - which might not be there)
This is not really a favorable solution - and I shall add a test for the
file (once I learn the name again) and
ask a yes/no question regarding how to proceed (do the install, or skip the
install to "real" area if the file already exists) - I'll want some advice
about alturnatives - under supposition that the live area is actually being
used - do not want to overwrite it.
Also, I am thinking, if ./Makefile already exists (or a better file?) to
skip the built-in ./configure command
and just run the make commands and then the mkinstallp.ksh (new name for
the 'packager' part, mkbuild.ksh is new name for the configure and make
part).
I'll mail the attachments separately, mail program refused then as too
large.
Michael
On Sun, Feb 5, 2012 at 10:16 PM, Graham Leggett <mi...@sharp.fm> wrote:
> On 05 Feb 2012, at 10:44 PM, Michael Felt wrote:
>
> > Sure - I'll assume it is build/aix/* and restart.
> >
> > I have a tested set with ssl enabled, which is what I shall make, and I
> can
> > include a result.
>
> The changes are a lot easier to apply as unified diffs - the easiest way
> to create them is to check out the code, and then use "svn diff" to produce
> the patch.
>
> > The Solaris packaging put the result in the root directory, I was placing
> > it in the build/aix directory.
> > Any preference?
>
> It's up to you, each type of packaging works differently, there isn't a
> one-size-fits-all anywhere.
>
> Regards,
> Graham
> --
>
>
Re: AIX packaging
Posted by Graham Leggett <mi...@sharp.fm>.
On 05 Feb 2012, at 10:44 PM, Michael Felt wrote:
> Sure - I'll assume it is build/aix/* and restart.
>
> I have a tested set with ssl enabled, which is what I shall make, and I can
> include a result.
The changes are a lot easier to apply as unified diffs - the easiest way to create them is to check out the code, and then use "svn diff" to produce the patch.
> The Solaris packaging put the result in the root directory, I was placing
> it in the build/aix directory.
> Any preference?
It's up to you, each type of packaging works differently, there isn't a one-size-fits-all anywhere.
Regards,
Graham
--
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
Sure - I'll assume it is build/aix/* and restart.
I have a tested set with ssl enabled, which is what I shall make, and I can
include a result.
The Solaris packaging put the result in the root directory, I was placing
it in the build/aix directory.
Any preference?
Michael
On Sun, Feb 5, 2012 at 8:28 PM, Graham Leggett <mi...@sharp.fm> wrote:
> On 02 Feb 2012, at 7:57 PM, Michael Felt wrote:
>
> > Updated. removed some bad comments (configure never got run), and added
> README.aix
>
> I have committed it in r1240778.
>
> One of the things I had to change was the directory base, the "pkg"
> directory belongs to Solaris packaging, which creates "pkg" packages. I
> updated the scripts to refer to "aix" instead. Would it be possible to
> sanity check this and check it all still works ok? I don't have any access
> to an AIX box to test this.
>
> Regards,
> Graham
> --
>
>
Re: AIX packaging
Posted by Graham Leggett <mi...@sharp.fm>.
On 02 Feb 2012, at 7:57 PM, Michael Felt wrote:
> Updated. removed some bad comments (configure never got run), and added README.aix
I have committed it in r1240778.
One of the things I had to change was the directory base, the "pkg" directory belongs to Solaris packaging, which creates "pkg" packages. I updated the scripts to refer to "aix" instead. Would it be possible to sanity check this and check it all still works ok? I don't have any access to an AIX box to test this.
Regards,
Graham
--
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
Updated. removed some bad comments (configure never got run), and added
README.aix
On Thu, Feb 2, 2012 at 3:01 PM, Michael Felt <ma...@gmail.com> wrote:
> I so wish I could also see the packagers list ... have a request out to
> the admins to look into the problem...
>
> Thank you Graham for adding this initially to dev (or to me as well).
>
>
> On Thu, Feb 2, 2012 at 2:59 PM, Michael Felt <ma...@gmail.com> wrote:
>
>> yes, README, is needed of course, but it is the same as for the
>> buildpkg.sh script.
>> Be in the httpd project root and execute build/pkg/buildaix.ksh
>>
>> I am going to make a modification (install the zlib developer rpm that is
>> part of the standard AIX toolbox, so readly available, and add the the AIX
>> fileset bos.adt.insttools is needed as well.
>>
>> (README coming soon)
>>
>>
>> On Thu, Feb 2, 2012 at 11:54 AM, Graham Leggett <mi...@sharp.fm> wrote:
>>
>>> On 02 Feb 2012, at 12:40 AM, Michael Felt wrote:
>>>
>>> > a tar file with buildaix.ksh (to do the build), aixproto.ksh (to
>>> create a very simple AIX template and create an installable image, and
>>> lastly, an example of a new layout for AIX (which I used for this
>>> packaging).
>>>
>>> Would it be possible to put together a brief README to go in the same
>>> directory giving an example of how to use the scripts?
>>>
>>> In the mean time, let me commit the layout for you, that seems fine.
>>>
>>> Regards,
>>> Graham
>>> --
>>>
>>>
>>
>
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
Updated. removed some bad comments (configure never got run), and added
README.aix
On Thu, Feb 2, 2012 at 3:01 PM, Michael Felt <ma...@gmail.com> wrote:
> I so wish I could also see the packagers list ... have a request out to
> the admins to look into the problem...
>
> Thank you Graham for adding this initially to dev (or to me as well).
>
>
> On Thu, Feb 2, 2012 at 2:59 PM, Michael Felt <ma...@gmail.com> wrote:
>
>> yes, README, is needed of course, but it is the same as for the
>> buildpkg.sh script.
>> Be in the httpd project root and execute build/pkg/buildaix.ksh
>>
>> I am going to make a modification (install the zlib developer rpm that is
>> part of the standard AIX toolbox, so readly available, and add the the AIX
>> fileset bos.adt.insttools is needed as well.
>>
>> (README coming soon)
>>
>>
>> On Thu, Feb 2, 2012 at 11:54 AM, Graham Leggett <mi...@sharp.fm> wrote:
>>
>>> On 02 Feb 2012, at 12:40 AM, Michael Felt wrote:
>>>
>>> > a tar file with buildaix.ksh (to do the build), aixproto.ksh (to
>>> create a very simple AIX template and create an installable image, and
>>> lastly, an example of a new layout for AIX (which I used for this
>>> packaging).
>>>
>>> Would it be possible to put together a brief README to go in the same
>>> directory giving an example of how to use the scripts?
>>>
>>> In the mean time, let me commit the layout for you, that seems fine.
>>>
>>> Regards,
>>> Graham
>>> --
>>>
>>>
>>
>
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
I so wish I could also see the packagers list ... have a request out to the
admins to look into the problem...
Thank you Graham for adding this initially to dev (or to me as well).
On Thu, Feb 2, 2012 at 2:59 PM, Michael Felt <ma...@gmail.com> wrote:
> yes, README, is needed of course, but it is the same as for the
> buildpkg.sh script.
> Be in the httpd project root and execute build/pkg/buildaix.ksh
>
> I am going to make a modification (install the zlib developer rpm that is
> part of the standard AIX toolbox, so readly available, and add the the AIX
> fileset bos.adt.insttools is needed as well.
>
> (README coming soon)
>
>
> On Thu, Feb 2, 2012 at 11:54 AM, Graham Leggett <mi...@sharp.fm> wrote:
>
>> On 02 Feb 2012, at 12:40 AM, Michael Felt wrote:
>>
>> > a tar file with buildaix.ksh (to do the build), aixproto.ksh (to create
>> a very simple AIX template and create an installable image, and lastly, an
>> example of a new layout for AIX (which I used for this packaging).
>>
>> Would it be possible to put together a brief README to go in the same
>> directory giving an example of how to use the scripts?
>>
>> In the mean time, let me commit the layout for you, that seems fine.
>>
>> Regards,
>> Graham
>> --
>>
>>
>
Re: AIX packaging
Posted by Michael Felt <ma...@gmail.com>.
yes, README, is needed of course, but it is the same as for the buildpkg.sh
script.
Be in the httpd project root and execute build/pkg/buildaix.ksh
I am going to make a modification (install the zlib developer rpm that is
part of the standard AIX toolbox, so readly available, and add the the AIX
fileset bos.adt.insttools is needed as well.
(README coming soon)
On Thu, Feb 2, 2012 at 11:54 AM, Graham Leggett <mi...@sharp.fm> wrote:
> On 02 Feb 2012, at 12:40 AM, Michael Felt wrote:
>
> > a tar file with buildaix.ksh (to do the build), aixproto.ksh (to create
> a very simple AIX template and create an installable image, and lastly, an
> example of a new layout for AIX (which I used for this packaging).
>
> Would it be possible to put together a brief README to go in the same
> directory giving an example of how to use the scripts?
>
> In the mean time, let me commit the layout for you, that seems fine.
>
> Regards,
> Graham
> --
>
>
AIX packaging
Posted by Graham Leggett <mi...@sharp.fm>.
On 02 Feb 2012, at 12:40 AM, Michael Felt wrote:
> a tar file with buildaix.ksh (to do the build), aixproto.ksh (to create a very simple AIX template and create an installable image, and lastly, an example of a new layout for AIX (which I used for this packaging).
Would it be possible to put together a brief README to go in the same directory giving an example of how to use the scripts?
In the mean time, let me commit the layout for you, that seems fine.
Regards,
Graham
--
Re: test message: still not received a message from the list
Posted by Michael Felt <ma...@gmail.com>.
should have changed the subject, i.e. started over - but probably have all
see the other posts anyway ;)
On Wed, Feb 1, 2012 at 10:40 PM, Michael Felt <ma...@gmail.com> wrote:
> That is the idea I believe.
>
> My first submission (also to dev@ as I still do not see packagers@)
>
> a tar file with buildaix.ksh (to do the build), aixproto.ksh (to create a
> very simple AIX template and create an installable image, and lastly, an
> example of a new layout for AIX (which I used for this packaging).
>
>
>
>
>
>
> On Wed, Feb 1, 2012 at 7:51 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>
>> I, for one, wish that the packagers@ list was more active. I think it
>> would solve many problems of inter-platform differences. And, after all, I
>> started the list myself for that reason. But, alas, the list has gotten no
>> traction at all, although I've personally invited a large number of package
>> managers.
>>
>> Welcome, and perhaps we can start a conversation! :)
>>
>> On Feb 1, 2012, at 2:32 PM, Michael Felt wrote:
>>
>> William Rowe suggested it, that I "discuss" a layout for AIX here, rather
>> than in dev.
>>
>> He is looking into it. At least I know for sure that I am not mistyping
>> the email address. Thanks for the reply,
>>
>> Michael
>>
>> On Wed, Feb 1, 2012 at 6:16 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>>
>>> I have received all three of your messages, but I'm not sure what,
>>> exactly, you're testing. This list is mostly dead.
>>>
>>> On Feb 1, 2012, at 1:08 PM, Michael Felt wrote:
>>>
>>> testing after 20+ hours
>>>
>>>
>>> --
>>> Rich Bowen
>>> rbowen@rcbowen.com :: @rbowen
>>> rbowen@apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> Rich Bowen
>> rbowen@rcbowen.com :: @rbowen
>> rbowen@apache.org
>>
>>
>>
>>
>>
>>
>>
>
AIX packaging
Posted by Graham Leggett <mi...@sharp.fm>.
On 02 Feb 2012, at 12:40 AM, Michael Felt wrote:
> a tar file with buildaix.ksh (to do the build), aixproto.ksh (to create a very simple AIX template and create an installable image, and lastly, an example of a new layout for AIX (which I used for this packaging).
Would it be possible to put together a brief README to go in the same directory giving an example of how to use the scripts?
In the mean time, let me commit the layout for you, that seems fine.
Regards,
Graham
--
Re: test message: still not received a message from the list
Posted by Michael Felt <ma...@gmail.com>.
That is the idea I believe.
My first submission (also to dev@ as I still do not see packagers@)
a tar file with buildaix.ksh (to do the build), aixproto.ksh (to create a
very simple AIX template and create an installable image, and lastly, an
example of a new layout for AIX (which I used for this packaging).
On Wed, Feb 1, 2012 at 7:51 PM, Rich Bowen <rb...@rcbowen.com> wrote:
> I, for one, wish that the packagers@ list was more active. I think it
> would solve many problems of inter-platform differences. And, after all, I
> started the list myself for that reason. But, alas, the list has gotten no
> traction at all, although I've personally invited a large number of package
> managers.
>
> Welcome, and perhaps we can start a conversation! :)
>
> On Feb 1, 2012, at 2:32 PM, Michael Felt wrote:
>
> William Rowe suggested it, that I "discuss" a layout for AIX here, rather
> than in dev.
>
> He is looking into it. At least I know for sure that I am not mistyping
> the email address. Thanks for the reply,
>
> Michael
>
> On Wed, Feb 1, 2012 at 6:16 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>
>> I have received all three of your messages, but I'm not sure what,
>> exactly, you're testing. This list is mostly dead.
>>
>> On Feb 1, 2012, at 1:08 PM, Michael Felt wrote:
>>
>> testing after 20+ hours
>>
>>
>> --
>> Rich Bowen
>> rbowen@rcbowen.com :: @rbowen
>> rbowen@apache.org
>>
>>
>>
>>
>>
>>
>>
>
> --
> Rich Bowen
> rbowen@rcbowen.com :: @rbowen
> rbowen@apache.org
>
>
>
>
>
>
>
Re: test message: still not received a message from the list
Posted by Michael Felt <ma...@gmail.com>.
That is the idea I believe.
My first submission (also to dev@ as I still do not see packagers@)
a tar file with buildaix.ksh (to do the build), aixproto.ksh (to create a
very simple AIX template and create an installable image, and lastly, an
example of a new layout for AIX (which I used for this packaging).
On Wed, Feb 1, 2012 at 7:51 PM, Rich Bowen <rb...@rcbowen.com> wrote:
> I, for one, wish that the packagers@ list was more active. I think it
> would solve many problems of inter-platform differences. And, after all, I
> started the list myself for that reason. But, alas, the list has gotten no
> traction at all, although I've personally invited a large number of package
> managers.
>
> Welcome, and perhaps we can start a conversation! :)
>
> On Feb 1, 2012, at 2:32 PM, Michael Felt wrote:
>
> William Rowe suggested it, that I "discuss" a layout for AIX here, rather
> than in dev.
>
> He is looking into it. At least I know for sure that I am not mistyping
> the email address. Thanks for the reply,
>
> Michael
>
> On Wed, Feb 1, 2012 at 6:16 PM, Rich Bowen <rb...@rcbowen.com> wrote:
>
>> I have received all three of your messages, but I'm not sure what,
>> exactly, you're testing. This list is mostly dead.
>>
>> On Feb 1, 2012, at 1:08 PM, Michael Felt wrote:
>>
>> testing after 20+ hours
>>
>>
>> --
>> Rich Bowen
>> rbowen@rcbowen.com :: @rbowen
>> rbowen@apache.org
>>
>>
>>
>>
>>
>>
>>
>
> --
> Rich Bowen
> rbowen@rcbowen.com :: @rbowen
> rbowen@apache.org
>
>
>
>
>
>
>