Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Jan 2017 12:57:16 +0700
From:      Victor Sudakov <sudakov+freebsd@sibptus.tomsk.ru>
To:        Joe Nosay <superbisquit@gmail.com>
Cc:        Victor Sudakov <sudakov+freebsd@sibptus.tomsk.ru>, FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: make.conf options and poudriere
Message-ID:  <20170122055716.GA307@admin.sibptus.transneft.ru>
In-Reply-To: <CA%2BWntOvP4TiFiSdGk24%2BfO-AqLZsJKuZCY3frCQPo6Swm1JEkA@mail.gmail.com>
References:  <20170120091718.GA73239@admin.sibptus.transneft.ru> <CA%2BWntOuGEC1%2Bf02KVDrboA9qP3DsSCX32pOUrvBe7GSXxmDXVg@mail.gmail.com> <20170120163158.GA78266@admin.sibptus.transneft.ru> <CA%2BWntOvP4TiFiSdGk24%2BfO-AqLZsJKuZCY3frCQPo6Swm1JEkA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Joe Nosay wrote:
> >
> > Are you suggesting some alternative to poudriere? Of course I can
> > create a dedicated ports tree in poudriere, edit the Makefile manually
> > and never update that special tree. But isn't it something of an overkill
> > if I just want to protect my precious changes from being overwritten
> > by the next ports tree update?

> Keep the untouched file within the standard /usr/ports directory and build
> the edited file in the jail. Whatever differences there are, you will be
> able to share with the mailing list.

Which means the edited package will not make it into one of the
repositories I publish via poudriere for my hosts? This would be an inconvenience.

I think I'd better go with the ".if ${.CURDIR.....}"  clause in make.conf.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
AS43859



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170122055716.GA307>