On 06/04/20 15:01, Slawa Olhovchenkov wrote:
> On Mon, Apr 06, 2020 at 12:59:13PM +0200, Guido Falsi via freebsd-pkgbase 
> wrote:
> 
>> On 06/04/20 11:56, Grzegorz Junka wrote:
>>>
>>> On 06/04/2020 09:42, Guido Falsi wrote:
>>>> On 06/04/20 11:24, Grzegorz Junka wrote:
>>>>> Is it possible to create a poudriere jail using FreeBSD-base packages?
>>>>>
>>>>> I am thinking about a scenario where I build kernel/world and base
>>>>> packages on the host, then create a poudriere jail to build packages on
>>>>> the exact same kernel/world that was build on the host.
>>>> I'm doing a similar thing on head. What I do is run normal svn up; make
>>>> buildworld; make buildkernel; make packages on the poudriere machine. I
>>>> the upgrade that machine with the new base packages.
>>>>
>>>> After that I perform:
>>>>
>>>> poudriere jail -j ${j} -u -t 359154
>>>>
>>>> where 359154 is the subversion revision I have just compiled in /usr/src.
>>>>
>>>> So I get packages for that exact head revision.
>>>>
>>>> Hope this answers your question.
>>>>
>>>> BTW I have found no way to create a jail with a fixed svn revision from
>>>> the get go. When I need to do that, I resort to temporarily modifying
>>>> poudriere code at jail.sh:563, adding -r <rev> option. I then revert the
>>>> change.
>>>>
>>>
>>> Thanks, that's interesting. So, poudriere will build the jail from
>>> sources from that specific revision?
>>
>> Yes, since it will "svn up -r <rev>" it's source tree for that jail.
>>
>> It will also invalidate and remove all packages if __FreeBSD_version has
>> changed.
>>
>>>
>>> But I think it still won't solve the problem where the base packages
>>> have been build with modified kernel configuration. Can you supply a
>>> custom kernel configuration in your method?
>>
>> No I can't, but really a modified kernel configuration should not impact
>> on ports, do you have a specific scenario?
>>
>> At most ports interact with kernel sources, whatever the configuration.
> 
> NOINET6 don't change __FreeBSD_version but affect all inet-related
> modules, for example.
> 

__FreeBSD_version can be changed only via commit it's unrelated to options.

Anyway I accept your correction, but I don't see the issue anyway,
changing such kernel configurations is not something one does every day
or should be done without planning for it.

-- 
Guido Falsi <m...@madpilot.net>
_______________________________________________
freebsd-pkgbase@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-pkgbase
To unsubscribe, send any mail to "freebsd-pkgbase-unsubscr...@freebsd.org"

Reply via email to