|
Dne 28.4.2017 v 12:27 Ryan Lerch
napsal(a):
Dne 28.4.2017 v 07:34 Chenxiong Qi napsal(a):
> On Wed, Apr 26, 2017 at 2:54 PM, Pierre-Yves Chibon
<pingou@xxxxxxxxxxxx> wrote:
>> On Wed, Apr 26, 2017 at 11:29:28AM +0800, Chenxiong
Qi wrote:
>>>
>>> On 04/25/2017 10:23 PM, Pierre-Yves Chibon
wrote:
>>>> (adding the releng list on CC, please keep
the reply on the infra list)
>>>>
>>>>
>>>> Hi Everyone,
>>>>
>>>> Following up on the thread about pagure on
the top of dist-git started a
>>>> few days ago Ralph Bean, Matthew Prahl and
I had a quick meeting just a few
>>>> minutes ago about the future of pkgdb.
>>>>
>>> Will pkgdb go away? It looks Pagure would be a
data store combining package
>>> repositories and pkgdb data together. From my
point of view, pkgdb could
>>> still sit between packagers and Pagure rather
than exposing lower level data
>>> directly as an interface of package data
(whatever it comes from Pagure or
>>> PDC) to packagers and existing tools like
pkgdb-cli. If anything of my
>>> understand about current pkgdb is not accurate,
just scratch my thought :)
>> The idea is indeed to retire pkgdb. However, I'm
not sure I follow why you would
>> prefer to keep it and what you don't like about
dropping it. Could you expand
>> your thoughts a little more?
> I thought "pkgdb" would become a main interface for
anyone who wants
> to lookup package information without need to interact
with Pagure or
> PDC directly, meanwhile we can keep using current terms
about packages
> e.g. main contacts, that would be easier for anyone to
get involved
> and start to contribute.
I support this. For me is the pkgdb entry point. If I want
to know
something about package, I'm going to take a look into
pkgdb. I'll be
missing its simple UI.
Vít
There is also the packages app that provides information
on packages
I know ... but honestly, this one is unusable ... starting by the
ton of slow _javascript_ which often fails, ending with wrong
information such as
https://apps.fedoraproject.org/packages/rubygems/
Vít
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
|
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
