Re: openpkg 1.1.0 questions

2002-09-04 Thread Michael Schloh von Bennewitz

On Wed, Sep 04, 2002, Miles Egan wrote:
 It's still getting power macintosh from somewhere. The bootstrap script dies
 trying to run this command:

 uuencode openpkg-20020904-20020904.power macintosh-darwin6.0-pd.tar.Z

 Tracing it back it looks like it gets this string by running:

 rpm --eval %_target


Hello Miles, looking at the specfile for the openpkg package (bootstrapper),
we download config.guess from GNU and then use it when compiling RPM source
(also downloaded). It is very likely that GNU or Redhat have to put some
priority on Darwin to make this work. I hope it does work in the end, though.

From cvs.openpkg.org:/e/openpkg/cvs/openpkg-pkg/openpkg/openpkg.spec

  [...]
  Source2:  ftp://ftp.rpm.org/pub/rpm/dist/rpm-%{V_rpm}.x/rpm-%{V_rpm}.tar.gz
  [...]
  Source44: ftp://ftp.gnu.org/gnu/config/config.guess
  Source45: ftp://ftp.gnu.org/gnu/config/config.sub

-- 
[EMAIL PROTECTED]
Development Team, Application Services
Cable  Wireless Deutschland GmbH



msg00125/pgp0.pgp
Description: PGP signature


Re: openpkg 1.1.0 questions

2002-09-03 Thread Miles Egan

On Tue, Sep 03, 2002 at 11:59:22PM +0200, Michael Schloh von Bennewitz wrote:
 On Tue, Sep 03, 2002, Miles Egan wrote:
  uname -a:
 
  Darwin bunny.pixar.com 6.0 Darwin Kernel Version 6.0: Sat Jul 27 13:18:52 PDT
  2002; root:xnu/xnu-344.obj~1/RELEASE_PPC  Power Macintosh powerpc
 
  uname -m (the real offender):
  Power Macintosh
 
  unane -p:
  powerpc
 
  The rpm config.guess script translates uname -m to uname -p. Would this be
  reasonable to do in openpkg as well?
   
 Our 'shtool guessos' script does a little more than the standard RPM.
 Since there seems to be some variation in what I expect the bootstrapper
 to aknowlege from Darwin, lets be even more precise.
 
 I am attaching a close relative from the shtool script which is uuencoded
 into the bootstrapper. Please run 'shtool guessos' on your Darwin, and
 lets see what happens. I think it will report 'powerpc-apple-macos'. You
 might have to adjust the shell path after the shebang on the first line of
 the shtool script, of course. I am pretty unfamiliar with Darwin, but
 rather interested in any case. Good luck, and post the results to
 [EMAIL PROTECTED] I'm not posting this there, because I don't
 like MIME encoded mail on the mailing list.

Running shtool guessos gives me this output:

Power Macintosh-unknown-Darwin/6.0/Darwin Kernel Version 6.0: Sat Jul 27
13:18:52 PDT 2002; root:xnu/xnu-344.obj~1/RELEASE_PPC

Applying the following patch gives me powerpc-apple-darwin6.0, which is what
the config.guess script from rpm gives me.  Is this reasonable?

diff -u ./shtool /var/tmp/openpkg/shtool
--- ./shtoolTue Sep  3 15:40:00 2002
+++ /var/tmp/openpkg/shtool Tue Sep  3 15:47:22 2002
@@ -2529,6 +2529,9 @@
esac
echo ${MACHINE}-apple-rhapsody${RELEASE}; exit 0
;;
+Darwin:*:*:*)
+   echo `uname -p`-apple-darwin${RELEASE}; exit 0
+   ;;
 Mac OS:*:*:*)
MACHINE=`uname -p`
echo ${MACHINE}-apple-macos${RELEASE}; exit 0

-- 
miles egan
senior unix sysadmin
[EMAIL PROTECTED]
__
The OpenPKG Projectwww.openpkg.org
User Communication List  [EMAIL PROTECTED]



Re: openpkg 1.1.0 questions

2002-09-03 Thread Ralf S. Engelschall

On Tue, Sep 03, 2002, Miles Egan wrote:

 1.  Previous releases included make in the openpkg base package.  This no longer
 seems to be the case, at least in my builds.  Is this deliberate?

No, the bootstrapping package named openpkg never included GNU make --
not in 1.0 nor in any -CURRENT version.

 2.  Are there any plans for Os X / Darwin support?

Sure, as long as we have a machine available for porting. Unfortunately,
currently we have no PowerPC box available where we can setup MacOS X /
Darwin, hence we cannot do anything ourself here.

 The bootstrap procedure
 seems to work but the bootstrap package fails to install because the platform is
 identified as power macintosh and the space breaks the script.  What's the
 proper fix here?  Are there any hooks for munging/translating uname's output?

With 1.1.0 the bootstrap package's vendor parts use a common
config.guess/config.sub script. It is part of the package. All you have
to do is to fix your platform support there and this way all parts of
the bootstrap packaging should identify your platform correctly. But
make sure that you also forward your changes to the GNU people to make
sure your changes are not lost.

If you show me the output of

$ uname -a
$ uname -m
$ uname -s
$ uname -r

I can look for you into config.guess and try to help you...

   Ralf S. Engelschall
   [EMAIL PROTECTED]
   www.engelschall.com
__
The OpenPKG Projectwww.openpkg.org
User Communication List  [EMAIL PROTECTED]