On 03/05/10 17:14, Anselm Strauss wrote:
That gives me some static information on the ports requirements. But I
would like a preview of what rests to be done. Some ports have a lot of
dependencies, most of them are already installed. Can ports also
incorporate the current state of installed packages?

On Fri, Mar 5, 2010 at 5:01 PM, daniele <gl...@live.com
<mailto:gl...@live.com>> wrote:

    On 03/05/10 16:43, Anselm Strauss wrote:

        Hi,

        is it possible to do a real preview with portupgrade? I want to
        see all
        ports that would be installed/upgraded when installing a
        particular port.
        The --noexecute option doesn't really show me a lot. How would
        this be done
        with packages? pkg_add would have to download all packges first
        to be able
        to calculate all dependencies, or can it operate on an index file?

        Anselm
        _______________________________________________
        freebsd-questions@freebsd.org
        <mailto:freebsd-questions@freebsd.org> mailing list
        http://lists.freebsd.org/mailman/listinfo/freebsd-questions
        To unsubscribe, send any mail to
        "freebsd-questions-unsubscr...@freebsd.org
        <mailto:freebsd-questions-unsubscr...@freebsd.org>"


    Hello !

    Take a look at the 'ports' manpage and you will find a mean on how
    to get useful information on the ports collection (configuring
    building discover dependencies etc..) :

    
http://www.freebsd.org/cgi/man.cgi?query=ports&apropos=0&sektion=0&manpath=FreeBSD+8.0-RELEASE&format=html
    
<http://www.freebsd.org/cgi/man.cgi?query=ports&apropos=0&sektion=0&manpath=FreeBSD+8.0-RELEASE&format=html>

    Examples

    *     fetch-list
                    Show list of files to be fetched in order to build
    the port.

    *     run-depends-list, build-depends-list
                          Print a list of all the compile and run
    dependencies, and dependencies of those dependencies, by port directory.

    etc...

    d


Well, I don't know if there's already some pre-packaged tool to retrieve the information you need. In the worst case, I suppose one should set up a script that makes use of that "static information" + the information provided by pkg_info to reach the goal... but that's just a guess

d
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to