[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: list of all prerequisites/ dependencies on a package
On Thursday 2022-04-14 01:59, Roland Illig wrote:
Am 14.04.2022 um 00:04 schrieb Roland Illig:
Am 13.04.2022 um 17:36 schrieb J. Lewis Muir:
On 04/08, Roland Illig wrote:
There should be a cleaner way of listing all of a package's
dependencies. My first idea was to define a target named
'show-all-depends', but that name is already used as part of 'show-all'.
Therefore I suggest 'show-depends-all'.
Please, not that name, though. Not that there's anything wrong with
it on its own, but this would make for two targets that only differ in
the order of two words, and I think most people would not be able to
remember which is which.
Makes sense. My preferred name would have been 'show-all-transitive',
but there is already prior art in the form of 'fetch-list-recursive',
which also uses _DEPENDS_WALK_CMD, so I went with 'show-all-recursive'.
Oops, I made some typos in the above paragraph. Of course, I meant
'show-depends-transitive' and 'show-depends-recursive'. In the code, I
used the correct names.
Is there a way to create for every package in pkgsrc a
package-name-depends list that I may store on my machine for when I need
to find the dependentcies. I guess a pre-view? I would then know in
advance which packages need building to get a desired application like
Java. Even better, doing so in order would reduce build failures that
are hard to track down because of an issue in an earlier build.
Boyd Gerber <gerberb%zenez.com@localhost> 801 849-0213
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
Main Index |
Thread Index |