Re: what is pkg_create doing?
paul beard [EMAIL PROTECTED] writes: I realize it should be obvious from the name but it seems to linger for several minutes after each package is installed. PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 55763 root 11210 1852K 1232K RUN 0 2:38 95.73% pkg_create I am new to 6.2 (being a belated migrator from 4.x): is there a knob somewhere to turn off pkg creation? Not that I see any packages being kept anywhere . . . . When a package is built, it is always done *after* the port has been installed into $PREFIX. As far as I recall, packages don't get built unless you explicitly ask for them, so the command you used to install the program is what you need to look at for details. Incidentally, built packages get installed to /usr/ports/packages by default. None of this is different from earlier versions, as far as I remember. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what is pkg_create doing?
On Thu, 31 May 2007 09:47:20 -0400 Lowell Gilbert [EMAIL PROTECTED] wrote: paul beard [EMAIL PROTECTED] writes: I realize it should be obvious from the name but it seems to linger for several minutes after each package is installed. PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 55763 root 11210 1852K 1232K RUN 0 2:38 95.73% pkg_create I am new to 6.2 (being a belated migrator from 4.x): is there a knob somewhere to turn off pkg creation? Not that I see any packages being kept anywhere . . . . When a package is built, it is always done *after* the port has been installed into $PREFIX. As far as I recall, packages don't get built unless you explicitly ask for them, so the command you used to install the program is what you need to look at for details. I think pkg_create is used to register the package in /var/db/pkg even when no package file is created. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what is pkg_create doing?
On May 31, 2007, at 11:22 AM, Conrad J. Sabatier wrote: No, by default, portupgrade runs pkg_create *before* installing the newly built port, to create a backup of the old version in case something goes wrong. Depending on the size of the old port (package), this can take an appreciable amount of time, even on a fast system. Packages are only built *after* installation if one explicitly tells portupgrade to do so, via the -p or --package switches. This is consistent with what I am observing, as the command output claims the package is installed, I then see a delay (minutes? on a dual core 2.4GHz system?) while pkg_create runs, and then cleanup happens. The man page lists several package-related ENVIRONMENT variables, which may or may not provide a means to disable some or all of this package creation; I don't know for sure, as I've never tried changing or unsetting them to see what may happen. If you're curious, though, it may be worth experimenting with, although I would certainly advise against disabling the precautionary backup package creation before the new port is successfully installed. Thanks. I'll take a look there. I wasn't sure if something changes in how ports are done in the Moderne Age. -- Paul Beard words: http://paulbeard.org/wordpress pictures: http://www.flickr.com/photos/pdb206/ Are you trying to win an argument or solve a problem? PGP.sig Description: This is a digitally signed message part
Re: what is pkg_create doing?
On Thu, 31 May 2007 09:47:20 -0400 Lowell Gilbert [EMAIL PROTECTED] wrote: paul beard [EMAIL PROTECTED] writes: I realize it should be obvious from the name but it seems to linger for several minutes after each package is installed. PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 55763 root 11210 1852K 1232K RUN 0 2:38 95.73% pkg_create I am new to 6.2 (being a belated migrator from 4.x): is there a knob somewhere to turn off pkg creation? Not that I see any packages being kept anywhere . . . . When a package is built, it is always done *after* the port has been installed into $PREFIX. As far as I recall, packages don't get built unless you explicitly ask for them, so the command you used to install the program is what you need to look at for details. Incidentally, built packages get installed to /usr/ports/packages by default. None of this is different from earlier versions, as far as I remember. No, by default, portupgrade runs pkg_create *before* installing the newly built port, to create a backup of the old version in case something goes wrong. Depending on the size of the old port (package), this can take an appreciable amount of time, even on a fast system. Packages are only built *after* installation if one explicitly tells portupgrade to do so, via the -p or --package switches. The man page lists several package-related ENVIRONMENT variables, which may or may not provide a means to disable some or all of this package creation; I don't know for sure, as I've never tried changing or unsetting them to see what may happen. If you're curious, though, it may be worth experimenting with, although I would certainly advise against disabling the precautionary backup package creation before the new port is successfully installed. -- Conrad J. Sabatier [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what is pkg_create doing?
Conrad J. Sabatier [EMAIL PROTECTED] writes: On Thu, 31 May 2007 09:47:20 -0400 Lowell Gilbert [EMAIL PROTECTED] wrote: paul beard [EMAIL PROTECTED] writes: I realize it should be obvious from the name but it seems to linger for several minutes after each package is installed. PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 55763 root 11210 1852K 1232K RUN 0 2:38 95.73% pkg_create I am new to 6.2 (being a belated migrator from 4.x): is there a knob somewhere to turn off pkg creation? Not that I see any packages being kept anywhere . . . . When a package is built, it is always done *after* the port has been installed into $PREFIX. As far as I recall, packages don't get built unless you explicitly ask for them, so the command you used to install the program is what you need to look at for details. Incidentally, built packages get installed to /usr/ports/packages by default. None of this is different from earlier versions, as far as I remember. No, by default, portupgrade runs pkg_create *before* installing the newly built port, to create a backup of the old version in case something goes wrong. Depending on the size of the old port (package), this can take an appreciable amount of time, even on a fast system. Packages are only built *after* installation if one explicitly tells portupgrade to do so, via the -p or --package switches. The man page lists several package-related ENVIRONMENT variables, which may or may not provide a means to disable some or all of this package creation; I don't know for sure, as I've never tried changing or unsetting them to see what may happen. If you're curious, though, it may be worth experimenting with, although I would certainly advise against disabling the precautionary backup package creation before the new port is successfully installed. Ah; I'm sure that's it. I didn't realize that the poster was using portupgrade... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what is pkg_create doing?
In the last episode (May 31), paul beard said: On May 31, 2007, at 11:22 AM, Conrad J. Sabatier wrote: No, by default, portupgrade runs pkg_create *before* installing the newly built port, to create a backup of the old version in case something goes wrong. Depending on the size of the old port (package), this can take an appreciable amount of time, even on a fast system. Packages are only built *after* installation if one explicitly tells portupgrade to do so, via the -p or --package switches. The man page lists several package-related ENVIRONMENT variables, which may or may not provide a means to disable some or all of this package creation; I don't know for sure, as I've never tried changing or unsetting them to see what may happen. If you're curious, though, it may be worth experimenting with, although I would certainly advise against disabling the precautionary backup package creation before the new port is successfully installed. Thanks. I'll take a look there. I wasn't sure if something changes in how ports are done in the Moderne Age. Apply the patch in PR 112630. It fixes an inefficient dependency sorting algorithm that only became an issue after the xorg port update introduced an extra 100 dependencies to every X-using port. Took my pkg_create times down from 5 minutes to 5 seconds :) -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
what is pkg_create doing?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I realize it should be obvious from the name but it seems to linger for several minutes after each package is installed. PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 55763 root 11210 1852K 1232K RUN 0 2:38 95.73% pkg_create I am new to 6.2 (being a belated migrator from 4.x): is there a knob somewhere to turn off pkg creation? Not that I see any packages being kept anywhere . . . . I'm not subscribed, so CCing would ensure I get your reply. - -- Paul Beard words: http://paulbeard.org/wordpress pictures: http://www.flickr.com/photos/pdb206/ Are you trying to win an argument or solve a problem? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGXO1AjE2ksZfa4ZURAlIXAJsE844ANT3n0szi55MvP1w5+cAsxwCgzvxg RVB/DwVspsN24/UqdPzRCPE= =Vaao -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
