On 2016/09/15 22:10, Daniel Jakots wrote:
> On Sat, 27 Aug 2016 21:21:07 +0100, Stuart Henderson
> wrote:
>
> > You have to bump them all because otherwise packaging will fail
> > (PLIST_DB). If you are going to this trouble anyway it is probably
> > worth looking at setting PKGSPEC for setuputil
On Sat, 27 Aug 2016 21:21:07 +0100, Stuart Henderson
wrote:
> You have to bump them all because otherwise packaging will fail
> (PLIST_DB). If you are going to this trouble anyway it is probably
> worth looking at setting PKGSPEC for setuputils to reduce the need
> for future bumps..
So I'm look
You have to bump them all because otherwise packaging will fail (PLIST_DB).
If you are going to this trouble anyway it is probably worth looking at
setting PKGSPEC for setuputils to reduce the need for future bumps..
On 27 August 2016 5:35:44 p.m. Daniel Jakots wrote:
On Sat, 27 Aug 2016 18
On Sat, 27 Aug 2016 18:08:32 +0200, Daniel Jakots
wrote:
> I looked at what happened last time it was updated, the update was
> committed and then all ports that use setuptools were bumped, I don't
> know if such thing would be needed this time?
Talking about it with aja an jca, I understand tha
On Sat, 27 Aug 2016 18:08:32 +0200, Daniel Jakots
wrote:
> Hi,
>
> I'd like to update py-setuptools to not to lag too much on upstream. I
> cooked a diff that I used on a test machine (i386 fwiw).
This time it's attached to it won't get mangled.Index: Makefile
==
Hi,
I'd like to update py-setuptools to not to lag too much on upstream. I
cooked a diff that I used on a test machine (i386 fwiw).
I looked for any need to change the plist for a few ports
(py-werkzeug, py-requests, youtube-dl, beets and py-cares), nothing
came up.
I asked aja to put the diff i
