On Tue, 28 Nov 2017 10:56:45 -0800 <bsd-li...@bsdforge.com> said

On Tue, 28 Nov 2017 08:56:12 -0800 <bsd-li...@bsdforge.com> said

> On Wed, 29 Nov 2017 00:31:56 +0800 "Julian Elischer" <jul...@freebsd.org>
> said
> > > On 28/11/17 11:09 pm, Chris H wrote:
> > > On Tue, 28 Nov 2017 07:29:10 +0100 "Kurt Jaeger" <li...@opsec.eu> said
> > >
> > >> Hi!
> > >>
> > >> > >> I have a requirement from $JOB to install some software (the > > >> python
> > >> > >> based Azure SDK actually) [...]
> > >> > > I suggest you put your initial version up somewhere and
> > >> > > then start ask questions here.
> > >> > >
> > >> > > It might be faster if many people submit hints than if
> > >> > > only one person gives you hints 8-}
> > >> > So far I don't know enough to put up anything.
> > >>
> > >> Ok, then there are two steps for the start:
> > >>
> > >> 1) Where is the distfile ? Because the first step would be to
> > >> create a ports Makefile that downloads that distfile.
> > >>
> > >> Is it this ?
> > >>
> > >> https://go.microsoft.com/fwlink/?LinkId=253472&clcid=0x409
> > >>
> > >> 2) Then, one has to dig into
> > >>
> > >>
> >
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
> > > > > >>
> > >>
> > >> to get to a initial Makefile.
> > >>
> > >> For this step: Install ports-mgmt/porttools and use
> > >>
> > >> port create
> > >>
> > >> Extra homework: Think about a nice name 8-}
> > >
> > > Not to discount anything Kurt as already suggested
> > > But I'd just like to throw in a couple of things that come to mind.
> > > You can think of this as a short learning curve, or the highway to > > > hell.
> > > You decide.
> > >
> > > 1) With a brand new port; I have often found it makes it quicker to > > > find a > > > already existing port that closely resembles the one I'm attempting > > > to create,
> > > and either gut it, or simply replace the parts required.
> > >
> > > 2) Given it's the Python Azure SDK. I'd probably go with the > > > following location:
> > > https://github.com/Azure/azure-sdk-for-python
> > > The opening page nearly creates the port for you. :)
> > > > well it may for you but for me it's all a learning curve where I need > > to discover the significance of every little thing.
> Ahh, sure OK. Now I have a little better base line to work with.
> I'll cobble up a starting point, and post it for you. :)
> FYI my dev box is out of commission right now, so there'll be some testing
> required on you're part. :)
OK I'm dealing with network woes here. So I'm a little slow in responding.
But... I've got a Makefile in the works. In the mean time, in case you've
already got something started; here's the Build/Requires/Depends list:

Requires
--------
python2-azure-sdk:
   py-openssl
   python(abi)
   py-dateutil
   py-requests
   py-vcrpy

python3-azure-sdk:
   python(abi)
   py3-dateutil
   py3-openssl
   py3-requests
   py3-vcrpy

Provides
--------
python2-azure-sdk:
   python-azure
   python-azure-common
   python-azure-mgmt
   python-azure-mgmt-common
   python-azure-mgmt-compute
   python-azure-mgmt-network
   python-azure-mgmt-nspkg
   python-azure-mgmt-resource
   python-azure-mgmt-storage
   python-azure-nspkg
   python-azure-sdk
   python-azure-servicebus
   python-azure-servicemanagement-legacy
   python2-azure
   python2-azure-common
   python2-azure-mgmt
   python2-azure-mgmt-common
   python2-azure-mgmt-compute
   python2-azure-mgmt-network
   python2-azure-mgmt-nspkg
   python2-azure-mgmt-resource
   python2-azure-mgmt-storage
   python2-azure-nspkg
   python2-azure-sdk
   python2-azure-servicebus
   python2-azure-servicemanagement-legacy

python3-azure-sdk:
   python3-azure
   python3-azure-common
   python3-azure-mgmt
   python3-azure-mgmt-common
   python3-azure-mgmt-compute
   python3-azure-mgmt-network
   python3-azure-mgmt-nspkg
   python3-azure-mgmt-resource
   python3-azure-mgmt-storage
   python3-azure-nspkg
   python3-azure-sdk
   python3-azure-servicebus
   python3-azure-servicemanagement-legacy

I haven't prefaced them with the [port] appropriate categories. But this
part completes most of the grunt work to create this port. :)

Alright. I *think* I've created a Makefile that you can (easily?) work with.
I commented it heavily, and should go a long way to get you where you're
going. If the mailing list doesn't strip it. You'll find it attached.

Good lick, and best wishes!

--Chris

P.S. Just give a howler if you have any ??? :)


--Chris
> > > > > thanks though..
> You're *quite* welcome. :)
> > --Chris > > > > > HTH > > > > every bit helps > > > > >
> > > --Chris
> > >
> > >>
> > >> -- > > >> p...@opsec.eu            +49 171 > > > 3101372                         3 > > >> years to go
> > >> !
> > >
> > >
> > >
> > >
> > > > _______________________________________________
> > freebsd-ports@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> > > _______________________________________________
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Attachment: Makefile
Description: Makefile

_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to