From: Jarry <mr.jarry@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] ~40 new perl-related ebuilds, why???
Date: Thu, 30 Sep 2010 18:20:54 +0200 [thread overview]
Message-ID: <4CA4B8E6.3090206@gmail.com> (raw)
Now this really scared me:
I just updated portage tree and checked if there are some updates
to install. To my surprise a huge list came with ~40 new ebuilds:
# emerge --pretend --update --deep --newuse world
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] net-misc/curl-7.20.0-r2 USE="idn ipv6 ssl -ares -gnutls
-kerberos -ldap -libssh2 -nss -test"
[ebuild N ] dev-perl/Net-SSLeay-1.36
[ebuild N ] dev-perl/Net-LibIDN-0.12
[ebuild N ] perl-core/Scalar-List-Utils-1.23
[ebuild N ] perl-core/libnet-1.22 USE="-sasl"
[ebuild N ] perl-core/MIME-Base64-3.08
[ebuild N ] dev-perl/YAML-Tiny-1.41
[ebuild N ] perl-core/Test-Harness-3.17
[ebuild N ] perl-core/Package-Constants-0.02
[ebuild N ] perl-core/Compress-Raw-Bzip2-2.024
[ebuild N ] perl-core/Compress-Raw-Zlib-2.024
[ebuild N ] perl-core/ExtUtils-CBuilder-0.27.03
[ebuild N ] virtual/perl-Scalar-List-Utils-1.23
[ebuild N ] virtual/perl-libnet-1.22
[ebuild N ] virtual/perl-MIME-Base64-3.08
[ebuild N ] virtual/perl-ExtUtils-CBuilder-0.27.03
[ebuild N ] virtual/perl-Test-Harness-3.17
[ebuild N ] virtual/perl-Package-Constants-0.02
[ebuild N ] virtual/perl-Compress-Raw-Bzip2-2.024
[ebuild N ] virtual/perl-Compress-Raw-Zlib-2.024
[ebuild N ] dev-perl/IO-Socket-SSL-1.33 USE="idn"
[ebuild N ] perl-core/digest-base-1.16
[ebuild N ] perl-core/IO-Compress-2.024
[ebuild N ] perl-core/ExtUtils-ParseXS-2.22.05
[ebuild N ] virtual/perl-digest-base-1.16
[ebuild N ] dev-perl/Net-SMTP-SSL-1.01
[ebuild N ] virtual/perl-IO-Compress-2.024
[ebuild N ] virtual/perl-ExtUtils-ParseXS-2.22.05
[ebuild N ] dev-perl/Digest-SHA1-2.12
[ebuild N ] perl-core/Digest-MD5-2.39
[ebuild N ] perl-core/IO-Zlib-1.10
[ebuild N ] virtual/perl-Digest-MD5-2.39
[ebuild N ] virtual/perl-IO-Zlib-1.10
[ebuild N ] dev-perl/Digest-HMAC-1.01-r1
[ebuild N ] perl-core/Archive-Tar-1.54
[ebuild N ] dev-perl/Authen-SASL-2.12 USE="-kerberos"
[ebuild N ] virtual/perl-Archive-Tar-1.54
[ebuild N ] perl-core/Module-Build-0.36.07
[ebuild N ] virtual/perl-Module-Build-0.36.07
[ebuild N ] dev-perl/Error-0.17.016 USE="-test"
[ebuild N ] dev-vcs/git-1.7.2.2 USE="blksha1 curl iconv perl
threads webdav -bash-completion -cgi -cvs -doc -emacs -gtk (-ppcsha1)
-subversion -tk -xinetd"
[ebuild U ] sys-devel/gettext-0.18.1.1-r1 [0.17-r1] USE="git%*"
[ebuild U ] sys-libs/e2fsprogs-libs-1.41.12 [1.41.11]
[ebuild U ] sys-fs/e2fsprogs-1.41.12 [1.41.11]
What happened since yesterday, why suddenly so many ebuilds want
to be newly installed? I checked changelogs for gettext, e2fsprogs
and e2fsprogs-libs but did not find any clue about what caused
all this perl-stuff to be pulled up. Can someone explain it to me?
Jarry
--
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.
next reply other threads:[~2010-09-30 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 16:20 Jarry [this message]
2010-09-30 16:37 ` [gentoo-user] ~40 new perl-related ebuilds, why??? Willie Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CA4B8E6.3090206@gmail.com \
--to=mr.jarry@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox