> On Apr 2, 2019, at 5:40 PM, Ryan Schmidt wrote:
>
> On Mar 25, 2019, at 08:48, Craig Treleaven wrote:
>
>> On Mar 24, 2019, at 4:05 PM, Mojca Miklavec wrote:
>>
>>> I now checked the first two random MythTV ports, which basically boils down
>>> to:
>>>
>>> require_active_variants
This happened again yesterday.
> On Feb 25, 2019, at 13:53, Rainer Müller wrote:
>
> Hello,
>
> if you are using Gmail or a Google hosted mail service for your domain,
> your subscription to the macports-changes mailing list was likely
> disabled on 2019-02-22 by mailman due to "excessive or
On Mar 25, 2019, at 08:48, Craig Treleaven wrote:
> On Mar 24, 2019, at 4:05 PM, Mojca Miklavec wrote:
>
>> I now checked the first two random MythTV ports, which basically boils down
>> to:
>>
>> require_active_variants qt5-mysql-plugin mariadb55
>> require_active_variants
Hey,
On Wed, Apr 3, 2019 at 2:35 AM Mojca Miklavec wrote:
>
> Dear Karan,
>
> you may put such statistics and suggestions for action plans in the proposal
> (or appendix to proposal).
Ok, I'll do that soon
> What about pypackage -> py-pypackage? (I miss such entries on the list,
> unless
Dear Karan,
you may put such statistics and suggestions for action plans in the
proposal (or appendix to proposal).
What about pypackage -> py-pypackage? (I miss such entries on the list,
unless those are the ones you intentionally didn't count.)
Did you ignore capitalisation of names?
Mojca
Hey,
Just to see how many ports will we have to rename if we take on this
path I ran a quick script and following were the results:
PyPI NameMacports NameNumber
package package 10
package py-package 769
package
On Mar 25, 2019, at 01:56, Mojca Miklavec wrote:
> would prefer if he or she would perhaps spend time adding novel
> functionality, which could even be allowing user comments on each port
> (which you could use to explain why the port appears to be broken)
The ability to add comments on web
On Tue 2 Apr, 2019, 21:07 Mihir Luthra, <1999mihir.lut...@gmail.com> wrote:
>
>> Mihir,
>>
>> The proposal is view-only. You might need to give comment-access for
>> us to leave feedback on the draft.
>>
>> Done
>
Try to avoid creating multiple mail threads. Thanks
>
On 2 Apr 2019, at 17:11, macports-dev-requ...@lists.macports.org wrote:
> GSoC 2019
Could it be possible to relocate all this topics somewhere else?
>
>
> Mihir,
>
> The proposal is view-only. You might need to give comment-access for
> us to leave feedback on the draft.
>
> Done
Hi Mojca,
On Fri, Mar 29, 2019 at 3:55 AM Mojca Miklavec wrote:
>
> Dear MacPorts users & developers,
>
> You probably noticed a slightly increased traffic on this mailing list
> recently.
>
Really appreciate your emails and response to the GSoC students :).
> GSOC is an amazing opportunity
On Tue, 2 Apr 2019 at 16:01, Pierre Tardy wrote:
>
> Not sure if this is applicable, but there is no import method from
> buildbot 0.8.x to buildbot 0.9+
I don't believe we really need that.
It would be nice to "export" all the relevant (summary) data once
before decommissioning the old master
Not sure if this is applicable, but there is no import method from
buildbot 0.8.x to buildbot 0.9+
Buildbot do not import previous commit as changes when starting, it
only looks for new things.
Pierre
Le lun. 1 avr. 2019 à 23:03, Mojca Miklavec a écrit :
>
> On Mon, 1 Apr 2019 at 18:52,
Hi Mojca,
On Tue, Apr 2, 2019 at 3:14 AM Mojca Miklavec wrote:
> The drawbacks may include:
> - some ports will be skipped on the builder, for various reasons (port
> is known not to build on a particular builder, it may not be
> distributable, ...)
> - the buildbot master may be down or
On Tue, 2 Apr 2019 at 01:33, KARAN SHETH wrote:
>
> Is it possible to rename the existing Python ports as per PYPI so that
> issues of duplicates ports can be avoided?
>
Yes, I would be in favour of coming up with an "algorithm" for naming all
python ports and then stick to it. Ports which don't
15 matches
Mail list logo
