From: Tom Wijsman <TomWij@gentoo.org>
To: axs@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [OT] pkgcore bikeshed (was Portage team)
Date: Mon, 13 Jan 2014 16:31:36 +0100 [thread overview]
Message-ID: <20140113163136.26635d92@TOMWIJ-GENTOO> (raw)
In-Reply-To: <52D3FE8D.6010603@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 13 Jan 2014 09:56:13 -0500
Ian Stakenvicius <axs@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 13/01/14 09:46 AM, Tom Wijsman wrote:
> > On Mon, 13 Jan 2014 16:15:37 +0700 "C. Bergström"
> > <cbergstrom@pathscale.com> wrote:
> >
> >> Long term the API to pkgcore could be beneficial, but again I'm
> >> not sure it's a game changer for users.
> >
> > Long term, we should have an independent API backend that tools
> > can query; not rewrite our tools every time users want to use them
> > with a different package manager.
>
> ..you mean, define the API and include it in PMS? how much
> bureaucracy will that need to occur?
The API can be separate of the PMS. The bureaucracy needed for an API
to provide to tools, that doesn't need as much involvement as PMS.
- --
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJS1AbYAAoJEJWyH81tNOV90DEIAIk+zQe4vgJ2XWchQLET064Q
mij/sQQRcI52PZwXFfRh23G+dKkywsPIg+US5KmbWJTtT4UbbLFnn4KCRB/QZE6E
43wHYsKGMgTovpkXQZEy8O4GbFUOb1k9DrsR05r91+QUUUmxxxi9ODq86kavtPVs
UaPyz3me4j3olHLSxzUtxJd5/AgHGwkH+YHtcWny2oaXNUIFpusIPRURqyFyE4xI
Leq/w8/nsmeCc25pPN4cbY6bBwOwCxsZZwik3gmz6FzrAVwCjuRvX8n7szl8viNr
Kd56odFjX/n7pAL+Rj52spz6TNcSe1H8IMkwI9rMYc/LYQSw+/uCGnAXeIxrzWY=
=F2d3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-01-13 15:32 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 5:33 [gentoo-dev] Portage team, Zac's development break and stepping down as lead Brian Dolbec
2014-01-06 7:53 ` Dirkjan Ochtman
2014-01-06 8:27 ` Brian Dolbec
2014-01-13 3:07 ` Brian Dolbec
2014-01-13 5:05 ` Brian Dolbec
2014-01-13 8:39 ` C. Bergström
2014-01-13 8:43 ` Alexander Berntsen
2014-01-13 9:15 ` [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) "C. Bergström"
2014-01-13 9:31 ` Fabio Erculiani
2014-01-13 9:38 ` "C. Bergström"
2014-01-13 14:58 ` Tom Wijsman
2014-01-13 15:38 ` Luis Ressel
2014-01-13 15:46 ` Tom Wijsman
2014-01-13 17:03 ` Luis Ressel
2014-01-13 18:07 ` Tom Wijsman
2014-01-13 18:05 ` Ciaran McCreesh
2014-01-13 18:19 ` Tom Wijsman
2014-01-13 16:49 ` Alec Warner
2014-01-13 17:10 ` Fabio Erculiani
2014-01-13 18:16 ` Tom Wijsman
2014-01-13 18:21 ` Ciaran McCreesh
2014-01-13 18:32 ` Tom Wijsman
2014-01-13 23:22 ` Patrick Lauer
2014-01-13 23:49 ` Tom Wijsman
2014-01-13 11:02 ` [gentoo-dev] Re: [OT] pkgcore bikeshed Steven J. Long
2014-01-13 12:28 ` Alexander Berntsen
2014-01-13 13:06 ` Andreas K. Huettel
2014-01-13 13:50 ` Ulrich Mueller
2014-01-13 15:28 ` Tom Wijsman
2014-01-13 17:51 ` [gentoo-dev] " Ulrich Mueller
2014-01-14 7:41 ` [gentoo-dev] pkgcore EAPI-6 (Was: OT: pkgcore bikeshed) Steven J. Long
2014-01-13 15:21 ` [gentoo-dev] Re: [OT] pkgcore bikeshed Tom Wijsman
2014-01-13 20:29 ` Donnie Berkholz
2014-01-13 14:46 ` [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) Tom Wijsman
2014-01-13 14:56 ` Ian Stakenvicius
2014-01-13 15:31 ` Tom Wijsman [this message]
2014-01-13 18:01 ` Brian Dolbec
2014-01-13 18:07 ` Ciaran McCreesh
2014-01-13 18:27 ` Tom Wijsman
2014-01-13 18:37 ` Ciaran McCreesh
2014-01-14 7:56 ` [gentoo-dev] " Steven J. Long
2014-01-13 14:53 ` [gentoo-dev] " Tom Wijsman
2014-01-19 8:25 ` Mike Frysinger
2014-01-13 17:37 ` Greg KH
2014-01-13 17:42 ` "C. Bergström"
2014-01-13 17:56 ` Greg KH
2014-01-13 8:59 ` [gentoo-dev] Portage team, Zac's development break and stepping down as lead Dirkjan Ochtman
2014-01-13 14:42 ` Tom Wijsman
2014-01-13 14:46 ` Peter Stuge
2014-01-13 15:38 ` Tom Wijsman
2014-01-13 16:41 ` Alec Warner
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=20140113163136.26635d92@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=axs@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