On 24 Feb, 2018, at 19:53, Marcin Cieslak wrote:
On Sun, 25 Feb 2018, Marcin Cieslak wrote:
Hello,
why is poudriere on 11.1-STABLE trying to build by custom port which has
the following
in the Makefile:
post-fetch:
${MKDIR} ${DISTDIR}/${PORTNAME}
${MKDIR} ${NPM_CACHE}
On Sun, 25 Feb 2018, Adam Weinberger wrote:
> > > (full log:
> > > https://gist.github.com/saper/0be3f9b4e9eb819d3ec00f5273705517#file-node-sass-4-7-2-log
> > > )
> > >
> > > Why are /bin/mkdir -p and /bin/cp commands invoked again in the "extract"
> > > phase?
> > >
> > > FreeBSD 11.1-STABLE #1
Hi,
Koichiro IWAO wrote
in
<01010161bc060e73-5e01b825-b1eb-4f4a-a112-b280ae670da7-000...@us-west-2.amazonses.com>:
me>
me> I'll take the maintainership if nobody wants however
me> I think security/softether and security/softether-devel
me> should be maintained by the same maintainer.
me>
me>
Can it/should it be assigned to enlightenm...@freebsd.org?
Does enlightenm...@freebsd.org need to be asked if they want to maintain it?
Or the submitter should maintain it?
Yuri
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/m
On 02/25/18 05:37, Marcin Cieslak wrote:
Yes, this is my private port that I am using to produce FreeBSD binaries
for node-sass. Getting binary npm modules into our ports tree is another
conversation.
The problem here is that a whole thing worked for me before for months
so I am aware of all th
On 2/26/18 9:45 AM, Yuri wrote:
> Can it/should it be assigned to enlightenm...@freebsd.org?
For new ports, it's a defacto, strongly encouraged guideline that new
ports should be MAINTAINER'd by the person who authored it, for reasons
outlined:
https://www.freebsd.org/doc/en/books/porters-handboo
