On 12/28/20 6:06 PM, Thomas Mueller wrote:
>> Kudos to Stefan for keeping portmaster relevant and up-to-date.
>> But I never understood the appeal of portsnap. What's the advantage over
>
>> svnlite co ...
>> cd /usr/ports; make update
>
>> This mechanism is in the base system, so an extra tool dem
On 12/27/20 4:00 AM, LuMiWa via freebsd-ports wrote:
> The subject is 'portmaster new development' but again start pushing
> poudriere to FreeBSD users. I do not use zfs file system and I do not
> use poudriere and I do not want to use on my computer for building some
> ports and then spending hour
games/oneko was recently removed as it was marked broken due to being
unfetchable. I tried an old copy of the ports tree I had where it was
marked as such and `make fetch -DTRYBROKEN` succeeded. Was there an
error recorded for this and was it ever retested? Is this just a side
effect of having a
up other examples I have ran into in detail but was wondering
about the general approach and if the freebsd ports tree likes to fix it,
note it, or ignore it?
Thanks again,
Edward Sanford Sutton, III
___
freebsd-ports@freebsd.org mailing list
http://lists
On a couple ports I am working on, availability is only in the form of
cvs/svn. I made a temporary prefetch section for my own convenience which
calls up a particular revision off the server, compresses an archive of it,
and places it in the distfiles directory (thus leaving fetch happy as lon
