From: Rafael Martins <rafael@rafaelmartins.eng.br>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Distfile patching support - Weekly report #9
Date: Sat, 30 Jul 2011 16:48:41 -0300 [thread overview]
Message-ID: <CAHgY3qcyCuHYOrsK07yMVOo4C85HkkoEPKS=r6knDBuGxdMtwA@mail.gmail.com> (raw)
In-Reply-To: <CAHgY3qeFksNnmvbj7rWJHsJKubOfJZtZ94kkow3RPQ0ch4Lorw@mail.gmail.com>
On Sat, Jul 30, 2011 at 4:47 PM, Rafael Martins
<rafael@rafaelmartins.eng.br> wrote:
> On Sat, Jul 30, 2011 at 10:30 AM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
>> On 18:09 Fri 29 Jul , Rafael Martins wrote:
>>> I'm also writing a helper tool, called distpatchq, inspired by
>>> portageq, that will provide info about the deltas and distfiles to the
>>> package managers willing to implement distfile patching support.
>>
>> Wouldn't package managers prefer an API rather than a helper tool?
>>
>
> Yes. Actually the Python API of the tools is usable by package
> managers, but this won't work for paludis, I guess. I'm just
> implementing Portage support for now, though.
>
> On the other hand, I want to be able to change the internal API, if
> needed. In this case, I need a helper tool or a stable public API will
> be required. I picked the first to make the things easy for all the
> package managers.
>
> Best regards,
>
> --
> Rafael Goncalves Martins
> http://rafaelmartins.eng.br/
>
s/will be required//
--
Rafael Goncalves Martins
http://rafaelmartins.eng.br/
prev parent reply other threads:[~2011-07-30 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 21:09 [gentoo-soc] Distfile patching support - Weekly report #9 Rafael Martins
2011-07-30 13:30 ` Donnie Berkholz
2011-07-30 19:47 ` Rafael Martins
2011-07-30 19:48 ` Rafael Martins [this message]
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='CAHgY3qcyCuHYOrsK07yMVOo4C85HkkoEPKS=r6knDBuGxdMtwA@mail.gmail.com' \
--to=rafael@rafaelmartins.eng.br \
--cc=gentoo-soc@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