Date: Sun, 12 Jul 2015 19:33:11 -0700 From: Jeffrey Bouquet <jeffreybouquet@yahoo.com> To: freebsd-pkg@freebsd.org Subject: Re: pkg problem, not severe but tedious. Message-ID: <55A32367.3070809@yahoo.com> In-Reply-To: <1436752112.28827.YahooMailBasic@web140903.mail.bf1.yahoo.com> References: <1436752112.28827.YahooMailBasic@web140903.mail.bf1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Even less of a problem (see below) On 07/12/15 18:48, Jeffrey Bouquet via freebsd-pkg wrote: > Each time across major versions I find it convenient to install one or two > upgrades ( portupgrade and another, in this case) > > pkg install portupgrade [the installworld just completed an hour or two ago] > > I use a > script reinstall.log pkg install portupgrade > > Because > the deinstalls called for are too numerous, no option to delay [ another SQL field? ] > > For instance > > Those two reinstalls (major version) require removal of some 200-400 of which I note > manually 35 or so for immediate reinstall later today. > > In this case > Not trivial... > > serf > apr > subversion > w3m > firefox > vte > intltool > gnutls > gsasl > gtk2 > cups-base > ....... and twenty-odd others of the several hundred to be removed upon the > upgrade of portupgrade from another major version and another ruby version > to the latest one. > > So it is handy workaround, but I wonder if a combination of > 1... "delay these til later" > 2... "to be removed and logged in a /var/log/pkg-removed.log " file > 3... or some other scenario should make it more simple. > 4... a 2nd field in the 'to be removed' ... some removed because of the > ruby21 upgrade, some removed for some other reason... one could maybe > craft the request to pkg in a more orderly fashion if more information was > known at that step. Maybe. > > Obviously this does not occur in the usual course of upgrading... but those to be removed could > probably still be of use in the meantime... Not that is is too problematic to reinstall them (usually but > not always )... but it is not as automatic as it maybe could be eventually. > > Thanks for reading. > _______________________________________________ > freebsd-pkg@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pkg > To unsubscribe, send any mail to "freebsd-pkg-unsubscribe@freebsd.org" The large list of files to be removed, upgrading 800 or so, halted at near the start because I had locked one package, causing pkg to halt. Upon the next invocation, it had resolved to only 80 or so. So some of those on that list were not actually, newly, to be removed. Simplest interim solution seems to be a file in /var/log that details deinstalls, optionally ??? with the reason, optionally ??? with parsing lines out from it if they have been subsequently reinstalled... maybe would reinstate some of the functionality of the /var/db/pkg text files [directories] I had used for that purpose [or something similar ]... not a direct comparison but the general idea. All I wish to write about the topic now. I know other issues may be more pertinent in the queue. Sorry!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A32367.3070809>