Opened 7 years ago

Last modified 7 years ago

#54014 new submission

py-stem @1.5.4 : Python controller library for Tor

Reported by: 1-61803 Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: py-stem

Description

Stem is a Python controller library for Tor. With it you can use Tor's control protocol to script against the Tor process, or write applications with capabilities similar to arm. From a technical standpoint, Stem is a Python implementation of Tor's directory and control specifications.

https://stem.torproject.org

Attachments (1)

Portfile (1.8 KB) - added by 1-61803 7 years ago.
corrected master_sites typo

Download all attachments as: .zip

Change History (7)

comment:1 Changed 7 years ago by mf2k (Frank Schima)

Comments:

  • I think we should be forward looking with python versions. So remove py34 and add py36 if it works with it.

comment:2 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Surely there's a better value that can be used for master_sites

comment:3 in reply to:  2 ; Changed 7 years ago by 1-61803

Replying to ryandesign:

Surely there's a better value that can be used for master_sites

I couldn't find a better one. If you find one though, I'll certainly use it.

comment:4 in reply to:  3 ; Changed 7 years ago by aque (Allan Que)

Replying to 1-61803:

Replying to ryandesign:

Surely there's a better value that can be used for master_sites

I couldn't find a better one. If you find one though, I'll certainly use it.

Try this. I used it for the py-typing Portfile.

master_sites        pypi:s/${python.rootname}
distname            ${python.rootname}-${version}

I also recommend you add categories-append devel security. The python PortGroup automatically adds the python category.

comment:5 in reply to:  4 ; Changed 7 years ago by 1-61803

Replying to aque:

Thanks! I emended the portfile.

Where does pypi:t/ come from?

comment:6 in reply to:  5 Changed 7 years ago by aque (Allan Que)

Replying to 1-61803:

Where does pypi:t/ come from?

It comes from the mirror_sites.tcl file. Here is the relevant section:

set portfetch::mirror_sites::sites(pypi) {
    https://pypi.python.org/packages/source/:nosubdir
    https://files.pythonhosted.org/packages/source/:nosubdir
}

pypi: is a placeholder for those sites and you're just adding s/${python.rootname} at the end of the path. So it will put them all together with ${distname} and fetch https://pypi.python.org/packages/source/s/stem/stem-1.5.4.tar.gz and then try https://files.pythonhosted.org/packages/source/s/stem/stem-1.5.4.tar.gz. Your file is found in the latter url.

Note that you have to change your Portfile to use pypi:s/${python.rootname} since it's the first letter of your file. It's how they hosted those packages. Hope that makes sense. I had to trace it myself.

Last edited 7 years ago by aque (Allan Que) (previous) (diff)

Changed 7 years ago by 1-61803

Attachment: Portfile added

corrected master_sites typo

Note: See TracTickets for help on using tickets.