Not sure why your version of install doesn't support the standard options but you can just manually copy the podget bash script to /usr/local/bin/podget.
And then gzip the man page (gzip -9 < DOC/podget.7 > podget.7.gz) and copy it to /usr/local/share/man/man7/podget.7.gz.
Thats all the Makefile does.
Enjoy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-08-21
Logged In: YES
user_id=1387013
Originator: YES
ok, was finally able to run podget by setting the dir_library variable manually at the command line, and then specifying bash as the shell interpreter.
at which point the script start executing, and then I get seventeen of these errors:
/usr/local/bin/podget: line 363: export: `=': not a valid identifier
line 363 of the /usr/local/bin/podget script is as follows:
eval export $var2set='$set2var'
I think this has something to do with a discrepancy between the version of sed that is included with OpenBSD, and the one found on most linux distributions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-08-21
Logged In: YES
user_id=1387013
Originator: YES
Also I believe this instruction to be incorrect for OpenBSD systems:
And then gzip the man page (gzip -9 < DOC/podget.7 > podget.7.gz) and copy
it to /usr/local/share/man/man7/podget.7.gz.
I tried the step above, and it did not add podget into the man page directories
in the default search path.
Based on where the gnupg package installs the man page file, I believe the proper directory to copy the manpage file is /usr/local/man/man7/
Also the file podget.7 should not be gzipped beforehand.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-08-23
status: closed --> open
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-08-23
Logged In: YES
user_id=1387013
Originator: YES
Ok, latest version of CVS makefile has fixed the long option install error.
However there still exists the issue(s) of the podget man page file being installed into a non-standard location for OpenBSD. TTBOMK, man pages for software that is not part of the base system belong in /usr/local/man and are not gzipped.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-08-23
Logged In: YES
user_id=1387013
Originator: YES
Ok, just downloaded and install cvs version 1.32 of podget on a fresh OpenBSD 4.1 system.
Installation works, and the switch to "#!/usr/bin/env" eliminated my need to create a softlink for /bin/bash to /usr/local/bin/bash on my system.
Man page is still in the wrong place and format, but that's not a show stopper.
When I got to run podget for the first time, here is what happens. I think the problem has to do with some semantical differences in the sed command between linux and BSD platforms.
podget
First Run. Installing user configuration files.
Configuration directory not found. Creating /home/seth/.podget
sed: unknown option -- -
usage: sed script [-an] [file ...]
sed [-an] [-e script] ... [-f script_file] ... [file ...]
sed: unknown option -- -
usage: sed script [-an] [file ...]
sed [-an] [-e script] ... [-f script_file] ... [file ...]
Session file not found. Creating.
Downloading a single item from each default server to test configuration.
LIBRARY DIR:
ERROR - Library directory not defined.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-08-23
Logged In: YES
user_id=1387013
Originator: YES
ok, couple of issues.
1) When I run podget for the first time, I get the sed error, and the default podgetrc config file in $HOME/.podget is empty (blank)
2) When I copy a working $HOME/.podget/podgetrc file over from my ubuntu box, and run podget on my Obsd computer, I am still a dozen or so of these errors
/usr/local/bin/podget: line 426: export: `=': not a valid identifier
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1387013
Originator: YES
ok, I was able to fix the install problems by editing the Makefile and changing the --mode switches to -m.
Now when I run the podget executable however, I get the follow error:
host:/home/user$ podget
ksh: podget: No such file or directory
host:/home/user$
Logged In: YES
user_id=371080
Originator: NO
Not sure why your version of install doesn't support the standard options but you can just manually copy the podget bash script to /usr/local/bin/podget.
And then gzip the man page (gzip -9 < DOC/podget.7 > podget.7.gz) and copy it to /usr/local/share/man/man7/podget.7.gz.
Thats all the Makefile does.
Enjoy.
Logged In: YES
user_id=1387013
Originator: YES
ok, was finally able to run podget by setting the dir_library variable manually at the command line, and then specifying bash as the shell interpreter.
env dir_library=/home/seth bash /usr/local/bin/podget
at which point the script start executing, and then I get seventeen of these errors:
/usr/local/bin/podget: line 363: export: `=': not a valid identifier
line 363 of the /usr/local/bin/podget script is as follows:
eval export $var2set='$set2var'
I think this has something to do with a discrepancy between the version of sed that is included with OpenBSD, and the one found on most linux distributions.
Logged In: YES
user_id=1387013
Originator: YES
Also I believe this instruction to be incorrect for OpenBSD systems:
And then gzip the man page (gzip -9 < DOC/podget.7 > podget.7.gz) and copy
it to /usr/local/share/man/man7/podget.7.gz.
I tried the step above, and it did not add podget into the man page directories
in the default search path.
Based on where the gnupg package installs the man page file, I believe the proper directory to copy the manpage file is /usr/local/man/man7/
Also the file podget.7 should not be gzipped beforehand.
Logged In: YES
user_id=1387013
Originator: YES
Ok, latest version of CVS makefile has fixed the long option install error.
However there still exists the issue(s) of the podget man page file being installed into a non-standard location for OpenBSD. TTBOMK, man pages for software that is not part of the base system belong in /usr/local/man and are not gzipped.
Logged In: YES
user_id=1387013
Originator: YES
Ok, just downloaded and install cvs version 1.32 of podget on a fresh OpenBSD 4.1 system.
Installation works, and the switch to "#!/usr/bin/env" eliminated my need to create a softlink for /bin/bash to /usr/local/bin/bash on my system.
Man page is still in the wrong place and format, but that's not a show stopper.
When I got to run podget for the first time, here is what happens. I think the problem has to do with some semantical differences in the sed command between linux and BSD platforms.
podget
First Run. Installing user configuration files.
Configuration directory not found. Creating /home/seth/.podget
sed: unknown option -- -
usage: sed script [-an] [file ...]
sed [-an] [-e script] ... [-f script_file] ... [file ...]
sed: unknown option -- -
usage: sed script [-an] [file ...]
sed [-an] [-e script] ... [-f script_file] ... [file ...]
Session file not found. Creating.
Downloading a single item from each default server to test configuration.
LIBRARY DIR:
ERROR - Library directory not defined.
Logged In: YES
user_id=1387013
Originator: YES
ok, couple of issues.
1) When I run podget for the first time, I get the sed error, and the default podgetrc config file in $HOME/.podget is empty (blank)
2) When I copy a working $HOME/.podget/podgetrc file over from my ubuntu box, and run podget on my Obsd computer, I am still a dozen or so of these errors
/usr/local/bin/podget: line 426: export: `=': not a valid identifier