kpa said:
pkg delete perl? That's madness that I can't delete a damn package!markbsd said:
markbsd said:
markbsd said:
markbsd said:
pkg delete -f perl is the only option I have? And then pkg install perl-5.16 will get everything depending on perl working again?markbsd said:
OJ said:I don't think that resources are very important any more. I just built a new machine with middle of the road parts (Intel i3) and KDE runs fast. As for HDD space as a resource, the size of an OS is completely irrelevant these days.
Mind you, I do understand the aesthetics of the basic concept. I still run, and use daily, a machine which is extremely fast and runs perfectly after more than 20 years of tweaking my setup and OS setup skills. The processor is an Intel P1, and the OS is MS-DOS-6.22 - and yes I use it on the net too. The elegance of high functionality with very low resources is intoxicating. But since we got Gigabyte harddrives and multicore processors, that game is over.
The only thing that happened here is that my left shift key gets less use. Go figure.
I do feel your pain though. I've come close to quitting FreeBSD on several occasions recently. I didn't publish my rants, but they weren't pretty.
markbsd said:
#pkg updating perl
20131023:
AFFECTS: users of lang/perl5.12 lang/perl5.14
AUTHOR: mat@FreeBSD.org
The default Perl has been switched to lang/perl5.16. These examples
are for switching from lang/perl5.14, if you are running another
version, replace lang/perl5.14 with the origin of the Perl you have
installed.
Pkgng users:
# pkg set -o lang/perl5.14:lang/perl5.16
# pkg install -Rf lang/perl5.16
Portupgrade users:
0) Fix pkgdb.db (for safety):
pkgdb -Ff
1) Reinstall new version of Perl (5.16):
portupgrade -o lang/perl5.16 -f perl-5.14.\*
2) Reinstall everything that depends on Perl:
portupgrade -fr perl
Portmaster users:
portmaster -o lang/perl5.16 lang/perl5.14
Conservative:
portmaster p5-
Comprehensive (but perhaps overkill):
portmaster -r perl-
Note: If the "perl-" glob matches more than one port you will need to specify
the name of the Perl directory in /var/db/pkg explicitly.Juanitou said:Code:#pkg updating perl 20131023: AFFECTS: users of lang/perl5.12 lang/perl5.14 AUTHOR: mat@FreeBSD.org The default Perl has been switched to lang/perl5.16. These examples are for switching from lang/perl5.14, if you are running another version, replace lang/perl5.14 with the origin of the Perl you have installed. Pkgng users: # pkg set -o lang/perl5.14:lang/perl5.16 # pkg install -Rf lang/perl5.16 Portupgrade users: 0) Fix pkgdb.db (for safety): pkgdb -Ff 1) Reinstall new version of Perl (5.16): portupgrade -o lang/perl5.16 -f perl-5.14.\* 2) Reinstall everything that depends on Perl: portupgrade -fr perl Portmaster users: portmaster -o lang/perl5.16 lang/perl5.14 Conservative: portmaster p5- Comprehensive (but perhaps overkill): portmaster -r perl- Note: If the "perl-" glob matches more than one port you will need to specify the name of the Perl directory in /var/db/pkg explicitly.
Following these instructions worked here, but with ports and portmaster. I won’t dare to suggest you again reading the pkg manuals, I’ve perfectly understood that you don’t have time to waste…
pkg upgrade instead.I don’t remember suggesting anything related to updating perl, but you certainly have verified it. I’m only insisting, as the beginner I am, to read the manual pages: Google was not needed here to upgrade perl several weeks ago and have all ports needed for a nice desktop experience updated and running. Anyway, who am I to provide advice, isn’t it? The number and volume of the threads you have initiated show that you’re in the perfect mood for tinkering with FreeBSD as a desktop OS, so I’m not willing to irritate you any more and I’ll refrain from posting on them any more.markbsd said:
Juanito said:
markbsd said:
pkg conversion had a problem > solution flowchart... ( for instance often in perl upgrades (I run perl5-14 but packages I expect now use perl5-16 ...) ) in the sense that packages may contain often dependencies that locally have not been updated to the default version, etc... I don't believe that the new packages system has too many bugs, per se, just that it has enough missing features that it should have been delayed as the default. I can grep /var/db/pkg files in a pipe to reinstall ports which have been installed via package when they should have been installed via ports... fiddle with the directories in /var/db/pkg (temporarily rename to allow duplicate installs of conflicting ports which for some reason may both need to be installed, etc... ) and countless other fixes/workarounds which with more effort, one would just choose to not install, instead. pkg has not been building here for months, with a sqlite3.so error. /pkg/ but am posting in the hopes that one or two or more persons reading the post will concur that the package system would be served by such a flowchart, constantly revised... making it more user-friendly even to those not yet using FreeBSD but who may be swayed by simply reading the flowchart should it ever appear. [Not to discourage a multipage EXAMPLES section that would contain all the fixes/workarounds in a more verbose manner than is common except in exceptionally informative manpages, a few of which exist already. And common problems could be fixed by code to make the EXAMPLES list or flowchart size less sizable, a problem repository immediately available to all without further search, so to speak. man gpart and summarized (I know, a wiki, but many do not look there "first", as a matter of recourse...) it could be helpful in a similar manner to the topic of this thread, maybe having first recourse to a flowchart or very verbose EXAMPLES section.