21 lines
No EOL
3.2 KiB
XML
21 lines
No EOL
3.2 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Caught in the Net (Posts about perl-core)</title><link>francescomecca.eu</link><description></description><atom:link href="francescomecca.eu/categories/perl-core.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 <a href="mailto:francescomecca.eu">Francesco Mecca</a> </copyright><lastBuildDate>Wed, 28 Feb 2024 09:29:26 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>About Perl packages in Gentoo</title><link>francescomecca.eu/blog/2015/9/11/about-perl-packages-in-gentoo/</link><dc:creator>Francesco Mecca</dc:creator><description><p>In this post I wish to explain a bit about Perl related ebuilds in Gentoo and how to update from perl-core to virtual/perl without conflicts.</p>
|
|
<p>First of all the core distribution of Perl is included in <a href="https://packages.gentoo.org/package/dev-lang/perl">dev-lang/Perl</a> along with <a href="http://perldoc.perl.org/index-modules-A.html">modules</a>.</p>
|
|
<p>The <a href="https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/perl-core/">perl-core category</a> in portage contains ebuilds for perl modules, some of which are included in the core perl distibution. The perl-core ebuilds overrides the perl-core modules such that you can update them without recompiling dev-lang/Perl.</p>
|
|
<p>Each perl-core module has a corrensponding virtual/perl-* package. The virtual category is used by portage when emerging to take into account that a module can be either provided by dev-lang/perl package or found in perl-core category.</p>
|
|
<p>So, what to do in case of blocks when upgrading your Gentoo machine?</p>
|
|
<p>Perl-cleaner is a package provided to get rid of these blocks and to migrate from perl-core to virtual/perl-*.</p>
|
|
<pre class="wp-code-highlight prettyprint linenums:1">emerge perl-cleaner
|
|
emerge dev-lang/perl
|
|
perl-cleaner --all</pre>
|
|
|
|
<p>if you still have problems when upgrading @world you add a backtrack option</p>
|
|
<pre class="wp-code-highlight prettyprint linenums:1">emerge -uDN --backtrack=30 @world</pre>
|
|
|
|
<p>or you can unmerge all perl-core packages and then finally upgrade world</p>
|
|
<pre class="wp-code-highlight prettyprint linenums:1">emerge --unmerge perl-core/*</pre>
|
|
|
|
<p>This will remove all perl-core packages that virtual/perl-* packages will bring back if needed.</p>
|
|
<p style="text-align: right;">
|
|
Francesco Mecca
|
|
</p></description><category>emerge</category><category>Gentoo</category><category>perl</category><category>perl-core</category><category>PesceWanda</category><category>portage conflict</category><category>virtual/perl</category><guid>francescomecca.eu/blog/2015/9/11/about-perl-packages-in-gentoo/</guid><pubDate>Fri, 11 Sep 2015 12:52:25 GMT</pubDate></item></channel></rss> |