Date: Tue, 6 Nov 2018 09:25:07 +0100 From: Harry Schmalzbauer <freebsd@omnilan.de> To: freebsd-ports@freebsd.org Subject: target_COOKIE making a real one? Message-ID: <3f82673a-5cb4-e6fc-d62c-5c89d0734b6c@omnilan.de>
next in thread | raw e-mail | index | archive | help
Sorry, me again, asking hopefully not so stupid questions.
Another thing I'm wondering from the beginning is why the target_COOKIE
don't store metadata.
I think it should be the infrastructure's task to wipe outdated work
directories.
So if PORTREVISION (stored in BUILD_COOKE) or OPTIONS (stored in
CONFIGURE_COOKIE) change, the ${WRKDIR} simply should be removed which
leads to a in-sync build. To my limited view, this seems a quiet simple
approch, with quiet high user experience improvement. This could be
extended to record dependencies' COOKIEs hashes in the EXTRACT_COOKIE...
I'm writing a wrapper for that (again) for now, but would be curious
what others think.
Thanks,
-harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3f82673a-5cb4-e6fc-d62c-5c89d0734b6c>