Free Downloads, Community Forum,
FAQs and Developer Resources


Make /Tools Your Home | Link to us

Today's posts | Posts since last visit | Most Active Topics

All Forums Register Login Search Subscriptions My Profile Inbox
Tool Warehouse FAQs Resources Help Member List Address Book Logout

pkg-current-bin35.sh (pkg-2.5.1) broken ?

 
Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [SFU / Interix / SUA Technology] >> SFU / Interix - Getting Started >> pkg-current-bin35.sh (pkg-2.5.1) broken ? Page: [1]
Login
Message << Older Topic   Newer Topic >>
pkg-current-bin35.sh (pkg-2.5.1) broken ? - Apr. 10, '06, 8:58:05 AM   
haubi

 

Posts: 1
Joined: Apr. 6, '06,
Status: offline
Hi,

when bootstrapping with pkg-current-bin35.sh (as of pkg-2.5.1), i end up with no pkg_* in /usr/local/bin/ at all.

$ ./pkg-current-bin35.sh
<snip>
 the bottom of page http://www.interopsystems.com/tools/pkg_install.htm

 Press Enter to continue or ^C to cancel.


 Now in directory  /usr/local/packages  extracting the file
 Please wait...

tar: Removing leading / from absolute path names in the archive
usr/local/bin/pkg_add
usr/local/bin/pkg_create
<snip>
var/db/pkg/env_manpath_local-1.0.7-bin/+DESC
var/db/pkg/env_manpath_local-1.0.7-bin/+REQUIRED_BY

 Installation of software completed.
<snip>
 Would you like to update now? (y/n)[y]
 Using 'pkg_add' to get the update of 'pkg' (the installer).
 This will take a couple of minutes...
./pkg-current-bin35.sh[244]: /usr/local/bin/pkg_add: not found
 Finished getting the update for 'pkg'.

 Done.
$

After some digging, i found the expected files extracted into /tmp/{bin,usr,var}/

So i applied this patch to pkg-current-bin35.sh to get it working as expected:
@@ -144,7 +144,8 @@
 
 # umask adjusted here with purpose for 'tar' running
 umask 2
-/tmp/tar xvpf pkg-${ver}-bin35.tar
+cd /
+/tmp/tar xvpf /tmp/pkg-${ver}-bin35.tar
 
 if [ ! -e /usr/local/share/terminfo ]; then
        /bin/mkdir -p /usr/local/share

Is this the fix for my problem, or did i miss something ?

-- haubi
Post #: 1
RE: pkg-current-bin35.sh (pkg-2.5.1) broken ? - Apr. 10, '06, 12:52:00 PM   
Rodney

 

Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
To me it reads that you installed some other version of tar that doesn't
allow for the archives to have absolute paths. There was a period of time where
the BSD* OS's did this and then came back to traditional behavior (this is several
years back now). It reads to me that you installed/clobbered the /bin/tar that
ships with another version that has different behavior.
For the packaging system to work the shipped /bin/tar does gets replaced, but with
an extended version of tar (same base behavior). So don't clobber it.

(in reply to haubi)
Post #: 2
Page:   [1]
All Forums >> [SFU / Interix / SUA Technology] >> SFU / Interix - Getting Started >> pkg-current-bin35.sh (pkg-2.5.1) broken ? Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Search All Forums -

Advanced search


SPONSORS



Forum Software © ASPPlayground.NET Advanced Edition 2.5 ANSI

0.031