poudriere merging multiple ports trees

Henrik Rosenke rosenke at dssgmbh.de
Thu Jan 28 09:55:45 UTC 2021


Greetings,

UIDs and GIDs are also not resprected, i could solve this via this patch:

Index: Mk/bsd.port.mk
===================================================================
--- Mk/bsd.port.mk      (Revision 563120)
+++ Mk/bsd.port.mk      (Arbeitskopie)
@@ -1274,8 +1274,17 @@
  # where 'make config' records user configuration options
  PORT_DBDIR?=   /var/db/ports

+# add support for overlaying UIDs and GIDs, dont include them if they 
dont exist
+.if exists(${OVERLAYS}/UIDs)
+UID_FILES?=    ${OVERLAYS}/UIDs ${PORTSDIR}/UIDs
+.else
  UID_FILES?=    ${PORTSDIR}/UIDs
+.endif
+.if exists(${OVERLAYS}/GIDs)
+GID_FILES?=    ${OVERLAYS}/GIDs ${PORTSDIR}/GIDs
+.else
  GID_FILES?=    ${PORTSDIR}/GIDs
+.endif
  UID_OFFSET?=   0
  GID_OFFSET?=   0

Maybe this could be implented upstream to support overlaying GIDs and UIDs

Kind regards,

Henrik Rosenke

Am 27.01.21 um 17:57 schrieb Henrik Rosenke:
> Greetings,
>
> i just added the overlay to my portstree, works good and great 
> addition. I wonder how you handle moved ports with this? As example we 
> are using a adapted Version of sysutils/sge62 with own patches but i 
> need to remove this Line in MOVED on the Original portstree to allow 
> building it. Is there a way to handle such exceptions or do i need to 
> rename it? Is there any Documentation about this?
>
> Kind regards,
>
> Henrik Rosenke
>
> Am 25.01.21 um 16:28 schrieb Baptiste Daroussin:
>> On Mon, Jan 25, 2021 at 04:25:09PM +0100, Miroslav Lachman wrote:
>>> On 25/01/2021 15:10, Baptiste Daroussin wrote:
>>>> On Sun, Jan 24, 2021 at 10:23:45PM +0100, Guido Falsi via 
>>>> freebsd-ports wrote:
>>>>> On 24/01/21 20:35, Russell L. Carter wrote:
>>>>>> Greetings,
>>>>>> I am completely ignorant here and am looking for up to
>>>>>> date advice on how to get poudriere to build and make
>>>>>> available package sets from multiple ports trees.  I
>>>>>> see there is a port "portshaker" that seems to do much
>>>>>> of what I want.
>>> [...]
>>>
>>>>> BTW I noticed poudriere performs shallow clones for git repos, so 
>>>>> it should
>>>>> not use up a lot of disk space.
>>>> Why not using directly overlays, it will simplify everything ;)
>>> I don't know if you read me reply or not - I am using poudriere with 
>>> ports
>>> overlay but have a problem with it. Poudriere options does not take 
>>> overlay
>>> in to account so ports options cannot be configured for overlayed ports
>>> which do not exist in the base three.
>>> Is there a way to fix it / should I file a PR for it?
>>>
>>> Kind regards
>>> Miroslav Lachman
>> Yes I read it and for sure poudriere option not supporting overlays is a
>> limitation, and yes a PR would help to not forget about implementing it.
>>
>> That said most people aren't using poudriere option and prefer to 
>> define option
>> directly via make.conf for them overlay is fully suited, and avoid 
>> the risk or
>> dangerous merging of trees may it be via portshaker, or git mechanism.
>>
>> there are room of improvements for overlays but it should work in 
>> most cases
>>
>> Best regards,
>> Bapt
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"


More information about the freebsd-ports mailing list