-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 04 November 2003 13:38, Erwin Lang wrote: > > emerge -k package > > Remember that the PC need to have at least the same CPU. > > with this command I can install a prebuild package on a pc. but I want to > know how I can avoid to build the same package every week if there is no > new version available (as I said, emerge --buildpkg builds a package > regardless if there already exist a "packaged" version of this package in > /usr/portage/ packages or not.). Assume a script execute once a week: > `emerge --buildpkg apache tomcat samba ... (and other packages I need)`. So > I don't have to build packages manually if there is a new version > available. And I also need'n look for new versions of certain packages in > portage.
emerge -ubk package1 package2 package2 u = upgrade b = buildpkg k = usepkg No upgraded package, does nothing Upgraded package which doesn't exist as a tarball, compiles and makes a tarball. Upgraded package which exists as a tarball, use tarball, no compile. HTH - -- Mike Williams -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/p6+5InuLMrk7bIwRAtABAJ0UgABLLzeKvUFpAuWlEQw69ldz9ACgp01u p5TTnjTRyURk3/GVkBFjw/A= =i0y2 -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
