public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Integrating Portage with other package managers
Date: Wed, 7 Mar 2018 13:42:00 -0500	[thread overview]
Message-ID: <CAGfcS_ms2sPw8DTs4xKW8iSBX37EOyvedgZZt4V8c0J43CNS6Q@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr9J6gTxcXr4Ci0eshhUhwr1s8mhmrSObthJgrkTN_-62w@mail.gmail.com>

On Wed, Mar 7, 2018 at 12:52 PM, Alec Warner <antarus@gentoo.org> wrote:
>
> https://wiki.gentoo.org/wiki/Project:Perl/g-cpan is a project is in a
> similar space and basically reads perl CPAN metadata to generate stub
> ebuilds.
> Portage tracks these stub ebuilds (and so for example, it tracks what these
> cpan packages install and can remove them afterwards.)
>

This is the right general approach.  If somebody were willing to do
the work I'm sure it would be useful if portage had a more generic
interface for stuff like this, such as a way to do plugins/etc.  The
idea would be to run some outside package manager in some kind of
sandbox, then create a binary package from what gets installed.

Everybody I know has these sorts of complaints about language-based
PMs, whether they prefer Ubuntu, or Debian, or CentOS, or whatever.
Nobody wants random programs downloading random stuff and dropping
orphan files all over their filesystem with no way to identify these
or clean them up.  They're usually written by the same sorts of people
who tell you to pipe curl into sudo bash...

-- 
Rich


  parent reply	other threads:[~2018-03-07 18:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 16:06 [gentoo-dev] Integrating Portage with other package managers anoteros
2018-03-07 16:51 ` Michael Orlitzky
2018-03-07 17:52   ` Alec Warner
2018-03-07 18:22     ` R0b0t1
2018-03-07 19:15       ` Alec Warner
2018-03-07 20:55         ` R0b0t1
2018-03-07 21:06           ` Rich Freeman
2018-03-08 16:44             ` R0b0t1
2018-03-08 17:50               ` Rich Freeman
2018-03-08 21:00                 ` R0b0t1
2018-03-08 21:38                   ` Rich Freeman
2018-03-09  0:46                 ` [gentoo-dev] Functional portage with namespace (Was: Integrating Portage with other package managers) Benda Xu
2018-03-09  1:06                   ` Rich Freeman
2018-03-09  2:11                     ` R0b0t1
2018-03-09  2:16                       ` Rich Freeman
2018-03-09 13:12                   ` X dej
2018-03-11 22:55                     ` [gentoo-dev] Functional portage with namespace Benda Xu
2018-03-16 23:40                       ` Kent Fredric
2018-03-17 13:32                         ` Francesco Riosa
2018-03-09 16:17               ` [gentoo-dev] Integrating Portage with other package managers Alec Warner
2018-03-09 17:44                 ` Rich Freeman
2018-03-09 20:11                 ` R0b0t1
2018-03-09 20:56                   ` Rich Freeman
2018-03-10  8:36           ` Kent Fredric
2018-03-07 18:42     ` Rich Freeman [this message]
2018-03-08  2:38       ` Benda Xu
2018-03-08  7:56         ` Dawid Weglinski
2018-03-07 20:12     ` Michael Orlitzky
2018-03-07 20:35       ` Alec Warner
2018-03-08  5:54   ` Benda Xu
2018-03-08 12:25     ` Michael Orlitzky
2018-03-08 14:47       ` kuzetsa
2018-03-08 15:23         ` kuzetsa
2018-03-08 20:59 ` James Le Cuirot
2018-03-10  5:26 ` Kent Fredric
2018-03-11 23:32 ` Benda Xu

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=CAGfcS_ms2sPw8DTs4xKW8iSBX37EOyvedgZZt4V8c0J43CNS6Q@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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