FreeBSD-base and poudriere

[Grzegorz Junka]

On 06/04/2020 11:49, Grzegorz Junka wrote:
>
>>>> 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.
>
> Yes, I do have a specific scenario of building drm-fbsd12.0-kmod. As I 
> was told on the -ports group this package has to be compiled with 
> EXACT same sources and kernel configuration as the kernel modules. I 
> don't know if that also means building using the kernel compiled from 
> that configuration, or if it's enough that the custom kernel 
> configuration is active when compiling the port, but definitely it 
> would not be enough to just have the kernel sources without the 
> configuration. Unless I misunderstood.
>
Actually, I just remembered that one can provide custom make.conf. So 
this scenario should be covered by simply adding the KERNCONF with 
custom kernel to the make.conf when creating jail. Oh wait, will it use 
the make.conf when creating a jail or only when building ports?

GrzegorzJ