Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8243 - hidden deps not shown - a tool to find *all* deps is needed

Attached to Project: Arch Linux
Opened by Andreas Radke (AndyRTR) - Sunday, 07 October 2007, 12:16 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 01 September 2010, 08:40 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To Pierre Schmitz (Pierre)
Aaron Griffin (phrakture)
Architecture All
Severity Low
Priority Normal
Reported Version 1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Wednesday, 01 September 2010, 08:40 GMT
Reason for closing:  Implemented
Additional comments about closing:  sogrep from https://git.archlinux.de/repo-tools.git/
Comment by Aaron Griffin (phrakture) - Sunday, 07 October 2007, 12:24 GMT
Just to clarify, you want recursive dependencies?

Or do we want recursive _reverse_ dependencies?

That is... do you want libpcap and all depends OF libpcap, or all packages that DEPEND ON libpcap?
Comment by Andreas Radke (AndyRTR) - Sunday, 07 October 2007, 16:28 GMT
all packages that DEPEND ON libpcap - for the rebuild list

the other way round is (almost) well covered by namcap.
Comment by Jason Chu (jason) - Sunday, 07 October 2007, 19:39 GMT
The other way around *is* covered by namcap: namcap -i -r depends <package>

Something to walk the dependency tree in the other direction wouldn't be that bad, even if you just had the PKGBUILDs.
Comment by Aaron Griffin (phrakture) - Monday, 08 October 2007, 16:07 GMT
I almost think this should be namcap's territory too. I mean, we already have all this neat parsing and code there.

Might be best to look into writing a namcap rule for this first.
Comment by Jason Chu (jason) - Monday, 08 October 2007, 17:44 GMT
Hmmm... it's probably not something you'd want to run every single time though. As it stands, all applicable rules for the input type (PKGBUILD or package) are run when it processes that type. Can you think of a good interface to automatically not have that rule run? and an easy enough interface to remember when you want to run it...
Comment by Aaron Griffin (phrakture) - Monday, 08 October 2007, 21:18 GMT
Right right - I meant an optional rule with the errrr -r argument.

I think we could use that option a lot more than we do (most people don't even know it exists)
Comment by Jason Chu (jason) - Monday, 08 October 2007, 21:37 GMT
Yeah, I think that's fair enough. I'll just figure out a way to discern between optional rules and default rules and we should be good to go.
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 30 August 2010, 22:59 GMT
@Pierre: I guess that this old task can be closed. You have a tool that find deps in ELF.
Comment by Pierre Schmitz (Pierre) - Tuesday, 31 August 2010, 04:28 GMT
Indeed: We can use sogrep from https://git.archlinux.de/repo-tools.git/
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 31 August 2010, 06:20 GMT
Thanks. So this task can be closed.

Loading...