using /etc/portsnap.conf
When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? ___ 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
Re: using /etc/portsnap.conf
On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? It will use /etc/portsnap.conf by default. No need for -f unless you need to use a different config file. By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. ___ 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
Re: using /etc/portsnap.conf
Walter Hurry wrote: On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? It will use /etc/portsnap.conf by default. No need for -f unless you need to use a different config file. By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. My /ect/portsnap.conf looks like this. # $FreeBSD: src/etc/portsnap.conf,v 1.5.2.1.2.1 2009/10/25 01:10:29 kensmith Exp $ # Default directory where compressed snapshots are stored. # WORKDIR=/var/db/portsnap # Default location of the ports tree # (target for update and extract). # PORTSDIR=/usr/ports # Server or server pool from which to fetch updates. You can change # this to point at a specific server if you want, but in most cases # using a nearby server won't provide a measurable improvement in # performance. SERVERNAME=portsnap.FreeBSD.org # Trusted keyprint. Changing this is a Bad Idea unless you've received # a PGP-signed email from security-offi...@freebsd.org telling you to # change it and explaining why. KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 # List of INDEX files to build and the DESCRIBE file to use for each #INDEX INDEX-6 DESCRIBE.6 #INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 # Example of ignoring parts of the ports tree. If you know that you # absolutely will not need certain parts of the tree, this will save # some bandwidth and disk space. See the manual page for more details. # # WARNING: Working with an incomplete ports tree is not supported and # can cause problems due to missing dependencies. If you have REFUSE # directives and experience problems, remove them and update your tree # before asking for help on the mailing lists. # REFUSE arabic chinese french german hebrew hungarian japanese REFUSE korean polish portuguese russian ukrainian vietnamese # # The following is complete list of all the port categories . # # REFUSE accessibility archivers astro audio benchmarks biology cad # REFUSE comms converters databases deskutils devel dns editors emulators # REFUSE finance ftp games graphics irc java lang mail math mbone misc # REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print # REFUSE science security shells textproc www # REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers # REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils # REFUSE accessibility archivers astro audio benchmarks biology cad REFUSE comms converters databases deskutils devel dns editors emulators REFUSE finance ftp games graphics irc java lang mail math mbone misc REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print REFUSE science security shells textproc www REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils This should only populate /usr/ports/sysutils But its not being used because everything is being populated in /usr/ports. I do portsnap fetch followed by portsnap extract What am I doing wrong here? I even tried portsnap extract -f /etc/portsnap.conf with no joy. ___ 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
Re: using /etc/portsnap.conf
On Thu, 03 Jan 2013 00:43:36 +0100, Fbsd8 fb...@a1poweruser.com wrote: Walter Hurry wrote: On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? It will use /etc/portsnap.conf by default. No need for -f unless you need to use a different config file. By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. My /ect/portsnap.conf looks like this. # $FreeBSD: src/etc/portsnap.conf,v 1.5.2.1.2.1 2009/10/25 01:10:29 kensmith Exp $ # Default directory where compressed snapshots are stored. # WORKDIR=/var/db/portsnap # Default location of the ports tree # (target for update and extract). # PORTSDIR=/usr/ports # Server or server pool from which to fetch updates. You can change # this to point at a specific server if you want, but in most cases # using a nearby server won't provide a measurable improvement in # performance. SERVERNAME=portsnap.FreeBSD.org # Trusted keyprint. Changing this is a Bad Idea unless you've received # a PGP-signed email from security-offi...@freebsd.org telling you to # change it and explaining why. KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 # List of INDEX files to build and the DESCRIBE file to use for each #INDEX INDEX-6 DESCRIBE.6 #INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 # Example of ignoring parts of the ports tree. If you know that you # absolutely will not need certain parts of the tree, this will save # some bandwidth and disk space. See the manual page for more details. # # WARNING: Working with an incomplete ports tree is not supported and # can cause problems due to missing dependencies. If you have REFUSE # directives and experience problems, remove them and update your tree # before asking for help on the mailing lists. # REFUSE arabic chinese french german hebrew hungarian japanese REFUSE korean polish portuguese russian ukrainian vietnamese # # The following is complete list of all the port categories . # # REFUSE accessibility archivers astro audio benchmarks biology cad # REFUSE comms converters databases deskutils devel dns editors emulators # REFUSE finance ftp games graphics irc java lang mail math mbone misc # REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print # REFUSE science security shells textproc www # REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers # REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils # REFUSE accessibility archivers astro audio benchmarks biology cad REFUSE comms converters databases deskutils devel dns editors emulators REFUSE finance ftp games graphics irc java lang mail math mbone misc REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print REFUSE science security shells textproc www REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils This should only populate /usr/ports/sysutils But its not being used because everything is being populated in /usr/ports. I do portsnap fetch followed by portsnap extract What am I doing wrong here? I even tried portsnap extract -f /etc/portsnap.conf with no joy. Just guessing: Try without the spaces at the beginning of the REFUSE lines? Michael ___ 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
Re: using /etc/portsnap.conf
Michael Ross wrote: On Thu, 03 Jan 2013 00:43:36 +0100, Fbsd8 fb...@a1poweruser.com wrote: Walter Hurry wrote: On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? It will use /etc/portsnap.conf by default. No need for -f unless you need to use a different config file. By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. My /ect/portsnap.conf looks like this. # $FreeBSD: src/etc/portsnap.conf,v 1.5.2.1.2.1 2009/10/25 01:10:29 kensmith Exp $ # Default directory where compressed snapshots are stored. # WORKDIR=/var/db/portsnap # Default location of the ports tree # (target for update and extract). # PORTSDIR=/usr/ports # Server or server pool from which to fetch updates. You can change # this to point at a specific server if you want, but in most cases # using a nearby server won't provide a measurable improvement in # performance. SERVERNAME=portsnap.FreeBSD.org # Trusted keyprint. Changing this is a Bad Idea unless you've received # a PGP-signed email from security-offi...@freebsd.org telling you to # change it and explaining why. KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 # List of INDEX files to build and the DESCRIBE file to use for each #INDEX INDEX-6 DESCRIBE.6 #INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 # Example of ignoring parts of the ports tree. If you know that you # absolutely will not need certain parts of the tree, this will save # some bandwidth and disk space. See the manual page for more details. # # WARNING: Working with an incomplete ports tree is not supported and # can cause problems due to missing dependencies. If you have REFUSE # directives and experience problems, remove them and update your tree # before asking for help on the mailing lists. # REFUSE arabic chinese french german hebrew hungarian japanese REFUSE korean polish portuguese russian ukrainian vietnamese # # The following is complete list of all the port categories . # # REFUSE accessibility archivers astro audio benchmarks biology cad # REFUSE comms converters databases deskutils devel dns editors emulators # REFUSE finance ftp games graphics irc java lang mail math mbone misc # REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print # REFUSE science security shells textproc www # REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers # REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils # REFUSE accessibility archivers astro audio benchmarks biology cad REFUSE comms converters databases deskutils devel dns editors emulators REFUSE finance ftp games graphics irc java lang mail math mbone misc REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print REFUSE science security shells textproc www REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils This should only populate /usr/ports/sysutils But its not being used because everything is being populated in /usr/ports. I do portsnap fetch followed by portsnap extract What am I doing wrong here? I even tried portsnap extract -f /etc/portsnap.conf with no joy. Just guessing: Try without the spaces at the beginning of the REFUSE lines? Thanks that was it. Sometimes your to close to the trees to see the forest. ___ 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
Re: using /etc/portsnap.conf
On Wed, 02 Jan 2013 20:06:47 -0500, Fbsd8 wrote: Thanks that was it. Sometimes your to close to the trees to see the forest. But you wouldn't have needed any REFUSE lines if you had followed my suggestion and just extracted the ports you wanted. ___ 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
Re: using /etc/portsnap.conf
Walter Hurry wrote: On Wed, 02 Jan 2013 20:06:47 -0500, Fbsd8 wrote: Thanks that was it. Sometimes your to close to the trees to see the forest. But you wouldn't have needed any REFUSE lines if you had followed my suggestion and just extracted the ports you wanted. After doing portsnap fetch for the first time followed by portsnap extract mis/ytree will create an /usr/ports directory empty of the files and directories needed for the make command to function. But yes the /usr/ports/misc/ytree port will be there. But having a /etc/portsnap.conf with REFUSE statements for all of the ports categories will populate /usr/port directory with only the files and directories required for the make command to function correctly. In csup this was called the base category which could be selected separately in the same way other ports could be selected separately. But it's good to know that I can duplicate what I was doing with csup now with portsnap to have a ports tree trimmed to only the things required by make and the few major ports that I needed to recompile to change the defaults used in the packaged versions. And to address the dependents question. I used pkg_add -r to install the dependents and the make install compiled without any problems. So thanks for your pointer to portsnap extract mis/ytree. It took some testing to figure out things because the man portsnap is not very clear about what is really happening. ___ 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
Re: using /etc/portsnap.conf
On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? Judging from man portsnap, the file will be read automatically at start unless you specify a -f diifferent file. -f conffile Read the configuration from conffile. (default: /etc/portsnap.conf) See man portsnap for reference. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
Re: using /etc/portsnap.conf
On Wed, 2 Jan 2013 18:24:14 + (UTC), Walter Hurry wrote: By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. This is correct and works in many many situations. However, there has been a saying which states that only a complete ports tree is guaranteed to work properly; I think this basically refers to the availability of dependencies and turtles all the way down, plus the top level files (such as /usr/ports/Makefile) and the Mk/ and Tools/ subtrees. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
