Re: New Mac OS Forge administrator

[Blair Zajac]

On Nov 19, 2015, at 7:14 PM, Craig Treleaven  wrote:

>> On Nov 19, 2015, at 9:49 PM, Ryan Schmidt  wrote:
>> 
>> Dear MacPorts users and developers,
>> 
>> I'm pleased finally to be able to tell you that I have been hired to be your 
>> new Mac OS Forge administrator. I have been involved in improving MacPorts 
>> for years as a committer and as a manager, and now as a Mac OS Forge 
>> administrator I will work on ensuring our infrastructure runs smoothly too.
>> 
>> I apologize for the downtime we've experienced in the past months. My 
>> priority right now is to resolve the existing issues, as I become familiar 
>> with the systems.
>> 
>> Please continue to report new problems with MacPorts infrastructure (server 
>> not working) as you have before, using the server/hosting component in Trac 
>> or via email to admin at macosforge dot org. And continue to report MacPorts 
>> administrative issues (mailing list issues, commit access requests) to 
>> portmgr at macports dot org.
>> 
>> Thanks for your patience and support and thank you for using MacPorts.
> 
> Congratulations on the new gig!  That is certainly good news for MacPorts and 
> I wish you every success.

Yes, congratulations! For you and the project!

Blair
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Old tickets w/o any attention or review

[Ivan Larionov]

Hello there.

I have some tickets which I created several months ago and I don't feel like 
anyone is going to review or commit them.
Oldest tickets are from April. Others are newer but they are required for old 
ones.

pgcli: https://trac.macports.org/ticket/47403
pgcli additional dependencies:
  py-pgspecial: https://trac.macports.org/ticket/49554
  py-setproctitle: https://trac.macports.org/ticket/49555
  py-prompt_toolkit: https://trac.macports.org/ticket/47402
  py-prompt_toolkit dependencies:
py-wcwidth: https://trac.macports.org/ticket/47401

mycli: https://trac.macports.org/ticket/49142
mycli additional dependencies:
  py-pymysql: https://trac.macports.org/ticket/49141

thefuck: https://trac.macports.org/ticket/47535
thefuck additional dependencies:
  py-pathlib: https://trac.macports.org/ticket/47534

Could someone please review and/or commit them?

Thanks!

--
With best regards, Ivan Larionov.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: New Mac OS Forge administrator

[Craig Treleaven]

> On Nov 19, 2015, at 9:49 PM, Ryan Schmidt  wrote:
> 
> Dear MacPorts users and developers,
> 
> I'm pleased finally to be able to tell you that I have been hired to be your 
> new Mac OS Forge administrator. I have been involved in improving MacPorts 
> for years as a committer and as a manager, and now as a Mac OS Forge 
> administrator I will work on ensuring our infrastructure runs smoothly too.
> 
> I apologize for the downtime we've experienced in the past months. My 
> priority right now is to resolve the existing issues, as I become familiar 
> with the systems.
> 
> Please continue to report new problems with MacPorts infrastructure (server 
> not working) as you have before, using the server/hosting component in Trac 
> or via email to admin at macosforge dot org. And continue to report MacPorts 
> administrative issues (mailing list issues, commit access requests) to 
> portmgr at macports dot org.
> 
> Thanks for your patience and support and thank you for using MacPorts.

Congratulations on the new gig!  That is certainly good news for MacPorts and I 
wish you every success.

Craig
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

New Mac OS Forge administrator

[Ryan Schmidt]

Dear MacPorts users and developers,

I'm pleased finally to be able to tell you that I have been hired to be your 
new Mac OS Forge administrator. I have been involved in improving MacPorts for 
years as a committer and as a manager, and now as a Mac OS Forge administrator 
I will work on ensuring our infrastructure runs smoothly too.

I apologize for the downtime we've experienced in the past months. My priority 
right now is to resolve the existing issues, as I become familiar with the 
systems.

Please continue to report new problems with MacPorts infrastructure (server not 
working) as you have before, using the server/hosting component in Trac or via 
email to admin at macosforge dot org. And continue to report MacPorts 
administrative issues (mailing list issues, commit access requests) to portmgr 
at macports dot org.

Thanks for your patience and support and thank you for using MacPorts.

-Ryan


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Portfile newbie questions

[Terry Barnum]

