public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tastytea <gentoo@tastytea.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Discontinued Package: Copy to local overlay, just leave installed, or install manually?
Date: Sun, 19 Feb 2023 11:02:47 +0100	[thread overview]
Message-ID: <20230219110247.716b1542@ventiloplattform.tastytea.de> (raw)
In-Reply-To: <c346c684-6b48-46b4-d70d-299d59684408@hanft.de>

On 2023-02-19 10:24+0100 Matthias Hanft <mh@hanft.de> wrote:

> Hi,
> 
> according to https://bugs.gentoo.org/718972 (and a posting
> in the dev list), gsutil (and all needed libs) will be removed
> from the tree because "it's broken" (which is not true - works
> like a charm).
> 
> Since I do need gsutil urgently, I have already copied the needed
> ebuilds from /usr/portage to a local overlay in order to "emerge
> -c gsutil::gentoo" and then "emerge gsutil::local".
> 
> But then came to my mind: Is that necessary at all? As far as I
> know, I can just leave discontinued packages installed and continue
> to use them - regardless of whether they are still in portage tree
> or not. True or false?

Yes, you can just continue to use them. The ebuild will be kept in
/var/db/pkg/ in case portage needs to reinstall them or so.
However, it might make sense to copy it to a local overlay to make it
easier to get an overview of self/un -maintained packages. And since
gsutil requires Python, you'll have to modify the ebuild at some point
anyway to add support for newer Python versions.

> Or is it better to get rid of portage/ebuilds at all and do a
> manual installation, as described at
> https://cloud.google.com/storage/docs/gsutil_install?hl=en ?

I'd say use the ebuild since it already exists. Makes breakage less
likely.

Kind regards, tastytea


  reply	other threads:[~2023-02-19 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19  9:24 [gentoo-user] Discontinued Package: Copy to local overlay, just leave installed, or install manually? Matthias Hanft
2023-02-19 10:02 ` tastytea [this message]
2023-02-19 10:03 ` Mike Civil
2023-02-19 11:57   ` Matthias Hanft
2023-02-19 12:46     ` Mike Civil

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=20230219110247.716b1542@ventiloplattform.tastytea.de \
    --to=gentoo@tastytea.de \
    --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