Re: Portupgrade (vs. Portmanager) question
On Mon, 28 Mar 2005, Jay O'Brien wrote: Francisco Reyes wrote: /usr/ports/sysutils/pkg_tree Interesting. Thanks! I wonder how that compares to portmanager. I have never used port manager, but pkg_tree only lets you see a tree of the ports. It doesn't help you manage them. I don't know if port manager has an equivalent. -- http://stringsutils.com Utility for developers. Compute length, MD5, CRC and more. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Monday 28 March 2005 06:41, Jay O'Brien wrote: stheg olloydson wrote: Hello, They are recursive dependencies. Check each ports requirements. cvsup-without-gui depends on ezm3. ezm3 depends on gmake, gettext and libiconv. libiconv depends on libtool...and the foot bone's connected to the toe bone :). hth, stheg stheg, Thank you. Great learning experience. Especially 'make search'. That is very useful. But how does it work (/usr/ports/Makefile doesn't have a SEARCH statement) and is it documented somewhere, like in a MAN page? The handbook, ¶4.3, mentions 'make search' but doesn't explain how it works. make seach is documented in man ports ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Sun, 27 Mar 2005 23:49:11 -0800 Jay O'Brien [EMAIL PROTECTED] wrote: Michael C. Shultz wrote: It would be nice if the ports make options were better documented, but you can read through /usr/ports/Mk/bsd.port.mk and find information on the various options. here is an example: # all-depends-list # - Show all directories which are dependencies # for this port. then cd /usr/ports/lang/ezm3/ make all-depends-list result: /usr/ports/converters/libiconv /usr/ports/devel/gettext /usr/ports/devel/gmake /usr/ports/devel/libtool15 -Mike Mike, That's great info, thank you. It really helps put this into perspective. I did portmanager -sl and it identifies 7 candidates for deletion. It identifies cvsup-without-gui and also identifies ezm3 upon which it depends. Am I missing something here or shouldn't ezm3 not been identified as a leaf port? Good observation on your part and its a good question to ask. I'm not real familar with portmanager but it appears to identify the leaf ports in the same manner as sysutils/pkg_cutleaves and sysutils/pkg_rmleaves do. The utilities are only considering the run-dependencies as needed. Any port that is only required as a build-dependency is treated as a leaf port. They could be removed but it would have to be rebuilt if it were needed again. I usually keep these tools that are only needed for building since I run portupgrade nightly. Others that have limited hard disk space might elect to remove them and their associated source tarballs. Its left to the individual to decide whether or not to keep them. You're on the right track to understanding how the ports system works and using its tools. Just keep reading the man pages and observing how things function. Best regards, Randy -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Sunday 27 March 2005 11:49 pm, Jay O'Brien wrote: Michael C. Shultz wrote: It would be nice if the ports make options were better documented, but you can read through /usr/ports/Mk/bsd.port.mk and find information on the various options. here is an example: # all-depends-list # - Show all directories which are dependencies # for this port. then cd /usr/ports/lang/ezm3/ make all-depends-list result: /usr/ports/converters/libiconv /usr/ports/devel/gettext /usr/ports/devel/gmake /usr/ports/devel/libtool15 -Mike Mike, That's great info, thank you. It really helps put this into perspective. I did portmanager -sl and it identifies 7 candidates for deletion. It identifies cvsup-without-gui and also identifies ezm3 upon which it depends. Am I missing something here or shouldn't ezm3 not been identified as a leaf port? Jay ezm3 is a build dependency most likely, meaning once cvsup-without-gui is built it no longer needs ezm3, runs fine without it. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Monday 28 March 2005 05:50 am, Randy Pratt wrote: On Sun, 27 Mar 2005 23:49:11 -0800 Jay O'Brien [EMAIL PROTECTED] wrote: Michael C. Shultz wrote: It would be nice if the ports make options were better documented, but you can read through /usr/ports/Mk/bsd.port.mk and find information on the various options. here is an example: # all-depends-list # - Show all directories which are dependencies # for this port. then cd /usr/ports/lang/ezm3/ make all-depends-list result: /usr/ports/converters/libiconv /usr/ports/devel/gettext /usr/ports/devel/gmake /usr/ports/devel/libtool15 -Mike Mike, That's great info, thank you. It really helps put this into perspective. I did portmanager -sl and it identifies 7 candidates for deletion. It identifies cvsup-without-gui and also identifies ezm3 upon which it depends. Am I missing something here or shouldn't ezm3 not been identified as a leaf port? Good observation on your part and its a good question to ask. I'm not real familar with portmanager but it appears to identify the leaf ports in the same manner as sysutils/pkg_cutleaves and sysutils/pkg_rmleaves do. The utilities are only considering the run-dependencies as needed. The main difference between sysutils/pkg_cutleaves and portmanager -slid is portmanager catches all of the leafs in one pass, even after you've deleted a few. With pkg_cutleaves when you remove a leaf you have to look through all of them again to see if any new ones were exposed. Any port that is only required as a build-dependency is treated as a leaf port. They could be removed but it would have to be rebuilt if it were needed again. Correct. I usually keep these tools that are only needed for building since I run portupgrade nightly. Others that have limited hard disk space might elect to remove them and their associated source tarballs. Its left to the individual to decide whether or not to keep them. The idea behind identifying leaves is to see ports you may have installed and forgotten about because you never use them. Unless space is a problem I would recommend not removing ports that are build tools like ezm. -Mike You're on the right track to understanding how the ports system works and using its tools. Just keep reading the man pages and observing how things function. Best regards, Randy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
RW wrote: make seach is documented in man ports It sure is! THANK YOU! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
Randy, Mike: Thanks for the explanation. I hadn't considered a dependency that goes away after the dependent port is built. Now it makes perfect sense. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Sun, 27 Mar 2005, Jay O'Brien wrote: Alec Berryman wrote: Thanks for the heads up on 'make search', even if I can't find a complete description of the command. I find that it is referenced in the manual, however. Also check out the port /usr/ports/sysutils/pkg_tree It's very usefull to see dependencies. -- http://stringsutils.com Utility for developers. Compute length, MD5, CRC and more. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Sun, Mar 27, 2005 at 06:20:00PM -0800, Jay O'Brien wrote: Updating a computer, pkg_info reported I only had two packages, cvsup-without-gui-16.1h and perl-5.8.5, both of which were out of date as reported by pkg_version. I tried to install portmanager, but it was not able to get the needed files from http://portmanager.sunsite.dk. So, I installed portupgrade. Those files came in fine. I then did portupgrade -a -N -vu -rR, which was successful for me several months ago on another computer. The computer ran for over nearly two hours, with messages scrolling by so fast it was nearly impossible to read, filling up the screen with text. I used script so as to capture the screen messages; the capture file of the screen is 1.2MB in size! This is normal. Now, pkg_info says I have 10 packages installed; added were ezm3, gettext, gmake, libiconv, libtool, portupgrade,ruby and ruby18. If these all required to make portupgrade or perl work, where is that reference? These are in the port system /usr/ports/ Help! What did I do? You told you system to install portmanager and the ports that it needs, but also all the ports that are based on it. Please check 'man portupgrade' about the options. -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
Francisco Reyes wrote: On Sun, 27 Mar 2005, Jay O'Brien wrote: Thanks for the heads up on 'make search', even if I can't find a complete description of the command. I find that it is referenced in the manual, however. Also check out the port /usr/ports/sysutils/pkg_tree It's very usefull to see dependencies. -- http://stringsutils.com Utility for developers. Compute length, MD5, CRC and more. Interesting. Thanks! I wonder how that compares to portmanager. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
Alex de Kruijff wrote: You told your system to install portmanager and the ports that it needs, but also all the ports that are based on it. Please check 'man portupgrade' about the options. Good point, That is a man page I hadn't thought to review. Thank you! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Portupgrade (vs. Portmanager) question
Updating a computer, pkg_info reported I only had two packages, cvsup-without-gui-16.1h and perl-5.8.5, both of which were out of date as reported by pkg_version. I tried to install portmanager, but it was not able to get the needed files from http://portmanager.sunsite.dk. So, I installed portupgrade. Those files came in fine. I then did portupgrade -a -N -vu -rR, which was successful for me several months ago on another computer. The computer ran for over nearly two hours, with messages scrolling by so fast it was nearly impossible to read, filling up the screen with text. I used script so as to capture the screen messages; the capture file of the screen is 1.2MB in size! Now, pkg_info says I have 10 packages installed; added were ezm3, gettext, gmake, libiconv, libtool, portupgrade,ruby and ruby18. If these all required to make portupgrade or perl work, where is that reference? Help! What did I do? Jay O'Brien Rio Linda, California, USA PS.. I tried to install portmanager again, and this time it got the files immediately and installed fine. It took about a minute, not two hours. It reports that all my ports are up to date. Whew. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
Jay O'Brien on 2005-03-27 18:20:00 -0800: Now, pkg_info says I have 10 packages installed; added were ezm3, gettext, gmake, libiconv, libtool, portupgrade,ruby and ruby18. If these all required to make portupgrade or perl work, where is that reference? They are required to build and run portupgrade. If you do a 'make search name=portupgrade' from /usr/ports, it will list all the dependencies. PS.. I tried to install portmanager again, and this time it got the files immediately and installed fine. It took about a minute, not two hours. It reports that all my ports are up to date. Whew. That's because portupgrade did all the work :) If you had run portmanager before running portupgrade, you would have seen something similar - portmanager taking two hours and portupgrade taking almost no time at all. pgpfp6T6Aj4YX.pgp Description: PGP signature
Re: Portupgrade (vs. Portmanager) question
Alec Berryman wrote: Jay O'Brien on 2005-03-27 18:20:00 -0800: Now, pkg_info says I have 10 packages installed; added were ezm3, gettext, gmake, libiconv, libtool, portupgrade,ruby and ruby18. If these all required to make portupgrade or perl work, where is that reference? They are required to build and run portupgrade. If you do a 'make search name=portupgrade' from /usr/ports, it will list all the dependencies. PS.. I tried to install portmanager again, and this time it got the files immediately and installed fine. It took about a minute, not two hours. It reports that all my ports are up to date. Whew. That's because portupgrade did all the work :) If you had run portmanager before running portupgrade, you would have seen something similar - portmanager taking two hours and portupgrade taking almost no time at all. Alec, Thanks, I searched the FreeBSD Handbook for dependency and didn't find any reference to make search. I guess it is one of those things that once you know about it you don't have to look for it any more. Unfortunately a lot of the documentation I can review is written for those folks who already know the answers. Thanks for the heads up on 'make search', even if I can't find a complete description of the command. I find that it is referenced in the manual, however. I see that several of the packages that were installed aren't listed in the dependencies for portupgrade. Only the two ruby programs are listed. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Sun, 27 Mar 2005 19:08:56 -0800, Jay O'Brien [EMAIL PROTECTED] wrote: Alec Berryman wrote: Jay O'Brien on 2005-03-27 18:20:00 -0800: Now, pkg_info says I have 10 packages installed; added were ezm3, gettext, gmake, libiconv, libtool, portupgrade,ruby and ruby18. If these all required to make portupgrade or perl work, where is that reference? They are required to build and run portupgrade. If you do a 'make search name=portupgrade' from /usr/ports, it will list all the dependencies. PS.. I tried to install portmanager again, and this time it got the files immediately and installed fine. It took about a minute, not two hours. It reports that all my ports are up to date. Whew. That's because portupgrade did all the work :) If you had run portmanager before running portupgrade, you would have seen something similar - portmanager taking two hours and portupgrade taking almost no time at all. Alec, Thanks, I searched the FreeBSD Handbook for dependency and didn't find any reference to make search. I guess it is one of those things that once you know about it you don't have to look for it any more. Unfortunately a lot of the documentation I can review is written for those folks who already know the answers. Thanks for the heads up on 'make search', even if I can't find a complete description of the command. I find that it is referenced in the manual, however. I see that several of the packages that were installed aren't listed in the dependencies for portupgrade. Only the two ruby programs are listed. ezm3, gettext, gmake, libiconv, libtool are the build dependencies for cvsup-without-gui. # cd /usr/ports # make search name=cvsup-without-gui If you updated your soirces/ports cvsup then portupgrade did what you asked it to do. It Updated all outdated packages/ports and there dependencies. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
Abu Khaled wrote: ezm3, gettext, gmake, libiconv, libtool are the build dependencies for cvsup-without-gui. # cd /usr/ports # make search name=cvsup-without-gui Abu, I don't get that result. I only show ezm3-1.2. # cd /usr/ports # make search name=cvsup-without-gui Port: cvsup-without-gui-16.1h_2 Path: /usr/ports/net/cvsup-without-gui Info: General network file distribution system optimized for CVS (non-GUI version) Maint: [EMAIL PROTECTED] B-deps: ezm3-1.2 R-deps: WWW:http://www.cvsup.org/ # If you updated your soirces/ports cvsup then portupgrade did what you asked it to do. It Updated all outdated packages/ports and there dependencies. I'm convinced that you are right. However, why don't I show the other dependencies? Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Sun, 27 Mar 2005 20:27:17 -0800, Jay O'Brien [EMAIL PROTECTED] wrote: Abu Khaled wrote: ezm3, gettext, gmake, libiconv, libtool are the build dependencies for cvsup-without-gui. # cd /usr/ports # make search name=cvsup-without-gui Abu, I don't get that result. I only show ezm3-1.2. # cd /usr/ports # make search name=cvsup-without-gui Port: cvsup-without-gui-16.1h_2 Path: /usr/ports/net/cvsup-without-gui Info: General network file distribution system optimized for CVS (non-GUI version) Maint: [EMAIL PROTECTED] B-deps: ezm3-1.2 R-deps: WWW:http://www.cvsup.org/ # If you updated your soirces/ports cvsup then portupgrade did what you asked it to do. It Updated all outdated packages/ports and there dependencies. I'm convinced that you are right. However, why don't I show the other dependencies? # cd /usr/ports # make search name=ezm3 That's the best thing about portupgrade/portmanager. We don't have to worry (too much) about dependencies. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
it was said: If you updated your soirces/ports cvsup then portupgrade did what you asked it to do. It Updated all outdated packages/ports and there dependencies. I'm convinced that you are right. However, why don't I show the other dependencies? Hello, They are recursive dependencies. Check each ports requirements. cvsup-without-gui depends on ezm3. ezm3 depends on gmake, gettext and libiconv. libiconv depends on libtool...and the foot bone's connected to the toe bone :). hth, stheg __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
stheg olloydson wrote: Hello, They are recursive dependencies. Check each ports requirements. cvsup-without-gui depends on ezm3. ezm3 depends on gmake, gettext and libiconv. libiconv depends on libtool...and the foot bone's connected to the toe bone :). hth, stheg stheg, Thank you. Great learning experience. Especially 'make search'. That is very useful. But how does it work (/usr/ports/Makefile doesn't have a SEARCH statement) and is it documented somewhere, like in a MAN page? The handbook, ¶4.3, mentions 'make search' but doesn't explain how it works. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Sunday 27 March 2005 09:41 pm, Jay O'Brien wrote: stheg olloydson wrote: Hello, They are recursive dependencies. Check each ports requirements. cvsup-without-gui depends on ezm3. ezm3 depends on gmake, gettext and libiconv. libiconv depends on libtool...and the foot bone's connected to the toe bone :). hth, stheg stheg, Thank you. Great learning experience. Especially 'make search'. That is very useful. But how does it work (/usr/ports/Makefile doesn't have a SEARCH statement) and is it documented somewhere, like in a MAN page? The handbook, ¶4.3, mentions 'make search' but doesn't explain how it works. Jay It would be nice if the ports make options were better documented, but you can read through /usr/ports/Mk/bsd.port.mk and find information on the various options. here is an example: # all-depends-list # - Show all directories which are dependencies # for this port. then cd /usr/ports/lang/ezm3/ make all-depends-list result: /usr/ports/converters/libiconv /usr/ports/devel/gettext /usr/ports/devel/gmake /usr/ports/devel/libtool15 -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Sun, 27 Mar 2005 21:51:28 -0800, Michael C. Shultz [EMAIL PROTECTED] wrote: On Sunday 27 March 2005 09:41 pm, Jay O'Brien wrote: stheg olloydson wrote: Hello, They are recursive dependencies. Check each ports requirements. cvsup-without-gui depends on ezm3. ezm3 depends on gmake, gettext and libiconv. libiconv depends on libtool...and the foot bone's connected to the toe bone :). hth, stheg stheg, Thank you. Great learning experience. Especially 'make search'. That is very useful. But how does it work (/usr/ports/Makefile doesn't have a SEARCH statement) and is it documented somewhere, like in a MAN page? The handbook, ¶4.3, mentions 'make search' but doesn't explain how it works. Jay It would be nice if the ports make options were better documented, but you can read through /usr/ports/Mk/bsd.port.mk and find information on the various options. here is an example: # all-depends-list # - Show all directories which are dependencies # for this port. then cd /usr/ports/lang/ezm3/ make all-depends-list result: /usr/ports/converters/libiconv /usr/ports/devel/gettext /usr/ports/devel/gmake /usr/ports/devel/libtool15 -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thank you Michael for the very usefull information. Ahh, can't say how much I've learned after joining the lists. -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
it was said: But how does it work (/usr/ports/Makefile doesn't have a SEARCH statement) and is it documented somewhere, like in a MAN page? The handbook, ¶4.3, mentions 'make search' but doesn't explain how it works. Hello, It uses /usr/ports/Mk/bsd.port.mk. I doubt the options in there are officially documented, unless they are in the Developer's Handbook. There used to be a really good replacement for make search that had a lot of nifty options. Because I rarely used it (or make search), what it was called is lost to the mists of foggy memory Regards, stheg __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
Michael C. Shultz wrote: It would be nice if the ports make options were better documented, but you can read through /usr/ports/Mk/bsd.port.mk and find information on the various options. here is an example: # all-depends-list # - Show all directories which are dependencies # for this port. then cd /usr/ports/lang/ezm3/ make all-depends-list result: /usr/ports/converters/libiconv /usr/ports/devel/gettext /usr/ports/devel/gmake /usr/ports/devel/libtool15 -Mike Mike, That's great info, thank you. It really helps put this into perspective. I did portmanager -sl and it identifies 7 candidates for deletion. It identifies cvsup-without-gui and also identifies ezm3 upon which it depends. Am I missing something here or shouldn't ezm3 not been identified as a leaf port? Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
