Date: Mon, 26 Jun 2006 13:50:51 +0200 From: hans@lambermont.dyndns.org (Hans Lambermont) To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: New version of portmaster available for testing Message-ID: <20060626115051.GA19656@leia.lambermont.dyndns.org> In-Reply-To: <449CF1B2.5060404@FreeBSD.org> References: <4491F0AB.7050600@FreeBSD.org> <20060616143045.GA41923@leia.lambermont.dyndns.org> <44939B27.8070501@FreeBSD.org> <20060623084451.GA42262@leia.lambermont.dyndns.org> <449CF1B2.5060404@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton wrote: > What would you think about something like this? > http://dougbarton.us/portmaster-listplus.diff That shows the info I'm interested in :) Perhaps it can be improved slightly by having the 'new version' output on the same line ? So instead of : ===>>> en-openoffice.org-US-2.0.2 ===>>> New version available: openoffice.org-2.0.3rc6 ===>>> fetchmail-6.3.2_1 ===>>> New version available: fetchmail-6.3.4_3 Something like : ===>>> en-openoffice.org-US-2.0.2 update available: openoffice.org-2.0.3rc6 ===>>> fetchmail-6.3.2_1 update available: fetchmail-6.3.4_3 And perhaps add < > like 'pkg_version -v' : en-openoffice.org-US-2.0.2 < needs updating (port has 2.0.3rc6) fetchmail-6.3.2_1 < needs updating (port has 6.3.4_3) Also in list mode, the '===>>> ' seems unnecessary to me. >> | \--- 86809 root [dialog] >> # kill 21889 86809 >> ## what was going on here ? Daemonized distfile fetching perhaps ? > > Yes. The configure.kde3 script uses dialog, even in the make checksum > target. That is, um, weird; although I do see why they do it that way. > I'm really not sure how to handle this, so if anyone has a suggestion > ... Uhmpf, not yet (apart from uglyness ;-) What is the reasoning by the kde team ? >> # Adobe Reader >> Please type "accept" to accept the terms and conditions of license agreement; Type "decline" to exit. >> # accept >> ## Is there some way to handle this upfront like config ? This halted my >> ## build run for hours :-( > > No, sorry. Things that happen during the port make/install process > that are interactive can't be front loaded. However, I will add a > check to the dependency tracking and build to warn if IS_INTERACTIVE > is set anywhere. That would help, but only if it is possible to split a big upgrade set into parts, so that the interactive ones can be isolated. >> Can I skip en-openoffice.org-US-2.0.2 somehow for 'portmaster -GavD' ? > > Adding a list of ports to ignore is on the TODO list. Several people > have requested this, but so far no one has sent me an example of how > portupgrade flags this. Here's a port of my pkgtools.conf about HOLD_PKGS : # HOLD_PKGS: array # # This is a list of ports you don't want portupgrade(1) to upgrade, # portversion(1) to suggest upgrading, or pkgdb(1) to fix. # You can use wildcards ("ports glob" and "pkgname glob"). # -f/--force with each command will override the held status. # # To completely hide the existence of a package, put a dummy file # named "+IGNOREME" in the package directory. # # cf. pkg_glob(1), ports_glob(1) # # e.g.: # HOLD_PKGS = [ # 'bsdpan-*', # 'x11*/XFree86*', # ] HOLD_PKGS = [ 'bsdpan-*', 'openoffice-*', # 'perl-*', ] Is this what you needed ? regards, Hans Lambermont
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060626115051.GA19656>