i keep *trying* to move from portupgrade to portmaster
in [Ports]
|
From: Doug Barton on 6 Aug 2010 18:02 On 08/06/2010 14:33, Jim Trigg wrote: > One example I have (unfortunately): I accidentally wiped out > /usr/local/. Reinstalling all my ports was easy -- first reinstall > portmaster and then run "portmaster -af". The problem was that for > every single port I had to say "Yes, ignore the fact that the port > wasn't already there". So I had to tend the process all the way > through. An option to force ignoring the package creation failure > would allow that to be an unattended process. Too bad you didn't read the man page, as there is already an option to skip backup package creation altogether. :) 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: Adam Vande More on 6 Aug 2010 18:03 On Fri, Aug 6, 2010 at 4:26 PM, Doug Barton <dougb(a)freebsd.org> wrote: > I need to add an option for this, but it will likely be an "expert" > option that you can set in the rc file. The theory is that package > creation failure should be a rare thing, and since portmaster has no way > to know what packages are really critical to any given system it treats > inability to safely recover from an upgrade failure as a critical error. > However, having the ability to disable this is an oft-requested feature, > I just haven't gotten to it yet. > > I actually took a look at the code in this area last night with an eye > towards creating this option, I'll see if I can get it done for the next > release. > While your in the mood for for taking portmaster suggestions, I think an option to backup all currently installed packages would be useful. I have a python script that does this for me, but it would be easy enough to use sh as well. I do this because there have been too many times something has broken during a port upgrade run and I need to revert immediately and fix later. I realize the backup package feature sort of does the same thing, but reconciling the pre- and post- updates is a tough thing for me. Having a user defined directory all currently installed ports can be put in is much easier to work with IMO. I know of other people doing similar things because I shared my script on questions- and got a few responses awhile ago. -- Adam Vande More _______________________________________________ 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 18:11 On 08/06/2010 15:03, Adam Vande More wrote: > While your in the mood for for taking portmaster suggestions, I am always in the mood for taking suggestions. :) > I think an > option to backup all currently installed packages would be useful. for pkg in /var/db/pkg/* ; do pkg_create -b $pkg done > I > have a python script that does this for me, but it would be easy enough > to use sh as well. I do this because there have been too many times > something has broken during a port upgrade run and I need to revert > immediately and fix later. I realize the backup package feature sort of > does the same thing, but reconciling the pre- and post- updates is a > tough thing for me. Having a user defined directory all currently > installed ports can be put in is much easier to work with IMO. I know of > other people doing similar things because I shared my script on > questions- and got a few responses awhile ago. It sounds like you want to add the option(s) for "create and keep a backup package of an installed port" and/or "create a package of the new port" either to your command line, wrapper script, or a portmaster rc file. You could use the command line above to create an up to date repository of your currently installed packages, and the 2 options above would both make sure you can back out an update and keep your local package repo up to date automatically. In the upcoming portmaster version there is also a new feature to clean out stale stuff from your $PACKAGES directory similarly to the way the feature to clean out stale distfiles works now, which should help you in keeping the repository described above fairly un-crufty. 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: Doug Barton on 6 Aug 2010 18:27 On 08/06/2010 14:03, Doug Barton wrote: > On 08/06/2010 05:44, Sandra Kachelmann wrote: > >> Thank you for your answer (and everyone else who replied). This is >> exactly the reason why I keep going back to portupgrade. Default >> OPTIONS almost always work for me In my haste to point out the exciting new update to -G I neglected to point out how OPTIONS work generally, and more specifically with portmaster. If you run the current production version of portmaster without -G then you will be prompted with all of the OPTIONS screens for all of the ports that need install/updating, then portmaster will start building stuff and leave you alone till it's done. On successive builds for the same port you will not be presented with that OPTIONS dialog again unless the questions have changed (OPTIONS lines added or deleted). IOW, the ports system "remembers" your choices so that you don't need to re-answer all the same questions again. In portmaster this behavior can be influenced with a command line option to force reconsideration of all OPTIONS. Also, if you're satisfied with the defaults you should probably consider the option to try installing packages first, and only build the port if the package is not up to date. 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: Michel Talon on 6 Aug 2010 21:23
Doug Barton wrote: > On 08/06/2010 15:03, Adam Vande More wrote: > > > While your in the mood for for taking portmaster suggestions, > > I am always in the mood for taking suggestions. :) > > > I think an > > option to backup all currently installed packages would be useful. > > for pkg in /var/db/pkg/* ; do > pkg_create -b $pkg > done > > > I > > have a python script that does this for me, but it would be easy > > enough > > to use sh as well. I do this because there have been too many times > > something has broken during a port upgrade run I don't think pkg_create preserves the config files user edited, which is the precious stuff, but it preserves a lot of useless stuff. The following python script by Cyrille Szymanski may be more useful: http://www.lpthe.jussieu.fr/~talon/pkg_save.py It keeps the config files and the shared libraries. -- Michel TALON _______________________________________________ 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" |