Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Apr 2020 16:22:53 +0200
From:      Guido Falsi <mad@madpilot.net>
To:        Grzegorz Junka <list1@gjunka.com>, freebsd-pkgbase@freebsd.org
Subject:   Re: FreeBSD-base and poudriere
Message-ID:  <ab310304-fcee-8a0b-8c1a-06fd7b33020c@madpilot.net>
In-Reply-To: <acb3e6af-2a75-1c4d-334d-c2719f2ff554@gjunka.com>
References:  <8c4f0ffe-6961-f119-0034-0becf860b616@gjunka.com> <d07d49a6-740f-25f1-f3ba-4d43d6162f1a@madpilot.net> <649a0a62-1ae4-6ec8-308a-4dadc234126a@gjunka.com> <98f5a68c-90d1-1f9f-4199-aed87d6aabc3@madpilot.net> <acb3e6af-2a75-1c4d-334d-c2719f2ff554@gjunka.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 06/04/20 13: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.

I'm not sure that's the case for drm-fbsd12.0-kmod. I think it only
needs the same exact kernel sources.

The to actually use drm you will need a running kernel with the required
parts, but that should not change how the package is built.

-- 
Guido Falsi <mad@madpilot.net>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab310304-fcee-8a0b-8c1a-06fd7b33020c>