i keep *trying* to move from portupgrade to portmaster
in [Ports]
|
From: Sandra Kachelmann on 6 Aug 2010 03:24 I've been using ports-mgmt/portupgrade pretty much ever since it started to exist. Unfortunately portupgrade seems to be pretty much "abandonware" so I've been told to move on to portmaster. Despite the very long manpage I can't seem to be able to achieve the following thing with portmaster: $ portupgrade --batch -a If I issue this command I know exactly that I can go out, have a drink, cook some dinner and unlock my workstation the next day and find that everything completed unless a port failed to build. With portmaster I get asked a s*t load of interactive questions, whether I want to delete some package, whether it's really okay to pull in all the dependencies and so on. Can someone spoonfeed me the command I need to issue with portmaster in order to achieve the same thing as with $ portupgrade --batch -a Is that even possible? $ portupgrade --batch -a Thanks in advance! Sandra _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Doug Barton on 6 Aug 2010 04:06 On 08/06/2010 00:24, Sandra Kachelmann wrote: > I've been using ports-mgmt/portupgrade pretty much ever since it > started to exist. Unfortunately portupgrade seems to be pretty much > "abandonware" so I've been told to move on to portmaster. Despite the > very long manpage I can't seem to be able to achieve the following > thing with portmaster: > > $ portupgrade --batch -a Someone who has used portupgrade and is familiar with exactly what --batch does can probably help you with that bit, but I'm sure by now you've figured out that portmaster has a -a feature. Meanwhile, go get a $BEVERAGE, get comfortable, and actually _read_ the portmaster man page, don't just skim through it. I put a lot of effort into explain what portmaster does, how it does it, and also WHY it does things the way it does. Most (if not all) of your questions are answered there. > If I issue this command I know exactly that I can go out, have a > drink, cook some dinner and unlock my workstation the next day and > find that everything completed unless a port failed to build. You should be able to accomplish this with portmaster. hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Alex Kozlov on 6 Aug 2010 04:19 On 08/06/2010 00:24, Sandra Kachelmann wrote: > I've been using ports-mgmt/portupgrade pretty much ever since it > started to exist. Unfortunately portupgrade seems to be pretty much > "abandonware" so I've been told to move on to portmaster. Despite the > very long manpage I can't seem to be able to achieve the following > thing with portmaster: > $ portupgrade --batch -a Try echo BATCH?=yes >>/etc/make.conf && portmaster --no-confirm -a -- Adios _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Sandra Kachelmann on 6 Aug 2010 04:58 On Fri, Aug 6, 2010 at 10:06 AM, Doug Barton <dougb(a)freebsd.org> wrote: > On 08/06/2010 00:24, Sandra Kachelmann wrote: >> I've been using ports-mgmt/portupgrade pretty much ever since it >> started to exist. Unfortunately portupgrade seems to be pretty much >> "abandonware" so I've been told to move on to portmaster. Despite the >> very long manpage I can't seem to be able to achieve the following >> thing with portmaster: >> >> $ portupgrade --batch -a > > Someone who has used portupgrade and is familiar with exactly what > --batch does can probably help you with that bit, but I'm sure by now > you've figured out that portmaster has a -a feature. > > Meanwhile, go get a $BEVERAGE, get comfortable, and actually _read_ the > portmaster man page, don't just skim through it. I put a lot of effort > into explain what portmaster does, how it does it, and also WHY it does > things the way it does. Most (if not all) of your questions are answered > there. Please don't take this wrong but IMO it's way too overdocumented for normal users that don't actually read bsd.ports.mk before breakfast :-) Sandra _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Martin Schweizer on 6 Aug 2010 07:52
Hello Sandra I was in a similar situation. I found the following paramters very usefull: portmaster -a -d --no-confirm -a: Take all installed ports -d: Delete any dependicies -no--confirm: Wait not after the check which ports are upgradable With the above switch portmaster waits in two case: 1. If you run in an compile error 2. If the port is new and will asks you about make config I did now three upgrades like above and it worked as expected. Regards, 2010/8/6 Sandra Kachelmann <s.kachelmann(a)googlemail.com>: > On Fri, Aug 6, 2010 at 10:06 AM, Doug Barton <dougb(a)freebsd.org> wrote: >> On 08/06/2010 00:24, Sandra Kachelmann wrote: >>> I've been using ports-mgmt/portupgrade pretty much ever since it >>> started to exist. Unfortunately portupgrade seems to be pretty much >>> "abandonware" so I've been told to move on to portmaster. Despite the >>> very long manpage I can't seem to be able to achieve the following >>> thing with portmaster: >>> >>> $ portupgrade --batch -a >> >> Someone who has used portupgrade and is familiar with exactly what >> --batch does can probably help you with that bit, but I'm sure by now >> you've figured out that portmaster has a -a feature. >> >> Meanwhile, go get a $BEVERAGE, get comfortable, and actually _read_ the >> portmaster man page, don't just skim through it. I put a lot of effort >> into explain what portmaster does, how it does it, and also WHY it does >> things the way it does. Most (if not all) of your questions are answered >> there. > > Please don't take this wrong but IMO it's way too overdocumented for > normal users that don't actually read bsd.ports.mk before breakfast > :-) > > Sandra > _______________________________________________ > freebsd-ports(a)freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" > -- Martin Schweizer schweizer.martin(a)gmail.com Tel.: +41 32 512 48 54 (VoIP) Fax: +1 619 3300587 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |