From owner-freebsd-ports@freebsd.org Mon Apr 30 20:02:09 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D3D8FB566A for ; Mon, 30 Apr 2018 20:02:09 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout05.t-online.de (mailout05.t-online.de [194.25.134.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DA68678AA8 for ; Mon, 30 Apr 2018 20:02:08 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd20.aul.t-online.de (fwd20.aul.t-online.de [172.20.26.140]) by mailout05.t-online.de (Postfix) with SMTP id 35D15427A106; Mon, 30 Apr 2018 22:02:01 +0200 (CEST) Received: from Stefans-MBP-10.fritz.box (Vydrv8ZHYhPe+0Z-3aN8+cD6Wnw8Owr+XHU7saqPDRb4DhEbzHcSGf+RyfEH1t5wzL@[87.151.216.55]) by fwd20.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1fDEzm-0irAeG0; Mon, 30 Apr 2018 22:01:58 +0200 Subject: portmaster plans (was: Re: portupgrade vs. portmaster) To: freebsd-ports@freebsd.org References: <20180429214807.GA85409@elch.exwg.net> <20180430113403.AF3FF13BA@StefanEsser.freebsd.org> Cc: Thomas Mueller From: Stefan Esser Openpgp: preference=signencrypt Autocrypt: addr=se@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFVxiRIBCADOLNOZBsqlplHUQ3tG782FNtVT33rQli9EjNt2fhFERHIo4NxHlWBpHLnU b0s4L/eItx7au0i7Gegv01A9LUMwOnAc9EFAm4EW3Wmoa6MYrcP7xDClohg/Y69f7SNpEs3x YATBy+L6NzWZbJjZXD4vqPgZSDuMcLU7BEdJf0f+6h1BJPnGuwHpsSdnnMrZeIM8xQ8PPUVQ L0GZkVojHgNUngJH6e21qDrud0BkdiBcij0M3TCP4GQrJ/YMdurfc8mhueLpwGR2U1W8TYB7 4UY+NLw0McThOCLCxXflIeF/Y7jSB0zxzvb/H3LWkodUTkV57yX9IbUAGA5RKRg9zsUtABEB AAHNLlN0ZWZhbiBFw59lciAoVC1PbmxpbmUpIDxzdC5lc3NlckB0LW9ubGluZS5kZT7CwH8E EwEIACkFAlhtTvQCGwMFCQWjmoAHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRBH67Xv Wv31RAn0B/9skuajrZxjtCiaOFeJw9l8qEOSNF6PKMN2i/wosqNK57yRQ9AS18x4+mJKXQtc mwyejjQTO9wasBcniKMYyUiie3p7iGuFR4kSqi4xG7dXKjMkYvArWH5DxeWBrVf94yPDexEV FnEG9t1sIXjL17iFR8ng5Kkya5yGWWmikmPdtZChj9OUq4NKHKR7/HGM2dxP3I7BheOwY9PF 4mhqVN2Hu1ZpbzzJo68N8GGBmpQNmahnTsLQ97lsirbnPWyMviWcbzfBCocI9IlepwTCqzlN FMctBpLYjpgBwHZVGXKucU+eQ/FAm+6NWatcs7fpGr7dN99S8gVxnCFX1Lzp/T1YzsBNBFVx iRIBCACxI/aglzGVbnI6XHd0MTP05VK/fJub4hHdc+LQpz1MkVnCAhFbY9oecTB/togdKtfi loavjbFrb0nJhJnx57K+3SdSuu+znaQ4SlWiZOtXnkbpRWNUeMm+gtTDMSvloGAfr76RtFHs kdDOLgXsHD70bKuMhlBxUCrSwGzHaD00q8iQPhJZ5itb3WPqz3B4IjiDAWTO2obD1wtAvSuH uUj/XJRsiKDKW3x13cfavkad81bZW4cpNwUv8XHLv/vaZPSAly+hkY7NrDZydMMXVNQ7AJQu fWuTJ0q7sImRcEZ5EIa98esJPey4O7C0vY405wjeyxpVZkpqThDMurqtQFn1ABEBAAHCwGUE GAEKAA8FAlVxiRICGwwFCQWjmoAACgkQR+u171r99UQEHAf/ZxNbMxwX1v/hXc2ytE6yCAil piZzOffT1VtS3ET66iQRe5VVKL1RXHoIkDRXP7ihm3WF7ZKy9yA9BafMmFxsbXR3+2f+oND6 nRFqQHpiVB/QsVFiRssXeJ2f0WuPYqhpJMFpKTTW/wUWhsDbytFAKXLLfesKdUlpcrwpPnJo KqtVbWAtQ2/o3y+icYOUYzUig+CHl/0pEPr7cUhdDWqZfVdRGVIk6oy00zNYYUmlkkVoU7MB V5D7ZwcBPtjs254P3ecG42szSiEo2cvY9vnMTCIL37tX0M5fE/rHub/uKfG2+JdYSlPJUlva RS1+ODuLoy1pzRd907hl8a7eaVLQWA== Message-ID: <7b5364d5-daf3-69ce-f727-a42c52e47441@freebsd.org> Date: Mon, 30 Apr 2018 22:01:57 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180430113403.AF3FF13BA@StefanEsser.freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-ID: Vydrv8ZHYhPe+0Z-3aN8+cD6Wnw8Owr+XHU7saqPDRb4DhEbzHcSGf+RyfEH1t5wzL X-TOI-MSGID: 1553cd99-d6ab-4f05-9cc5-f3f70e20ebc5 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2018 20:02:09 -0000 Am 30.04.18 um 12:33 schrieb Thomas Mueller: > Current portmaster, even before FLAVORS, was clumsy upgrading a large number of ports, especially when there is an upgrade of perl or png. The author of portmaster decided to abort the upgrade of all remaining ports, if any dependency failed for any one port (i.e. did not try to build further independent ports, in that case). Or is there some other problem with e.g. perl upgrades? I plan to introduce new build options, e.g. to rebuild all ports that depend on libraries in some compat directory, or which have installed files in some path (e.g. the perl ports that install in a sub-directory that depends on the perl version). What other criteria might be useful to select ports for upgrading? > I see hardly any mention of synth on the freebsd-ports list. Have synth users become disenchanted? I do not know how much development is occurring for synth. It is written in a language that is only supported on amd64 (and i386?) and I'd rather use a tool that works on all platforms. > One downside is that synth fails to install build dependencies, so I have to pkg install all of these separately, very annoying. Pure build dependencies should not be required on a system, outside the build process. If you need some compiler or build tool, then it is just a normal program selected by the user. > I was bitten just yesterday trying to build cross-compiling tools for Haiku when make info was missing because texinfo was built but not installed. This might be a problem with the specification of dependencies in the port. > But I was able to recover with pkg install after checking my repository. With correct dependencies, this should not have been necessary. > With portmaster, I need to specify ports by category/portname rather than just portname, for example > portmaster www/seamonkey Yes, this is intentional. It could easily be changed, but currently only a parameter with / in it can lead to a new port being permanently installed (instead of as a dependency that might be automatically deleted when no longer required). What is the proposed semantic of a parameter that might select a port origin or some installed package, say if I invoke "portmaster bash" with or without bash being installed? > Will both the old and revamped portmaster be maintained, and what will be the port names, since there can't be two ports both named portmaster? I plan to create a portmaster-devel port, once the main-functionality of the existing portmaster port is complete. That version is meant for testing and as development version for new features. It should replace the current version after a few (say 3 to 6) months of testing. I'm willing to consider feature requests for the new version. My goal for now is to make it automatically deal with situations like the recent KDE4 port and package renaming, but also with scenarios not covered by the current version, where an indirect dependency must be considered. I'd like to implement a feature that builds all ports in a clean environment, as synth does. But this is not a priority, since we have poudriere and that is the official tool to build your own package repository. But a low overhead mode that works without setup effort on a subset of what poudriere offers might be quite useful. (And synth might offer that if it was written in a more portable language and if it was guaranteed to be well supported and maintained over the coming years.) Best regards, STefan