Tomoaki AOKI:
> Possibly I'm overlooking something in Porter's Handbook, but is there a
> proper and generic way that builds/installs some build dependencies
> under ${WRKDIR} and use it, without installing into the bare-metal
> environment?
Yes, you can use BUILD_DEPENDS=${NONEXISTENT}:foo/bar:s
Gleb Popov:
> > Well, now it blocks contributors that don't have a GitHub account
> > from being able to request a pull. :-)
>
> How would you request a pull when using FreeBSD git repo?
You wouldn't, but committers could directly commit to the branch.
Basically it's a question of whether colla
Gleb Popov:
> > No, I mean directly in git.freebsd.org, not in the GitHub mirror.
>
> That'd block contributors that are not committers for being able to
> request a pull.
Well, now it blocks contributors that don't have a GitHub account
from being able to request a pull. :-)
--
Christian "nad
Gleb Popov:
> > It would have been nicer if we could have had this as a collaborative
> > branch in the freebsd.org repository...
> > (Do we have a policy on this?)
>
> I wanted to do that too, actually, but it turned out that
> freebsd/freebsd-ports is a read-only repository that is automaticall
Gleb Popov:
> Check out [2] regularly to not step on others' feet.
>
> [2] https://github.com/arrowd/freebsd-ports/tree/autotools-mandir
Hint: You can add https://github.com/arrowd/freebsd-ports/ as an
additional remote to your local git repository, fetch and check out
that branch. That's a lot
Gleb Popov:
> I've created a branch [1] in my own fork that switches mandir for the
> autotools build system and am inviting everyone to collaborate on
> that, until all the fallout is fixed. I'm asking port maintainers to
> check if they have ports with the "GNU_CONFIGURE=yes" knob, as these
> ar
Gleb Popov:
> portmgr@ is currently working on switching the directory into which
> man pages are installed from "${PREFIX}/man" to "${PREFIX}/share/man".
>
> I've created a branch [1] in my own fork that switches mandir for the
> autotools build system and am inviting everyone to collaborate on
Christian Weisgerber:
> I just upgrade shells/yash, whose distfile is hosted on OSDN.
> I had to put the full URL into MASTER_SITES, because I can't figure
> out how to use the OSDN shortcut to fetch this:
Actually, the download page also offers a "simplified release file
I just upgrade shells/yash, whose distfile is hosted on OSDN.
I had to put the full URL into MASTER_SITES, because I can't figure
out how to use the OSDN shortcut to fetch this:
https://osdn.net/projects/yash/downloads/78345/yash-2.54.tar.xz
Any ideas?
Releases are linked from here:
https://osdn
"Pat Maddox":
> I am writing software that I would eventually like to install on
> FreeBSD. I'm currently stuck trying to write a Makefile that will point
> to my local git dir, so I can build and install it while I'm developing.
Set an empty DISTFILES and define a do-extract target that copie
monochrome:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259981
>
> I guess the "fix" is to install one or more from within the ports tree and
> not using portmaster
No. py-packaging still has a BUILD_DEPENDS on py-setuptools, so the
ports build will recurse there. Any py-setuptools sti
On 2021-11-28, Kevin Oberman wrote:
> If I remember correctly, the fix is to de-install both py38-packaging and
> py38-setuptools.
>> pkg delete -f py38-setuptools
>> pkg delete -f py38-packaging
>> portmaster devel/pkg-packaging
>> portmaster devel/py-setuptools
I'm stuck in the same catch-22 a
12 matches
Mail list logo