> On Nov 19, 2015, at 3:50 PM, Joshua Root  wrote:
> 
> On 2015-11-20 07:04 , Terry Barnum wrote:
>> My first post to macports-dev so please pardon the newbie questions.
>> 
>> I've wanted to try my hand at creating a Portfile for the pypolicyd-spf 
>> package . Postfix or Sendmail uses it 
>> to check a sender's SPF domain record to see if it's spoofed email.
>> 
>> pypolicyd-spf's README says it depends on v2.0.9+ of the python-spf library 
>> , which isn't in ports, and also 
>> depends on v2.1.10+ of the python ipaddr module, which is in ports but is an 
>> older version (v2.1.9). Current is 2.1.11 
>> .
>> 
>> Referencing the Macports docs, I created a local repository and successfully 
>> created local Portfiles to install the pymilter and ipaddr packages but then 
>> ran into warnings with the pypolicyd-spf port being installed into /etc. I 
>> think this means I need a patch file for its setup.py. Are there more 
>> examples of patchfiles? Like maybe a Dummy's Guide? ;) Or is it best just to 
>> look at other python Portfiles and see what they're doing?
> 
> There isn't a standard way to do this, mostly because having to patch
> build systems for this sort of reason is generally because the standard
> way of doing things doesn't work. It's just a matter of going through
> the code and finding out where the install location is defined, and
> figuring out how to get our install location there instead.

Thanks Joshua. I'll have a look at some other ports.

pixilla let me know about the pypi2port port which tries to build Portfiles for 
packages on the pypi site. I'm playing with it now.

>> Also, what's the convention for when to name a port just py-* versus py2?-* 
>> or py3?-*
> 
> The python portgroup handles creating a subport per supported python
> version for you. You put 'name py-something' and 'python.versions 27 35'
> and you will get subports py27-something and py35-something.

Thank you (and Brandon on the -users list) for the explanation.

-Terry

> 
> - Josh

Terry Barnum
digital OutPost
Carlsbad, CA

http://www.dop.com
800/464-6434


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Portfile newbie questions

[Joshua Root]

On 2015-11-20 07:04 , Terry Barnum wrote:
> My first post to macports-dev so please pardon the newbie questions.
> 
> I've wanted to try my hand at creating a Portfile for the pypolicyd-spf 
> package . Postfix or Sendmail uses it 
> to check a sender's SPF domain record to see if it's spoofed email.
> 
> pypolicyd-spf's README says it depends on v2.0.9+ of the python-spf library 
> , which isn't in ports, and also 
> depends on v2.1.10+ of the python ipaddr module, which is in ports but is an 
> older version (v2.1.9). Current is 2.1.11 
> .
> 
> Referencing the Macports docs, I created a local repository and successfully 
> created local Portfiles to install the pymilter and ipaddr packages but then 
> ran into warnings with the pypolicyd-spf port being installed into /etc. I 
> think this means I need a patch file for its setup.py. Are there more 
> examples of patchfiles? Like maybe a Dummy's Guide? ;) Or is it best just to 
> look at other python Portfiles and see what they're doing?

There isn't a standard way to do this, mostly because having to patch
build systems for this sort of reason is generally because the standard
way of doing things doesn't work. It's just a matter of going through
the code and finding out where the install location is defined, and
figuring out how to get our install location there instead.

> Also, what's the convention for when to name a port just py-* versus py2?-* 
> or py3?-*

The python portgroup handles creating a subport per supported python
version for you. You put 'name py-something' and 'python.versions 27 35'
and you will get subports py27-something and py35-something.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Portfile newbie questions

[Terry Barnum]

My first post to macports-dev so please pardon the newbie questions.

I've wanted to try my hand at creating a Portfile for the pypolicyd-spf package 
. Postfix or Sendmail uses it to check a 
sender's SPF domain record to see if it's spoofed email.

pypolicyd-spf's README says it depends on v2.0.9+ of the python-spf library 
, which isn't in ports, and also 
depends on v2.1.10+ of the python ipaddr module, which is in ports but is an 
older version (v2.1.9). Current is 2.1.11 
.

Referencing the Macports docs, I created a local repository and successfully 
created local Portfiles to install the pymilter and ipaddr packages but then 
ran into warnings with the pypolicyd-spf port being installed into /etc. I 
think this means I need a patch file for its setup.py. Are there more examples 
of patchfiles? Like maybe a Dummy's Guide? ;) Or is it best just to look at 
other python Portfiles and see what they're doing?

Also, what's the convention for when to name a port just py-* versus py2?-* or 
py3?-*

Thanks,
-Terry

Terry Barnum
digital OutPost
Carlsbad, CA

http://www.dop.com
800/464-6434

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev