Depfinder problem

[Sasquatch]

Not specifically a Salix problem I suppose. But I can't get depfinder to output to a file. I type;

Code: Select all

depfinder -f /path/to/program

with various changes at the end and it always prints to STDOUT. I've tried adding

Code: Select all

> file.txt
>> file.txt
> file.dep
> file

and probably a few other variations and it always prints to the screen instead of a file. I end up with an empty txt file in the working directory. What am I doing wrong? The wiki just says it normally outputs to a .dep file, it doesn't say whether there's anything more to the syntax than just adding the '-f'.

[mimosa]

Have a look at the depfinder man page. Are you pointing it at packages?

[Sasquatch]

Depfinder isn't having a problem reading the packages. It's the output that isn't cooperating. the -f option is not sending the output to a file. And the man pages don't say anything more than 'use -f to output a file'. The expected shell syntax;

Code: Select all

depfinder -f <package.txz> > file.txt

does not work. Nor do any of the variations I've tried. The man pages and '--help' don't specify a different syntax.


*EDIT*

I wonder if there's something missing from the core install that is required for it to print to a file? I would think the core install would have all the necessary shell commands and programs, but maybe not. I just tried sending 'ls' to a txt file and it worked fine. Maybe depfinder has some other requirements that are not met.

[mimosa]

That isn't how it works - have a look at the section of the man page on the -f switch. You should find a .dep file in the directory where you called depfinder. Because you used the -f switch, the output you sent to file.txt is empty.

To just see the dependenccies, call depfinder with no switch.

The redirection would work if you didn't use the switch. The advantage of -f is it creates an appropriately named file.

[Sasquatch]

Seems the problem was somewhat unrelated to the -f switch. I was using depfinder to look for the dependencies of Network Manager. It errored out, saying the package needs libraries not found in the system. So it doesn't print the file and it does show the STDERR output... so the -f switch was ignored rather than malfunctioning. The switch works as advertised when I use it on a package that has libraries available. I suppose that leaves it up to me to figure out which packages have those libraries.

[mimosa]

Again, see the man page:

You need to have all required dependencies for any package you run depfinder on installed in your system. That will of course always be the case
when you are building your own packages. In case there is a library that is required by a package you run depfinder on that is missing from your
system, depfinder will report the missing library and will not generate a dependency list.

You can find the dependencies of Salix packages in the repositories, that is, a .dep file in the same location as the package itself.