On Thu, Dec 22, 2011 at 1:52 PM, Christer Edwards
wrote:
> At this point I believe all I have left is to write init scripts for
> the minion and master and it should be ready to go. That reminds me,
> what method should I use to include a short message on getting things
> running post installation
On Thu, Dec 22, 2011 at 1:31 PM, Ruslan Mahmatkhanov wrote:
> Btw, i'd prefer to patch setup.py once again to install them with
> '.sample' postfix. User will need to copy them into just `master' and
> `minion' to make it work. This will guarantee that user will not lost
> their configuration whil
Christer Edwards wrote on 22.12.2011 23:54:
> On Thu, Dec 22, 2011 at 2:43 AM, Ruslan Mahmatkhanov
> wrote:
>> Sorry for delay. Please review this patch:
>> http://people.freebsd.org/~rm/salt.diff.txt
>>
>> it fixes:
>> - fetch (FETCH_ARGS added, that i noted erlier)
>> - build (you mistyped py-J
On Thu, Dec 22, 2011 at 2:43 AM, Ruslan Mahmatkhanov wrote:
> Sorry for delay. Please review this patch:
> http://people.freebsd.org/~rm/salt.diff.txt
>
> it fixes:
> - fetch (FETCH_ARGS added, that i noted erlier)
> - build (you mistyped py-Jinja2 dependency)
> - python version changed to 2.6-2.7
Christer Edwards wrote on 22.12.2011 11:28:
> On Sun, Dec 18, 2011 at 8:22 PM, Ruslan Mahmatkhanov
> wrote:
>> Looks like mailing list eats the attachment. Would you please upload
>> it somewhere and provide us with the link.
>
> Apologies. I've uploaded the archive here:
>
> http://dl.dropbox.
On Sun, Dec 18, 2011 at 8:22 PM, Ruslan Mahmatkhanov wrote:
> Looks like mailing list eats the attachment. Would you please upload
> it somewhere and provide us with the link.
Apologies. I've uploaded the archive here:
http://dl.dropbox.com/u/312414/salt-port.tar.gz
_
Christer Edwards wrote on 19.12.2011 01:25:
> On Sat, Dec 17, 2011 at 3:23 AM, Ruslan Mahmatkhanov
> wrote:
>> Chris and Matthew already noted what the problems are. I also
>> suggest to use:
>>
>> ${PYTHON_PKGNAMEPREFIX}yaml>=0:${PORTSDIR}/devel/py-yaml
>
> That is much cleaner. Thank you.
>
>
On Sat, Dec 17, 2011 at 3:23 AM, Ruslan Mahmatkhanov wrote:
> Chris and Matthew already noted what the problems are.
> I also suggest to use:
>
> ${PYTHON_PKGNAMEPREFIX}yaml>=0:${PORTSDIR}/devel/py-yaml
That is much cleaner. Thank you.
> So USE_PYTHON=yes should be changed with USE_PYTHON= 2.
On 17 December 2011 10:23, Ruslan Mahmatkhanov wrote:
> Christer Edwards wrote on 17.12.2011 11:54:
>> RUN_DEPENDS+=
>> ${PYTHON_SITELIBDIR}/yaml/__init__.py:${PORTSDIR}/devel/py-yaml \
>>
>> ${PYTHON_SITELIBDIR}/zmq/__init__.py}:${PORTSDIR}/devel/py-pyzmq \
>>
>> ${PYTHON_SITELIBDIR}/Crypto/Ciph
Christer Edwards wrote on 17.12.2011 11:54:
> I've been working on building my first python based port recently and
> I'm running into some issue that I'm hoping the list can provide some
> tips for. Currently the Makefile looks like this:
>
> -
>
> # New ports collection makefile for: salt
>
On 17 Dec 2011 08:23, "Christer Edwards" wrote:
>
> I've been working on building my first python based port recently and
> I'm running into some issue that I'm hoping the list can provide some
> tips for. Currently the Makefile looks like this:
>
> -
>
> # New ports collection makefile for: s
On 17/12/2011 07:54, Christer Edwards wrote:
> I'm not sure if I've done the RUN_DEPENDS properly, because when I try
> to 'make' the port, it tries running the salt tool and complains about
> missing python modules. The modules are of course provided by the
> depends, but they don't get installed
12 matches
Mail list logo