From owner-freebsd-ports@freebsd.org Sun Dec 17 01:06:33 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E72D1E95EDA for ; Sun, 17 Dec 2017 01:06:33 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A27457A95D for ; Sun, 17 Dec 2017 01:06:33 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x242.google.com with SMTP id z6so24608132iti.4 for ; Sat, 16 Dec 2017 17:06:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Q8iLaZx1EXFnEQRt/LGH0j8tCix80aa1FhoQT9fpaMw=; b=YW59t9jmH0bFbogf9D4BK7fiULoNQyZ/iuT3BKN6vasRxYMWGWO+DryjWr/OjsQ/Id dJuY7OKGhnRPFlNE9VhKIP6vzYwlmZzUB2gRq4nwyk2JFNdt4KTf50iwGJmFsgxd7w3G mlyqJSZNleAfzcUkaRM3Qhj1kWOiN0bvjt9VvK7QcZOSXCInvG011bjoOu6Ugw68mzxl HIbLiRVMMX/5hdBCrIglmMS3dg3Q8rhbjsma4yZLKdkC8ORTX81Wy/yE6jfYqzLBDVqY TNJDNr8qO5CZPrVU2Fc3XL4Wi2RynEiiZe6ubpZXu49UJJ3uEihOsFNZNbz5ep7oT8v3 FADg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Q8iLaZx1EXFnEQRt/LGH0j8tCix80aa1FhoQT9fpaMw=; b=IM12uqmL3iExfE9LwDiVcmsGeY1pWlvaoLNoethMY67uNiMa/yYczWQ2hCgDrqR/oS 1L0zDBy3/Teab+Ednw5LZnDY0jM8d9qXUqvjb7hlAMqo5sTvLP/EJ+4zuSJhX06tL7vU wwvUdB1gQ19Mmc6l4K6R39cawBv3W7nk/c2rM9McqXzieC4iFz1tiBR3bIUwibtCRV27 6+5XzkAONnp1sjq0HEZjH/6UYRTVeSuYz5vsiC7TnfkFUPuO+e5oWwZaV3YtDz7sHVOx qR9fa/fl0epZvG3pUbfEWryMlSJDA8UbEWROfl1IQEF3rqlucTOCF718sF1qH0XZPvwK Jz6w== X-Gm-Message-State: AKGB3mLT7UgqNvfe05YIlxKHI77+jUpe/SlX383nfpW4qcDAioe7GSq/ WNeO9P4Rj6F5QRqOkKlvgBj111zcim7qQn6nF6Y= X-Google-Smtp-Source: ACJfBouf39n9t57IA0WkHukpPylUby2JEtuOiRcAZXWL4ypIgxoTWq0eQI9qHf0xiDoAKHyEDtL2xs+joEKDo7cWs6c= X-Received: by 10.36.151.198 with SMTP id k189mr15411184ite.100.1513472792796; Sat, 16 Dec 2017 17:06:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.134.9 with HTTP; Sat, 16 Dec 2017 17:06:31 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Sun, 17 Dec 2017 09:06:31 +0800 Message-ID: Subject: Re: OSS Audio To: Sid Cc: Yuri , fjwcash@gmail.com, FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Sun, 17 Dec 2017 01:06:34 -0000 On Sun, Dec 17, 2017 at 6:53 AM, Sid wrote: > I've had a few misconceptions. > > Bluebee Blubeeme said, 4Front has a modern OSS implementation that is > under a FreeBSD license. > > The model of Sound on FreeBSD is, three layers: > 1. The API, where programs use libraries (of respective sound > architecture) to access the sound server. > 2. The sound server: OSS, Sndio, Portaudio, JACK, ALSA, native, etc > 3. FreeBSD's base is always OSS (OpenBSD's driver is sndio); sound servers > connect to and use this. > FreeBSD base is an older fork of 4Front OSS, somewhere around version 3 something. There's a 3,200 line diff between freebsd /sys/sys/soundcard.h and the one available in 4Front repo right now, there's been a lot of improvements between FreeBSD fork and 4Front OSS 4.2 Plus the OSS 4.x soundcard.h handles ALL legacy devices. The main thing that changed is the API, follow updated coding styles for new applications while old applications still just work. The sound server madness goes away with 4Front OSS. The API would be stable with 4Front OSS There's no single place with a more straight forward audio programming guide online compared to this: http://manuals.opensound.com/developer/ If there is please share. To use 4Front's OSS, FreeBSD's kernel will have to be recompiled without > OSS, "snd" and "sound" references, and then that version of OSS installed. > without the legacy oss, snd and sound references. That would be replaced by the 4Front OSS implementation. Then improvements/ fixes can be made on our end and tried to have upstreamed. The API is stable, well documented and the sound server madness goes away as well. > > The part of OSS in name, that is a mess, is the API structure, and various > implementations. In FreeBSD for instance, when a program uses an OSS API, I > hear that developers, need to write so many patches, because different OSS > frontends are not standardized. Most applications in ports use Sndio, > because across BSD's the API to it is standard. Bluebee claims that > 4Front's OSS is standard as well. As for API on programs/ports, just use > the FreeBSD API that is available for it, OSS, Sndio, Portaudio, to connect > to that sound server. > This is what can happen w/ open source software. Everyone took from Hannu's work and then no one credited him for his accomplishments but everyone dog piles on him. > > As long as OSS covers the wide range of implementations of it, OSS In > Name, without clarifiers, will carry this burden of being complex and > having a nonstandard API, even when certain implementations don't or may > not have this issue. > This is a Linuxism, spread right around the time they wanted to push ALSA. Since there are very few to NO audio developers who build software from the ground up for FreeBSD, all these Linuxism seeped in through the porting of software from Linux to FreeBSD. > > Bluebee says, to my understanding, that 4Front's OSS doesn't have certain > coding inefficiencies that certain sound architectures have. That is > something for the developers to be informed about, and to consider in > FreeBSD current. > This is why I am bringing up the issue and why I said the first step would be porting the proper 4Front OSS into the kernel. It doesn't have to be the default at first but if it's not in the kernel why bother wasting time to have it rejected because of all the misconceptions I've been dealing with in these threads. Add 4Front OSS to the kernel Use the 4.x API/ Documentation Add it to an audio programming section of FBSD Handbook Upstream changes that make sense Simplify audio programming, documentation, all those audio sound servers Port device drivers to the OSS Device Driver API: http://manuals.opensound.com/sources/drv_index.html > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > That's a lot of work and without being able to get this into the kernel because people just say "oss is a mess" isn't a valid reason. A lot of these opinions seeped into FreeBSD from other sources. From owner-freebsd-ports@freebsd.org Sun Dec 17 04:47:42 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72B11EA1B47 for ; Sun, 17 Dec 2017 04:47:42 +0000 (UTC) (envelope-from jktrigg@gmail.com) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B6932E4D for ; Sun, 17 Dec 2017 04:47:42 +0000 (UTC) (envelope-from jktrigg@gmail.com) Received: by mail-qt0-x22f.google.com with SMTP id e2so16607205qti.0 for ; Sat, 16 Dec 2017 20:47:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:from:message-id; bh=ch7IR58W/gtdO48hXhZtjgM9k83Q3yBgxx8ERQOOjNc=; b=l3BddEtIZfUQwXdClHOhiM+NwmCwWPoJehw4YgYdHfVGIDMo5OrnxbFXO1QOl7NFZk eXu2QfZNcjn6joxrpgZz6HM+Sf7EW5XHlQwynXeSvZdcNq/N11FB0QDf+6UjMWaJsxsk YGpSlfoiou9TvFQFNvPNBF+3CGTxJL0xu/5BeOiMg00xQcklZWbBtIFwqJtMl81gwdP4 DDnolgWc5RuVD530qdzRDBjJIisbcBHxHO5rx0eG2jJfYgaCEJ+mVfwlxJGU5FCtva5Z LIQGCjyNucPIzJyMyG2peSXWw3vuR5rCktwQKokN0VSVUyknoOIrGUvnloL5gntV7vKS 4drQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:from:message-id; bh=ch7IR58W/gtdO48hXhZtjgM9k83Q3yBgxx8ERQOOjNc=; b=BOM9RBNSlMDFI+5iIdVn7XmKL2P0MaKeFqep5Y/X8wL4ml9hgwXcwH23oQ58wjSEhy 7WuVRVKOsE8Hi/3KXdpVzQyoWCSi+jlGHB1dUzJ6jmHqQLYgcSPbjlyyt7IuJ4HdKsKH JZmBSPuZmL9kPbmNUtQIfNG0FTSNJOmEyojxqs00jaFpl6aymhS4cyAKLmiDqtJv/ZDL bXUU1PRtI0EawfvRTLQtDuhz6OBNIbI1Eb3mrau8wvllD7snn5uOQJTdVSSzYOZbZ+o6 wtMjd/v6jle8krRw5DAcDMrKCPP9pJZOABoibfsrRz1wy+8DlzaZSPrJer+tWseYUAdQ UK4A== X-Gm-Message-State: AKGB3mKxdNYRRs66OOkd7fJXegqS4Dh3KNsXR/GvtTq3Dt3TqhQO7lYT w7GuDnd0fQX5Is4osRVzQ5laA9nX X-Google-Smtp-Source: ACJfBovluTGQ4qdzXcIFofuyXPFWm5jtcD37CFyjmf1Bc4p+8WTKKlsp/OYP2mEFOProbHdiutsp4A== X-Received: by 10.200.33.143 with SMTP id 15mr29390833qty.165.1513486060950; Sat, 16 Dec 2017 20:47:40 -0800 (PST) Received: from stirge.home.huiekin.org (c-73-86-156-63.hsd1.va.comcast.net. [73.86.156.63]) by smtp.googlemail.com with ESMTPSA id v81sm6140748qkb.73.2017.12.16.20.47.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 16 Dec 2017 20:47:39 -0800 (PST) Sender: Jim Trigg Date: Sat, 16 Dec 2017 23:47:38 -0500 User-Agent: K-9 Mail for Android In-Reply-To: <875c07bd-b718-d74b-5302-d41af7476a14@gmail.com> References: <875c07bd-b718-d74b-5302-d41af7476a14@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: new portmaster fails to build devel/py-libzfs@py36 because of failing cython To: freebsd-ports@freebsd.org,Johan Hendriks From: Jim Trigg Message-ID: 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: Sun, 17 Dec 2017 04:47:42 -0000 On December 15, 2017 4:50:53 AM EST, Johan Hendriks wrote: >Hello all=2E >First of all thank you for the update of portmaster, much appreciated=2E > >When i am updating my ports, portmaster fails with the following error=2E > >=3D=3D=3D=3D> Compressing man pages (compress-man) >=3D=3D=3D>>> Starting check for runtime dependencies >=3D=3D=3D>>> Gathering dependency list for lang/cython@py36 from ports >=3D=3D=3D>>> Dependency check complete for lang/cython@py36 > >=3D=3D=3D>>> devel/py-libzfs@py36 1/10 >> lang/cython@py36 (1/1) > >=3D=3D=3D>=C2=A0 Installing for py36-cython-0=2E26 >=3D=3D=3D>=C2=A0 Checking if py36-cython already installed >=3D=3D=3D>=C2=A0=C2=A0 Registering installation for py36-cython-0=2E26 as= automatic >Installing py36-cython-0=2E26=2E=2E=2E >pkg-static: py36-cython-0=2E26 conflicts with cython3-0=2E26 (installs >files >into the same place)=2E=C2=A0 Problematic file: /usr/local/bin/cygdb-3=2E= 6 >*** Error code 70 > >Stop=2E >make: stopped in /usr/ports/lang/cython > >=3D=3D=3D>>> Installation of py36-cython-0=2E26 (lang/cython@py36) failed >=3D=3D=3D>>> Aborting update > >=3D=3D=3D>>> Update for lang/cython@py36 failed >=3D=3D=3D>>> Aborting update > >=3D=3D=3D>>> Update for devel/py-libzfs@py36 failed >=3D=3D=3D>>> Aborting update > > >Is there someting i can try or do? Question: is 3=2E6 your default python version? I've discovered that the c= urrent version of portmaster uses python default version for dependencies w= hen building a flavored port=2E Thanks, Jim Trigg --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E From owner-freebsd-ports@freebsd.org Sun Dec 17 04:23:57 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0E28EA09D8 for ; Sun, 17 Dec 2017 04:23:57 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by mx1.freebsd.org (Postfix) with ESMTP id 500CB215E for ; Sun, 17 Dec 2017 04:23:56 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp121-45-66-21.bras1.adl6.internode.on.net (HELO leader.local) ([121.45.66.21]) by ipmail07.adl2.internode.on.net with ESMTP; 17 Dec 2017 14:48:47 +1030 Subject: Re: Option vs. flavor? To: Yuri , Franco Fichtner Cc: Ben Woods , freebsd-ports@freebsd.org References: <20171216142849.GL10752@graf.pompo.net> <00619a7a-a812-1eac-bdb7-5cecfb891758@rawbw.com> <11f773c6-7f69-0a4a-d100-018d40a65f48@rawbw.com> <76d50979-5534-261e-83fa-9471a3850a54@rawbw.com> From: Shane Ambler Message-ID: <865c6db8-25e4-3129-4ea1-f9d4763b85a3@ShaneWare.Biz> Date: Sun, 17 Dec 2017 14:48:45 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <76d50979-5534-261e-83fa-9471a3850a54@rawbw.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit 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: Sun, 17 Dec 2017 04:23:57 -0000 On 17/12/2017 08:32, Yuri wrote: > On 12/16/17 13:39, Franco Fichtner wrote: >> Why not use a separate data package as optional dependency? Solves the >> conditional fetch. > > > But with the port option fetch is also conditional. There is no need to > create an extra-package. Flavours aren't for option variations, they are for the same code being linked against multiple versions of other ports, each with different dependencies - eg python 2.7/3.6 or ruby 2.2/ruby2.4 You could either make a separate port for the data files or add it as an option to the main port. Using an option for the data files, you either make it a default option so that the data is installed by anyone that installs the pkg or have it off so that anyone who wants the data files needs to build the port themselves. Having 4.5GB of optional data, I wouldn't suggest having it as an option that is on, this way the package repos don't need to add 4.5GB of data for each arch that pkgs are built for. Add a second port for data files - see games/alephone and alephone-data for an example. To prevent the pkg being added to pkg repos, add NO_PACKAGE= Data files too big, user to download manually Using a second data port means the user can download and install the data without having to compile the program. Add info about this to pkg-message for the user to read, even if it is about building the data port to get the extra data. As for adding it as an option - OPTIONS_DEFINE= EXTRADATA EXTRADATA_DISTFILES= extra_data_files.tgz post-install-EXTRADATA-on: ${COPYTREE_SHARE} ${WRKDIR}/extra_data_files ${STAGEDIR}/${DATADIR} -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-ports@freebsd.org Sun Dec 17 06:06:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFCD2EA46B8 for ; Sun, 17 Dec 2017 06:06:17 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DB2A664AF6 for ; Sun, 17 Dec 2017 06:06:17 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by mailman.ysv.freebsd.org (Postfix) id D7883EA46B7; Sun, 17 Dec 2017 06:06:17 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D730CEA46B6 for ; Sun, 17 Dec 2017 06:06:17 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF60364AF5 for ; Sun, 17 Dec 2017 06:06:17 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id ca8ced4f TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 16 Dec 2017 23:06:09 -0700 (MST) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Option vs. flavor? From: Adam Weinberger In-Reply-To: Date: Sat, 16 Dec 2017 23:06:08 -0700 Cc: "ports@freebsd.org" Content-Transfer-Encoding: 7bit Message-Id: References: To: Yuri X-Mailer: Apple Mail (2.3445.5.20) 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: Sun, 17 Dec 2017 06:06:18 -0000 > On 15 Dec, 2017, at 18:38, Yuri wrote: > > One port is small by itself, but it semi-optionally requires 4.5GB of > static data installed. > > It is possible to download this data optionally, conditional on the port > option DATA_FILES which will be "off" by default, so that the users who > need the data will install it with DATA_FILES=on. > > Alternatively, it is possible to create a flavor, something like @withData. > > > Should the option be preferred, or should the flavor be preferred? Hi Yuri, Is the port of any use without the data file? If everybody who uses the port needs the data file, I wouldn't make it an option at all. The precedent is that ports with huge data files are marked NO_PACKAGE, so there's no impact on the package builders. Make it non-optional, mark it as NO_PACKAGE, and then the port works for all users. If, however, the port IS real-world usable without the data files, I'd turn the data file into a second port. That way, package people can very easily install the NO_BUILD slave and still install the main program by pkg. # Adam -- Adam Weinberger adamw@adamw.org http://www.adamw.org From owner-freebsd-ports@freebsd.org Sun Dec 17 08:48:37 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F919E83401 for ; Sun, 17 Dec 2017 08:48:37 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7A77F69104 for ; Sun, 17 Dec 2017 08:48:37 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id 76AC0E83400; Sun, 17 Dec 2017 08:48:37 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 745F6E833FF for ; Sun, 17 Dec 2017 08:48:37 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5956269103 for ; Sun, 17 Dec 2017 08:48:37 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id vBH8mZ12045322 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 17 Dec 2017 00:48:35 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: Option vs. flavor? To: Adam Weinberger Cc: "ports@freebsd.org" References: From: Yuri Message-ID: Date: Sun, 17 Dec 2017 00:48:34 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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: Sun, 17 Dec 2017 08:48:37 -0000 On 12/16/17 22:06, Adam Weinberger wrote: > > Is the port of any use without the data file? If everybody who uses > the port needs the data file, I wouldn't make it an option at all. The > precedent is that ports with huge data files are marked NO_PACKAGE, so > there's no impact on the package builders. Make it non-optional, mark > it as NO_PACKAGE, and then the port works for all users. > > If, however, the port IS real-world usable without the data files, I'd > turn the data file into a second port. That way, package people can > very easily install the NO_BUILD slave and still install the main > program by pkg. Hi Adam, It is usable without data. Portions of the data are recommended to be downloaded into the specific directory for particular functions. Of course, it's more convenient to just a have all of it installed, and users will need all of it for all functions. This is the large physics package called Geant4 for simulation of the passage of particles through matter. https://reviews.freebsd.org/D13504 Yuri From owner-freebsd-ports@freebsd.org Sun Dec 17 09:12:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15D18E83D84 for ; Sun, 17 Dec 2017 09:12:59 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CC30569C6D for ; Sun, 17 Dec 2017 09:12:58 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from [134.76.11.225] (helo=email.stud.uni-goettingen.de) by mailer.gwdg.de with esmtp (Exim 4.80) (envelope-from ) id 1eQV06-0003iv-FJ; Sun, 17 Dec 2017 10:12:50 +0100 Received: from UM-EXCHT-A01.um.gwdg.de (134.76.9.210) by um-excht-s1.um.gwdg.de (134.76.9.213) with Microsoft SMTP Server (TLS) id 14.3.361.1; Sun, 17 Dec 2017 10:12:50 +0100 Received: from krabat.raven.hur (91.8.156.113) by email.gwdg.de (134.76.9.210) with Microsoft SMTP Server (TLS) id 14.3.361.1; Sun, 17 Dec 2017 10:12:49 +0100 Subject: Re: Flavor or not for this port? From: Rainer Hurling To: L.Bartoletti CC: References: <46cbd287-186f-9b92-f2a7-d6884c681040@gwdg.de> Message-ID: <37d007c1-0315-5b23-7357-5dc3fcb836fc@gwdg.de> Date: Sun, 17 Dec 2017 10:12:49 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <46cbd287-186f-9b92-f2a7-d6884c681040@gwdg.de> Content-Type: text/plain; charset="utf-8" Content-Language: de-DE Content-Transfer-Encoding: 8bit X-Spam-Level: - X-Virus-Scanned: (clean) by clamav 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: Sun, 17 Dec 2017 09:12:59 -0000 Am 02.11.2017 um 07:41 schrieb Rainer Hurling: > Am 02.11.2017 um 07:13 schrieb L.Bartoletti: >> Hi, >> >> I want to take x11-toolkits/qwt{5,6}-* >> >> Both are built for Qt4. I especially need qwt6 for Qt5. Since we have >> flavors. Is it better to add a Qt5 flavor for Qwt6 or simply add a >> x11-toolkits/qwt6-qt5 (like security/qtkeychain-qt{4,5} ?) >> >> Thanks. >> >> Regards. >> >> Loïc > > > Hi Loïc, > > Thanks for your dedication. I am very interested in a qwt6-qt5 port, > since it is needed for the upcoming version 3.0 of graphics/qgis :) > > Sorry for my inexperience. In case of adding the qwt6-qt5 as a flavor, > should we expect any change or restriction in the way, it would be used > as a dependency of e.g. QGIS? > > Thanks for any answer. > > Best wishes, > Rainer Hi Loïc, Again about x11-toolkits/qwt{5,6}-* Now, that we have our first real world experiences with FLAVORS, it seems to be functional to use flavors in this context. Something like x11-toolkits/qwt6@qt4 x11-toolkits/qwt6@qt5 A bit tricky could be, that USE_QT* are different in both cases: USE_QT4= corelib gui opengl svg xml moc_build USE_QT5= core gui opengl svg xml printsupport qmake_build widgets What do you think? Best wishes, Rainer From owner-freebsd-ports@freebsd.org Sun Dec 17 09:46:48 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5CD5E84786 for ; Sun, 17 Dec 2017 09:46:48 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 612FC6ABDB; Sun, 17 Dec 2017 09:46:48 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:792b:4c31:d2fe:1451]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 5B9C0E493; Sun, 17 Dec 2017 09:46:45 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Subject: Re: Can we have multiple flavors for a port? To: Stefan Esser , FreeBSD Ports ML Cc: FreeBSD Port-Manager References: <6ed4ac6e-a075-0fc0-a3da-371a46a9e977@FreeBSD.org> <09760447-455d-5de0-36a9-c978d84cfb72@freebsd.org> From: Matthew Seaman Message-ID: <98b88bc3-a4c1-bc1a-528e-612ed060cef6@FreeBSD.org> Date: Sun, 17 Dec 2017 09:46:44 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <09760447-455d-5de0-36a9-c978d84cfb72@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="sBFlrFoAijXmn17bsOandV1KQ1CFgeCpU" 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: Sun, 17 Dec 2017 09:46:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --sBFlrFoAijXmn17bsOandV1KQ1CFgeCpU Content-Type: multipart/mixed; boundary="n7OFfsmfQG26ispn5W4EbMh69dGFW1EVO"; protected-headers="v1" From: Matthew Seaman To: Stefan Esser , FreeBSD Ports ML Cc: FreeBSD Port-Manager Message-ID: <98b88bc3-a4c1-bc1a-528e-612ed060cef6@FreeBSD.org> Subject: Re: Can we have multiple flavors for a port? References: <6ed4ac6e-a075-0fc0-a3da-371a46a9e977@FreeBSD.org> <09760447-455d-5de0-36a9-c978d84cfb72@freebsd.org> In-Reply-To: <09760447-455d-5de0-36a9-c978d84cfb72@freebsd.org> --n7OFfsmfQG26ispn5W4EbMh69dGFW1EVO Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 16/12/2017 14:24, Stefan Esser wrote: > Am 16.12.17 um 14:51 schrieb Matthew Seaman: >> >> I have a review up to add a USES=3Ddjango -- >> https://reviews.freebsd.org/D12592 which I'm now modifying to be FLAVO= RS >> compatible given that has hit the tree. >> >> Now, we currently have ports for 4 different versions of django (1.8, >> 1.10, 1.11, 2.0) and the obvious next move is to add django-based >> flavouring. Currently, most django ports depend on django-1.8, with a= >> few depending on django-1.10, but this I think is mostly due to inerti= a >> and django ports should be compatible with more recent versions. Havi= ng >> four different versions of django in ports seems excessive -- so, for >> the sake of argument I'd cut that down to just django-1.11 and django-= 2.0 >> >> But this is all python code, and the python flavouring would also appl= y... >> >> Given that django-2.0 requires python-3.5+ we end up with the followin= g >> combinations: >> >> py27 django111 >> py36 django111 >> py36 django20 >> >> and there's some 104 django ports which will mostly end up needing all= >> three of these variants built -- so as combinatorial explosions go, it= 's >> not particularly earth-shattering. >> >> However, my questions are: >> >> - Is it possible or desirable to have multiple flavourings like this= ? >> >> - If so, what should the syntax look like for specifying a particula= r >> combination? eg. www/py-django-mezzanine@py27+django111 ? >=20 > I asked portmgr@ the same question when I started to work on portmaster= > and did not want to implement a solution that does only support a singl= e > flavor per port (or rather, waste time and effort on a portmaster versi= on > that only supported 1 flavor per port, when there were plans to support= > multiple flavors in the ports framework in the future). >=20 > The answer I received was very clear: There can only be 1 flavor per po= rt > and there are no plans to remove that restriction. >=20 > I questioned the wise-ness of that decision, but had better use for my > time than to continue arguing, that multi-flavor support was probably > going to be required very soon. >=20 >=20 > My questions were specifically, how a dependency with multiple flavors > should be specified (e.g. "@py36@xyz") and how to query a port for this= > case. The same notation should be used in the MOVED file in such a case= =2E >=20 > The order of flavors added to an origin must either be ignored by all > tools operating on them (which precludes simple string comparisons to > see whether one origin+flavors is identical to another one) or should > be required to follow some (e.g.) lexical order. >=20 >=20 > I'd also like to see the flavor(s) (if any) become part of the port ori= gin > (or some other variable in the PKG DB that can easily be queried). The > value should be identical to the format in dependencies and the MOVED > file to simplify tools like portmaster, which currently must execute a > complex series of queries to get at that information. Heh. I wrote the package annotation functionality, but I never anticipated the way that it has come to be used. I just thought of it as a way for package builders and end users to add notes to their package database, with no real functional effect. Instead, now it's being used as the quick and simple way to add novel metadata to packages, and to affect the way pkg(8) goes about solving dependency chai= ns. I have some mixed feelings about this. We used to have significant database schema churn whenever some metadata change happened in pkg(8), which made upgrading pkg(8) a bit more risky and harder to back-out than ideal. Now though, you can just create an annotation. No low-level schema change needed. On the other hand, you can't use pkg-query(8) or pkg-rquery(8) or similar to select and display packages according to the new metadata items like flavor. > The origin@flavor does not encode the information previously contained > in just the origin. >=20 >=20 > IMHO, multi-flavor support should have been one of the initial consider= ations > when designing the flavor extension to the ports system! Hmmm... There is another consideration here. Most of the django stuff I'm looking at is pure python code, and not dependent on against linkage to any specific shared library. Which means that the packages for the different flavours would be basically identical except for the metadata tracking the dependency chain. Making a raft of such similar packages, replicating the package file content each time strikes me as wasteful of time and resources. Why can't we express the alternate possibilities in the package metadata and have one package that fits all cases? I recall a proposal about "variable dependencies" being discussed at BSDCan a few years back -- is this anywhere on the roadmap? Potentially this would apply to many of the packages for interpreted or byte-compiled languages in the tree -- so Perl, Ruby, PHP, Java and in principle Python, although that has been complicated by the incompatible changes involved between python-2.7 and python-3.x. Cheers, Matthew --n7OFfsmfQG26ispn5W4EbMh69dGFW1EVO-- --sBFlrFoAijXmn17bsOandV1KQ1CFgeCpU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKoBAEBCgCSFiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlo2PQVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcUHG1hdHRoZXdA ZnJlZWJzZC5vcmcACgkQAFE/EOCp5Oegew/+I4Zya6dbHOouBvoRV/SJ+6jfxQWO 1zAH72+P9Y273xfmPjQYz9+uln3P6QBn4qzVZaOsg+diff/+oFUuhWaPaqNn0QyJ QDDD5RvF1G2Qs14j8XT3h72X1hVpRNVP4Vz/yghv8ETJpPUOcgIExQrfgY0yMU5a /bigTqmHr0mT3KYybbNwqQOFJH2iPXKqy1CQ/rdLFLkX7ah60AhVtR7dWUGvTPd6 ussgFif8Lj0BqIztoazo8NkQH1Gzdk5cCvh6pr6/8uq57ZWeiZDwgeAVYhDwJ2dl 1MfkQCJwFwvmsv/h44mOpbMmfCTMwBt7R6Uu62Z0aHBCjLalTlocy98v4sgCctfo zHY+BzUG0+FyYwVl9QPqqk9ZWsWQWPjvP9pBrrxJe+MlXHvhag2hqNdvVIDISqTW NzLM763uyZtZDGFmbwP6d0XLu9JqEmX8A6zsG9HGF4sczyMqz9dGJqGI8mhm59Cm uEsDjGEs69unAXoWpwanUenR8iFzNuJ7YPaEFAdIREKHNdvd9ggxioV3zUpBon3I 4m81hlHUY5mupqZFIX3mospFShCvLDpCaSyrtS37H9wreZObO9qLSmoSNi6/RcG2 MmYASsziCBcixj43b1lQDEjl3g4QHERdyhinr/HzCLnnJ+QZY2f+Qw5432UlTxN5 NQ+xP9yn67hg0/A= =Kp7g -----END PGP SIGNATURE----- --sBFlrFoAijXmn17bsOandV1KQ1CFgeCpU-- From owner-freebsd-ports@freebsd.org Sun Dec 17 13:01:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A08D5E8925F for ; Sun, 17 Dec 2017 13:01:54 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout07.t-online.de (mailout07.t-online.de [194.25.134.83]) (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 383EC6FA43 for ; Sun, 17 Dec 2017 13:01:53 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd34.aul.t-online.de (fwd34.aul.t-online.de [172.20.26.145]) by mailout07.t-online.de (Postfix) with SMTP id C8A3B426C3AC; Sun, 17 Dec 2017 14:01:44 +0100 (CET) Received: from Stefans-MBP-2.fritz.box (Gvpeq4ZVwhmJaAQfwQPkwVXnUf1O0iqNWjy9upanEc-3OGPAwodsu-OOEgmNu+CZ1-@[84.154.97.124]) by fwd34.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1eQYZZ-19DOIy0; Sun, 17 Dec 2017 14:01:41 +0100 Subject: Re: new portmaster fails to build devel/py-libzfs@py36 because of failing cython To: Jim Trigg , freebsd-ports@freebsd.org, Johan Hendriks References: <875c07bd-b718-d74b-5302-d41af7476a14@gmail.com> From: Stefan Esser Message-ID: <663c1678-7f32-7dd4-867f-b5fd3f862222@freebsd.org> Date: Sun, 17 Dec 2017 14:01:41 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit X-ID: Gvpeq4ZVwhmJaAQfwQPkwVXnUf1O0iqNWjy9upanEc-3OGPAwodsu-OOEgmNu+CZ1- X-TOI-MSGID: 5f3c257e-7ef9-434a-b9a3-398c67149cc7 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: Sun, 17 Dec 2017 13:01:54 -0000 Am 17.12.17 um 05:47 schrieb Jim Trigg: > > > On December 15, 2017 4:50:53 AM EST, Johan Hendriks wrote: >> Hello all. >> First of all thank you for the update of portmaster, much appreciated. >> >> When i am updating my ports, portmaster fails with the following error. >> >> ====> Compressing man pages (compress-man) >> ===>>> Starting check for runtime dependencies >> ===>>> Gathering dependency list for lang/cython@py36 from ports >> ===>>> Dependency check complete for lang/cython@py36 >> >> ===>>> devel/py-libzfs@py36 1/10 >> lang/cython@py36 (1/1) >> >> ===>  Installing for py36-cython-0.26 >> ===>  Checking if py36-cython already installed >> ===>   Registering installation for py36-cython-0.26 as automatic >> Installing py36-cython-0.26... >> pkg-static: py36-cython-0.26 conflicts with cython3-0.26 (installs >> files >> into the same place).  Problematic file: /usr/local/bin/cygdb-3.6 >> *** Error code 70 >> >> Stop. >> make: stopped in /usr/ports/lang/cython >> >> ===>>> Installation of py36-cython-0.26 (lang/cython@py36) failed >> ===>>> Aborting update >> >> ===>>> Update for lang/cython@py36 failed >> ===>>> Aborting update >> >> ===>>> Update for devel/py-libzfs@py36 failed >> ===>>> Aborting update >> >> >> Is there someting i can try or do? Yes, try the latest version of portmaster that I just committed ... Adding flavor support to portmaster was complicated by the way parameters are passed from one phase (config options, dependency checks, ...) to the final build process. It worked if either the port origin or package name changed when a port was upgraded, but not if both were changed simultaneously. And that was just the case with cython, were the origin changed from "lang/cython3" to "lang/cython" (with flavor py36) and the package name from "cython3-0.26" to "py36-cython-0.26". There was no way for portmaster to make the connection between the old and new version if both changed at a time, and thus it failed to deinstall the old version before installing the new one. I plan to completely change the way state is maintained in portmaster (from implicit by some global variables being set) to explicit state variables, and at the same time pass parameters explicitly. But this will be a major change, which will void any patches that have been attached to PRs and Issues, and will make it much harder to work on them. > Question: is 3.6 your default python version? I've discovered that the current version > of portmaster uses python default version for dependencies when building a flavored > port. Dependencies should be built based on the different *_DEPENDS variables defined in the port's Makefile and the *.mk files of the port framework. Portmaster currently only accepts the notation of "origin@flavor" when a new port of a given flavor is to be installed. I'm planning to add a --flavor option for that purpose, but I have to be careful not to introduce any regressions by doing so. Regards, STefan From owner-freebsd-ports@freebsd.org Sun Dec 17 13:11:22 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 944D7E896AB for ; Sun, 17 Dec 2017 13:11:22 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (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 582C36FF8E for ; Sun, 17 Dec 2017 13:11:21 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd22.aul.t-online.de (fwd22.aul.t-online.de [172.20.26.127]) by mailout12.t-online.de (Postfix) with SMTP id 7B10441E9F7A; Sun, 17 Dec 2017 14:11:14 +0100 (CET) Received: from Stefans-MBP-2.fritz.box (G59lJsZQ8huN8TxoX+t1IAVXErsFx4zUYrUUswpTZxTxyp-vHD7nYCNGaDCp2uJQ7N@[84.154.97.124]) by fwd22.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1eQYik-40QrUu0; Sun, 17 Dec 2017 14:11:10 +0100 Subject: Re: OSS Audio To: blubee blubeeme , Sid Cc: Yuri , fjwcash@gmail.com, FreeBSD Ports References: From: Stefan Esser Message-ID: <784ef8bf-c9ab-80a0-dae2-b1a0445ce9bf@freebsd.org> Date: Sun, 17 Dec 2017 14:11:10 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-ID: G59lJsZQ8huN8TxoX+t1IAVXErsFx4zUYrUUswpTZxTxyp-vHD7nYCNGaDCp2uJQ7N X-TOI-MSGID: 88ae7cfe-b8ae-4af2-bb77-a12560a5bf6c 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: Sun, 17 Dec 2017 13:11:22 -0000 Am 17.12.17 um 02:06 schrieb blubee blubeeme: > This is why I am bringing up the issue and why I said the first step would > be porting the proper 4Front OSS into the kernel. > > It doesn't have to be the default at first but if it's not in the kernel > why bother wasting time to have it rejected because of all the > misconceptions I've been dealing with in these threads. > > Add 4Front OSS to the kernel > Use the 4.x API/ Documentation > Add it to an audio programming section of FBSD Handbook > Upstream changes that make sense > Simplify audio programming, documentation, all those audio sound servers > Port device drivers to the OSS Device Driver API: > http://manuals.opensound.com/sources/drv_index.html Do you propose to just update the code to what 4Front provides? This may work for you as individual user, but the 4Front license makes it impossible to commit that version to FreeBSD. (That was the reason to stay at a reasonably licensed version, very long ago.) Or do you propose a clean-room implementation that in the end is fully compatible with 4Front OSS 4.x, but does not violate their license and intellectual property rights? You are welcome to start with such a clean-room implementation and it may even be accepted into FreeBSD, once you are ready (provided there really is no risk of legal problems in any part of the world). Regards, STefan From owner-freebsd-ports@freebsd.org Sun Dec 17 13:20:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C9C4E89A99 for ; Sun, 17 Dec 2017 13:20:46 +0000 (UTC) (envelope-from gary@hayers.org) Received: from mailout.easydns.com (mailout.easydns.com [64.68.203.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D196F70448 for ; Sun, 17 Dec 2017 13:20:45 +0000 (UTC) (envelope-from gary@hayers.org) Received: from localhost (localhost [127.0.0.1]) by mailout.easydns.com (Postfix) with ESMTP id EDA90E9D98 for ; Sun, 17 Dec 2017 13:10:48 +0000 (UTC) Received: from mailout.easydns.com ([127.0.0.1]) by localhost (emo11-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FDF7xMoInbrh for ; Sun, 17 Dec 2017 13:10:48 +0000 (UTC) Received: from mx1.hayers.org (cpc115706-tilb12-2-0-cust98.20-1.cable.virginm.net [82.14.148.99]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout.easydns.com (Postfix) with ESMTPSA id B143CDF55B for ; Sun, 17 Dec 2017 13:10:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx1.hayers.org (Postfix) with ESMTP id EF2E130ED5 for ; Sun, 17 Dec 2017 13:10:45 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hayers.org; s=hayers; t=1513516246; bh=Qd11lG4pPZo9RTgpHvsc9t/0wl6bxx/cUAs6iAOPk60=; h=To:From:Subject:Date; b=Z2L/Ili//td7MsphAGvHlvEvV1xQtDvSyKCA2tAxiAEzpTvWcAgVjPQXaliua6sJ5 pVX5lExPVfBhAhuW0JjKW2kXUgJIQL5/AfbzDrkObYRvz/UZd+3A6qChG4Jwr1Y/VF DH7a6YGkbCtuPJEY1gLo3Aq5thXWanSB4Vw+RPD8= Received: from mx1.hayers.org ([127.0.0.1]) by localhost (mx1.hayers.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 02401-02 for ; Sun, 17 Dec 2017 13:10:32 +0000 (GMT) Received: from [192.168.0.2] (zeus.hayers.org [94.173.133.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: gary@hayers.org) by mx1.hayers.org (Postfix) with ESMTPSA id 5606630ECA for ; Sun, 17 Dec 2017 13:10:32 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hayers.org; s=hayers; t=1513516232; bh=Qd11lG4pPZo9RTgpHvsc9t/0wl6bxx/cUAs6iAOPk60=; h=To:From:Subject:Date; b=IN9zqTSi6ZkHz9aFocB+mmEih/+jBVJCEypFGt0yQYb88r8ga76WP2eDkZMPCBt1w 00VNOf9n/t7TqBxMwXa+hdA97TeQhsatY5tfzZIhrzqOSLSO7F5Tn6qrTyYse1c/FY U6loxNLAeULPO7Zzm79Z1ALsS7QxPEzUiuOqQ5Ds= To: freebsd-ports@freebsd.org From: "Gary J. Hayers" Subject: Poudriere build of Python36 Message-ID: <6de86882-d7d9-4b37-50b4-06bb890160bd@hayers.org> Date: Sun, 17 Dec 2017 13:10:19 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV-SpamAssassin (Unix/FreeBSD) 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: Sun, 17 Dec 2017 13:20:46 -0000 Hi all, Can anyone offer some advice as to what's happening here? =>> Building lang/python36 build started at Sun Dec 17 12:35:43 GMT 2017 port directory: /usr/ports/lang/python36 package name: python36-3.6.3 building for: FreeBSD 11:1-AMD64-HEAD-ports-job-04 11.1-STABLE FreeBSD 11.1-STABLE amd64 maintained by: python@FreeBSD.org Makefile ident: $FreeBSD: head/lang/python36/Makefile 451202 2017-10-04 10:55:25Z sunpoet $ Poudriere version: 3.2.3 Host OSVERSION: 1101506 Jail OSVERSION: 1101506 Job Id: 04 ---Begin Environment--- SHELL=/bin/csh OSVERSION=1101506 UNAME_v=FreeBSD 11.1-STABLE UNAME_r=11.1-STABLE BLOCKSIZE=K MAIL=/var/mail/root STATUS=1 SAVED_TERM=screen MASTERMNT=/usr/home/poudriere/data/.m/11:1-AMD64-HEAD-ports/ref UID=0 PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin POUDRIERE_BUILD_TYPE=bulk OLDPWD=/usr/home/poudriere/data/.m/11:1-AMD64-HEAD-ports/ref/.p P_PORTS_FEATURES=FLAVORS SELECTED_OPTIONS PWD=/usr/home/poudriere/data/.m/11:1-AMD64-HEAD-ports/ref/.p/pool MASTERNAME=11:1-AMD64-HEAD-ports SCRIPTPREFIX=/usr/local/share/poudriere USER=root HOME=/root P_PYTHON_MAJOR_VER=2 POUDRIERE_VERSION=3.2.3 SCRIPTPATH=/usr/local/share/poudriere/bulk.sh GID=0 LIBEXECPREFIX=/usr/local/libexec/poudriere LOCALBASE=/usr/local POUDRIEREPATH=/usr/local/bin/poudriere ---End Environment--- ---Begin Poudriere Port Flags/Env--- PORT_FLAGS= PKGENV= FLAVOR= DEPENDS_ARGS= MAKE_ARGS= ---End Poudriere Port Flags/Env--- ---Begin OPTIONS List--- ===> The following configuration options are available for python36-3.6.3: DEBUG=off: Build with debugging support IPV6=off: IPv6 protocol support LIBFFI=off: Use libffi from ports instead of bundled version NLS=off: Enable gettext support for the locale module PYMALLOC=off: Enable specialized mallocs THREADS=off: Threading support ====> Hash Algorithm (PEP-456): you can only select none or one of them FNV=off: Modified Fowler-Noll-Vo Algorithm SIPHASH=off: SipHash24 Algorithm ===> Use 'make config' to modify these settings ---End OPTIONS List--- running install_scripts copying build/scripts-3.6/idle3.6 -> /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/bin copying build/scripts-3.6/pyvenv-3.6 -> /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/bin copying build/scripts-3.6/2to3-3.6 -> /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/bin copying build/scripts-3.6/pydoc3.6 -> /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/bin changing mode of /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/bin/idle3.6 to 755 changing mode of /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/bin/pyvenv-3.6 to 755 changing mode of /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/bin/2to3-3.6 to 755 changing mode of /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/bin/pydoc3.6 to 755 rm /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/python3.6/lib-dynload/_sysconfigdata__freebsd11_.py rm -r /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/python3.6/lib-dynload/__pycache__ install -m 0644 ./Misc/python.man /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/man/man1/python3.6.1 if test "xno" != "xno" ; then case no in upgrade) ensurepip="--altinstall --upgrade" ;; install|*) ensurepip="--altinstall" ;; esac; LD_LIBRARY_PATH=/wrkdirs/usr/ports/lang/python36/work/Python-3.6.3 ./python -E -m ensurepip $ensurepip --root=/wrkdirs/usr/ports/lang/python36/work/stage/ ; fi /bin/rm -f /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/libpython3.so # Upstream Issue: http://bugs.python.org/issue17975 for i in /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/python3.6/lib-dynload/*.so; do /usr/bin/strip $i; done # Strip shared extensions install -m 0644 /wrkdirs/usr/ports/lang/python36/work/Python-3.6.3/Tools/gdb/libpython.py /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/libpython3.6.so.1.0-gdb.py ====> Compressing man pages (compress-man) =========================================================================== =================================================== ===> Building package for python36-3.6.3 pkg-static: Unable to access file /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/python3.6/lib-dynload/_asyncio.so:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/python3.6/lib-dynload/_multiprocessing.so:No such file or directory *** Error code 1 Stop. make: stopped in /usr/ports/lang/python36 =>> Cleaning up wrkdir ===> Cleaning for python36-3.6.3 build of lang/python36 | python36-3.6.3 ended at Sun Dec 17 12:38:09 GMT 2017 build time: 00:02:26 !!! build failure encountered !!! To see the entire build log check here https://pkg.hayers.org/data/11:1-AMD64-HEAD-ports/2017-12-17_12h03m17s/logs/errors/python36-3.6.3.log Any help much appreciated. Many thanks, -- Regards, Gary J. Hayers gary@hayers.org PGP Signature https://www.hayers.org/pgp From owner-freebsd-ports@freebsd.org Sun Dec 17 13:23:34 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EED7CE89CBF for ; Sun, 17 Dec 2017 13:23:34 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D412370764 for ; Sun, 17 Dec 2017 13:23:34 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D08F8E89CBE; Sun, 17 Dec 2017 13:23:34 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D023AE89CBD for ; Sun, 17 Dec 2017 13:23:34 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B65F170763 for ; Sun, 17 Dec 2017 13:23:34 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id vBHDNYk9038297 for ; Sun, 17 Dec 2017 13:23:34 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id vBHDNY3F038295; Sun, 17 Dec 2017 13:23:34 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201712171323.vBHDNY3F038295@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Sun, 17 Dec 2017 13:23:34 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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: Sun, 17 Dec 2017 13:23:35 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ audio/qjackctl | 0.4.5 | 0.5.0 ------------------------------------------------+-----------------+------------ audio/qsynth | 0.4.4 | 0.5.0 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Sun Dec 17 13:57:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9816FE8A81A for ; Sun, 17 Dec 2017 13:57:40 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C24571485; Sun, 17 Dec 2017 13:57:40 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x231.google.com with SMTP id h12so7160543iof.6; Sun, 17 Dec 2017 05:57:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eJpcmVaj4VsgDWfbmhvG+ew9NS34WMWxzok6p22DFj8=; b=QVVP7vvT9duCB7Gh8wBaXroZZ5EOUF/arQ390oUe85bVHK5ar6H92Lqt4cqeg7Pjsr Kuux9PHkOfEuvKVrR3LhlGGdv67GDIIVHU4vXghg95f/diZ01mzfBU5GuP7fqND9C0PQ G298m8evZ1dmBuHj/tkOHu1srEkxZnhJLKzcjeK0bF0KwiNlSPCXHjiY2ZmPgdBSYoZE VkEUhpynYBLUG2MBzqbC3pM8qMDzHyB4dABEmWJaMCDwmoZtffJFV9VyzVBFtPrWKmfk LM4fd8dKiWkdgNt1JEzp/sCnRXtkyZG2t+y+yNtRzbDTiY7XgGcnRDD55BkXoFcgIFkU IXug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eJpcmVaj4VsgDWfbmhvG+ew9NS34WMWxzok6p22DFj8=; b=jUJrAFlOY+GAPIpesaMg4YF1BZdLIcH9oRvYDP5WgI/n1dP6/RIloMDVm4nvNXJASF yzJaJmK+ZXCZsyB8NAtFX8pEnqvvxsfNoNfbarfQzVZ2ZvA3IkOmDFysw2Wti0xDFjzS UODx2qpOoHru75qGOyoj2UlwoqTaTUGI0/Hdc6cIiedc2f1zDXaJNzFV3uZaHQu3hleH 7eyw4yGeeTxNYRgjVbfs6ZM6CcmQbCXNo/gFSmXHNS0c/yY5fI0yvpcamgLV192IpwYw FxpoXV1l8zboVyxX/j9qpFmrLe6Rq9S9cewCdAvsN6i5xJq9bjD8MbhS41+ZA5I93ml/ xIdQ== X-Gm-Message-State: AKGB3mL5CQcTJIU7fH2d1mC14nMU2wFdndCLIqmOcr1W9mk/0ADrrYR5 dXM+0SWB7vnddzYfHLL+s3dt177fFw03iPTWIOhMeNfL X-Google-Smtp-Source: ACJfBosDvEgx/MsFnyD4lxbhidkXwUCXwVMMDIfgAxJd3ckqmybvZGkOdJKiczknd2Qm+tOGL+6OmIE3dDV03Gv/KEc= X-Received: by 10.107.157.82 with SMTP id g79mr9789335ioe.296.1513519058864; Sun, 17 Dec 2017 05:57:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Sun, 17 Dec 2017 05:57:38 -0800 (PST) In-Reply-To: <784ef8bf-c9ab-80a0-dae2-b1a0445ce9bf@freebsd.org> References: <784ef8bf-c9ab-80a0-dae2-b1a0445ce9bf@freebsd.org> From: blubee blubeeme Date: Sun, 17 Dec 2017 21:57:38 +0800 Message-ID: Subject: Re: OSS Audio To: Stefan Esser Cc: Sid , Yuri , Freddie Cash , FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Sun, 17 Dec 2017 13:57:40 -0000 On Sun, Dec 17, 2017 at 9:11 PM, Stefan Esser wrote: > Am 17.12.17 um 02:06 schrieb blubee blubeeme: > > This is why I am bringing up the issue and why I said the first step > would > > be porting the proper 4Front OSS into the kernel. > > > > It doesn't have to be the default at first but if it's not in the kernel > > why bother wasting time to have it rejected because of all the > > misconceptions I've been dealing with in these threads. > > > > Add 4Front OSS to the kernel > > Use the 4.x API/ Documentation > > Add it to an audio programming section of FBSD Handbook > > Upstream changes that make sense > > Simplify audio programming, documentation, all those audio sound servers > > Port device drivers to the OSS Device Driver API: > > http://manuals.opensound.com/sources/drv_index.html > > Do you propose to just update the code to what 4Front provides? > > This may work for you as individual user, but the 4Front license This is not true. The source code is distributed under different license based on the OS. Look at audio/oss src build process. If the code is compiled on Linux it has some Linux type gpl license, if it's on a *BSD it has BSD license, there's also license that suits other platforms as well. There were some closed sourced parts because Hannu was trying different license models to pay the bills but instead of supporting him, everyone forked his code and left so he went on to do something else. > makes > it impossible to commit that version to FreeBSD. (That was the reason > to stay at a reasonably licensed version, very long ago.) > > It seems like everyone has this cloud of OSS is crap floating around in their minds, the guy just wanted to be able to work on his code and not have to write windows drivers at the same time, that's not how things played out. > Or do you propose a clean-room implementation that in the end is fully > compatible with 4Front OSS 4.x, but does not violate their license and > intellectual property rights? > > You are welcome to start with such a clean-room implementation and it > may even be accepted into FreeBSD, once you are ready (provided there > really is no risk of legal problems in any part of the world). > > Regards, STefan > FreeBSD doesn't have many if any audio programmers, most of the programs are ported from other platforms that do not follow good practices, then new devs come along, copy the old coding style and keep on perpetuating the bad habits. I propose properly implementing 4Font OSS 4.x in the FreeBSD kernel, properly using the API as documented on 4Front website. Have 4Front OSS the default audio system in FreeBSD Having proper Audio programming guide in the FreeBSD handbook ditch sndio and all that other stuff and move forward with a clean start and proper documentation for new audio programs. That's why I brought this issue up on this list is to try and hear from people who are doing audio but instead it's just a bunch of noise and misconceptions. From owner-freebsd-ports@freebsd.org Sun Dec 17 14:32:22 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47DC9E8B403 for ; Sun, 17 Dec 2017 14:32:22 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 335627228C for ; Sun, 17 Dec 2017 14:32:22 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by mailman.ysv.freebsd.org (Postfix) id 32B46E8B402; Sun, 17 Dec 2017 14:32:22 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 325AFE8B400 for ; Sun, 17 Dec 2017 14:32:22 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 996277228B for ; Sun, 17 Dec 2017 14:32:21 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 3e666f29 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 17 Dec 2017 07:32:19 -0700 (MST) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Option vs. flavor? From: Adam Weinberger In-Reply-To: Date: Sun, 17 Dec 2017 07:32:17 -0700 Cc: "ports@freebsd.org" Content-Transfer-Encoding: 7bit Message-Id: <0CE3611A-F100-4443-93B4-68A0A83F162B@adamw.org> References: To: Yuri X-Mailer: Apple Mail (2.3445.5.20) 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: Sun, 17 Dec 2017 14:32:22 -0000 > On 17 Dec, 2017, at 1:48, Yuri wrote: > > On 12/16/17 22:06, Adam Weinberger wrote: >> Is the port of any use without the data file? If everybody who uses the >> port needs the data file, I wouldn't make it an option at all. The >> precedent is that ports with huge data files are marked NO_PACKAGE, so >> there's no impact on the package builders. Make it non-optional, mark it >> as NO_PACKAGE, and then the port works for all users. >> >> If, however, the port IS real-world usable without the data files, I'd >> turn the data file into a second port. That way, package people can very >> easily install the NO_BUILD slave and still install the main program by >> pkg. > > > Hi Adam, > > > It is usable without data. Portions of the data are recommended to be > downloaded into the specific directory for particular functions. Of > course, it's more convenient to just a have all of it installed, and > users will need all of it for all functions. > > This is the large physics package called Geant4 for simulation of the > passage of particles through matter. https://reviews.freebsd.org/D13504 Ah okay. Then I'd say, make a slave port that just fetches/extracts/installs the data files, and an option in the Geant4 master port that defaults to off. Set the slave port to NO_PACKAGE. I wouldn't go the flavor route, because the purpose of flavors is to generate multiple packages. The 4.5GB data files shouldn't have a package, so options is the way to go. # Adam -- Adam Weinberger adamw@adamw.org http://www.adamw.org From owner-freebsd-ports@freebsd.org Sun Dec 17 17:53:55 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 482D5E90354 for ; Sun, 17 Dec 2017 17:53:55 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 34B037828C for ; Sun, 17 Dec 2017 17:53:55 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: by mailman.ysv.freebsd.org (Postfix) id 313FBE90353; Sun, 17 Dec 2017 17:53:55 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30F08E90351 for ; Sun, 17 Dec 2017 17:53:55 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F0AD07828B for ; Sun, 17 Dec 2017 17:53:54 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id vBHHrlWQ004624 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 17 Dec 2017 09:53:47 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id vBHHrkTT004623; Sun, 17 Dec 2017 09:53:46 -0800 (PST) (envelope-from fbsd) Date: Sun, 17 Dec 2017 09:53:46 -0800 From: bob prohaska To: ports@freebsd.org Cc: bob prohaska Subject: Stopping make in a port Message-ID: <20171217175346.GA4610@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) 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: Sun, 17 Dec 2017 17:53:55 -0000 >From time to time I would like to abort a make session in /usr/ports. In the past, one could get away with simply using kill or ctrl-c, but now that seems to keep make from restarting, with an error along the lines of "can't cd to /tmp/..... which does not seem easy to fix. What is the appropriate way to stop and restart make in /usr/ports? Thanks for reading, bob prohaska From owner-freebsd-ports@freebsd.org Sun Dec 17 18:10:55 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C887E9075E for ; Sun, 17 Dec 2017 18:10:55 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 16A8C789C9 for ; Sun, 17 Dec 2017 18:10:55 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id 160CEE9075D; Sun, 17 Dec 2017 18:10:55 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15B73E9075C for ; Sun, 17 Dec 2017 18:10:55 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 04C6E789C8 for ; Sun, 17 Dec 2017 18:10:54 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id vBHIArgV098304 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 17 Dec 2017 10:10:54 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: Option vs. flavor? Cc: "ports@freebsd.org" References: <0CE3611A-F100-4443-93B4-68A0A83F162B@adamw.org> From: Yuri Message-ID: <2e1a60e4-6800-49a9-aaca-73a1a856c7a3@rawbw.com> Date: Sun, 17 Dec 2017 10:10:52 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <0CE3611A-F100-4443-93B4-68A0A83F162B@adamw.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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: Sun, 17 Dec 2017 18:10:55 -0000 On 12/17/17 06:32, Adam Weinberger wrote: > > Ah okay. Then I'd say, make a slave port that just > fetches/extracts/installs the data files, and an option in the Geant4 > master port that defaults to off. Set the slave port to NO_PACKAGE. Ok, I will do it this way. > I wouldn't go the flavor route, because the purpose of flavors is to > generate multiple packages. The 4.5GB data files shouldn't have a > package, so options is the way to go. I was actually wondering, why the use of flavors is such a bad idea in this case? I know that flavors weren't originally intended for this, but it might seem that they lend themselves very well to such use. One can have a virtual flavor, say @withHugeData. It doesn't get built by default because it is virtual. At the same time, somebody who needs data can always run 'poudriere .... thepkg@withHudeData' and build the needed flavor of the package. What would be the downside of such use, besides it being the use of a completely different kind than anticipated? Yuri From owner-freebsd-ports@freebsd.org Sun Dec 17 18:17:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3151DE90D48 for ; Sun, 17 Dec 2017 18:17:25 +0000 (UTC) (envelope-from dmytro@posteo.net) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.posteo.de", Issuer "StartCom Class 3 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ED3CD78DF6 for ; Sun, 17 Dec 2017 18:17:23 +0000 (UTC) (envelope-from dmytro@posteo.net) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id AF50C20ED1 for ; Sun, 17 Dec 2017 19:17:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1513534634; bh=Ex5W2JBb6OL1f9GoQw5ShqhUZ9eZX20Bn46gJh/tUuQ=; h=Date:From:To:Subject:From; b=HxBAfxQzr0y1Tw1p1dkednqBX9QIlP6MvYjnJuJJ1feATXFEomK4dxiHaBJEUft5s qj2JaACjgk4TqzHFCxCGnRx/B+c28n0VH3B/EJUVHZVgfY47xfYPg8LZc31oA6vwh9 2oigE5f7ynnUjhyxSwXrp34X4l5JObtO4JcHROxnAXrB/met/EdU/Q62IxY89JtjSU 5UVGuSmPwtIdUGx5XV+hoi6TTrU8qA7EsOXE1SSNh3qPmRAbPMRo/RXJzf6rVIx9Y2 xsZWBf5MqVShLhTwFi8WObXyNhNcQ/GQX6cDwEqBOWYh2Naij+xEM0xE8BWCnYFaFy 5Ju2IED2ehPDw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3z0C7F6l7Wz9rxN for ; Sun, 17 Dec 2017 19:17:13 +0100 (CET) Date: Sun, 17 Dec 2017 20:17:12 +0200 From: Dmytro Bilokha To: freebsd-ports@freebsd.org Subject: www/payara port update looking for committer Message-ID: <20171217181712.GA3399@wstan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.7.2 (2016-11-26) 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: Sun, 17 Dec 2017 18:17:25 -0000 Hello! May some kind committer take a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224405 It is a diff to update the www/payara port. Thanks. -- Dmytro Bilokha dmytro@posteo.net +38-050-607-41-43 From owner-freebsd-ports@freebsd.org Sun Dec 17 18:18:34 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9BF2E90DF9 for ; Sun, 17 Dec 2017 18:18:34 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DC3878EB0; Sun, 17 Dec 2017 18:18:34 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa11.server.lan (via HTTP); Sun, 17 Dec 2017 19:18:23 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: "blubee blubeeme" Cc: "Stefan Esser" , Yuri , "Freddie Cash" , "FreeBSD Ports" Subject: Re: OSS Audio Content-Type: text/plain; charset=UTF-8 Date: Sun, 17 Dec 2017 19:18:23 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: <784ef8bf-c9ab-80a0-dae2-b1a0445ce9bf@freebsd.org> X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:FOuWkQ14EhCQ8UvnjA624Q/vzAAM+YfUiF4fyUq6cny WMYyprhpUifM8lI0qVHvsSQFGUuwjbE/e+Jak0yJZQLwLR11sE XW93VP7313lVGrJ4MnB84cAdAT+zXq0bIxG02fjMcOK9lg/duZ YttFblnXNsYRfjvPzOPntePFyHe7KJWVWgybU7oygismbhJhy/ quIU9/sKohCP0nD4/y4tAtbIaLxUHtpwbXYKGYKt8H/gdwuixH O9UC/38eIeaWOqnSGbRxTvwd4Bdo1Z8N6MnpnqT3qY3X1mhZOS rWltBk= X-UI-Out-Filterresults: notjunk:1;V01:K0:BlaYc10FY9U=:0qNhkM8xI6AhZXIN95xTsx D3ZuOf4jFfWxjjbMyHjRAfgTnBBdWouc/SK9oBFc0bd8z7wq3A+I1RpREPJN0go4C1nl8zhRX YCiRddcxWXerkwjxIc4TwFnhyqBob1ZlSuis59WP0IDvYG8iILxFm8AadtuIWrhGgX65L+is0 UvWyKIHtpJk3KSisUqOxYGSJdJLlRK4nqa0rEOKqpUQ+xPV1dwr1DwYS9R0HGuMAmACDRHcMb 4hYa2r9yPquT9vWBIMXbrfQuW3McLygpNSBZoAEx85DI7DYyoFg4xDUIV3/RrEy46s/AjxvIm Cgi78OQeeDqNxPsRuX+Nyo7WCyUPw6wQxYHEZjdqAjICVFe448SXPEH7TpKOeR/+2bt7/cNnh qTwCecpK+m7ieBqIXbbFE9m1434whVbqHYTYrHaDfNkvvG2cc9ogUR8y6ZT6S7dKilQs51zHR BmJumct2GkftiqT3NefCLesj11cmIyTmaH/wuCxVwuGhNiX8d9knNZLtg+ERSQ+e1s5sT35CF 8MM7wdp/95sZQiz1YVU1WTzL3vcXjtQ0yVwP7jEIX3Y 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: Sun, 17 Dec 2017 18:18:34 -0000 >> Stefan Esser; Sun Dec 17 13:11:22 UTC 2017 >> Do you propose to just update the code to what 4Front provides? >> This may work for you as individual user, but the 4Front license makes >> it impossible to commit that version to FreeBSD. (That was the reason >> to stay at a reasonably licensed version, very long ago.) >> Or do you propose a clean-room implementation that in the end is fully >> compatible with 4Front OSS 4.x, but does not violate their license and >> intellectual property rights? >> You are welcome to start with such a clean-room implementation and it >> may even be accepted into FreeBSD, once you are ready (provided there >> really is no risk of legal problems in any part of the world). > blubee blubeeme; Sun Dec 17 13:57:40 UTC 2017 > This is not true. The source code is distributed under different license > based on the OS. > Look at audio/oss src build process. > If the code is compiled on Linux it has some Linux type gpl license, if > it's on a *BSD it has BSD license, there's also license that suits other > platforms as well. > There were some closed sourced parts because Hannu was trying different > license models to pay the bills but instead of supporting him, everyone > forked his code and left so he went on to do something else. http://developer.opensound.com/opensource_oss/licensing.html It says most of it is available under a FreeBSD license, but there are parts of it, that are closed sourced. I'm not sure if any of the closed sourced code is in that download. If any closed sourced or GPL code is it in, it would have to be forked it to github, sourceforge or other repository, to include only FreeBSD licensed code. > blubee blubeeme; Sun Dec 17 13:57:40 UTC 2017 > I propose properly implementing 4Font OSS 4.x in the FreeBSD kernel, > properly using the API as documented on 4Front website. > Have 4Front OSS the default audio system in FreeBSD > Having proper Audio programming guide in the FreeBSD handbook > ditch sndio and all that other stuff and move forward with a clean start > and proper documentation for new audio programs. If 4Font OSS 4.x comes along, sndio's and portaudio's servers should be stripped down, to work on top of, and not duplicate OSS's server implementation, so the API of many programs that already use it, readily will. I also wish there were a FreeBSD patch for ALSA and other Linuxism API's to just connect directly to OSS or Sndio's server. Canberra's (computer sounds output) API especially needs to drop directly to OSS's sound server. The reason parts of sndio and portaudio should stay available, is that they've done a lot of work this year to fix most ports to work with sndio, and keeping compatibility with these two, will make porting easier from other BSDs, including GNU programs that already got ported to other BSDs. From owner-freebsd-ports@freebsd.org Sun Dec 17 19:04:36 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8340E9253B for ; Sun, 17 Dec 2017 19:04:36 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B2E1B7A794 for ; Sun, 17 Dec 2017 19:04:36 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by mailman.ysv.freebsd.org (Postfix) id B226DE9253A; Sun, 17 Dec 2017 19:04:36 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1C3FE92539 for ; Sun, 17 Dec 2017 19:04:36 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA1C67A793 for ; Sun, 17 Dec 2017 19:04:35 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 89a25170 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 17 Dec 2017 12:04:33 -0700 (MST) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Option vs. flavor? From: Adam Weinberger In-Reply-To: <2e1a60e4-6800-49a9-aaca-73a1a856c7a3@rawbw.com> Date: Sun, 17 Dec 2017 12:04:22 -0700 Cc: "ports@freebsd.org" Content-Transfer-Encoding: 7bit Message-Id: <0D663E61-19C0-4855-9A00-4C3AE27CDEEE@adamw.org> References: <0CE3611A-F100-4443-93B4-68A0A83F162B@adamw.org> <2e1a60e4-6800-49a9-aaca-73a1a856c7a3@rawbw.com> To: Yuri X-Mailer: Apple Mail (2.3445.5.20) 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: Sun, 17 Dec 2017 19:04:36 -0000 > On 17 Dec, 2017, at 11:10, Yuri wrote: > > On 12/17/17 06:32, Adam Weinberger wrote: >> Ah okay. Then I'd say, make a slave port that just >> fetches/extracts/installs the data files, and an option in the Geant4 >> master port that defaults to off. Set the slave port to NO_PACKAGE. > > Ok, I will do it this way. > > >> I wouldn't go the flavor route, because the purpose of flavors is to >> generate multiple packages. The 4.5GB data files shouldn't have a >> package, so options is the way to go. > > > I was actually wondering, why the use of flavors is such a bad idea in > this case? I know that flavors weren't originally intended for this, but > it might seem that they lend themselves very well to such use. > > One can have a virtual flavor, say @withHugeData. It doesn't get built by > default because it is virtual. At the same time, somebody who needs data > can always run 'poudriere .... thepkg@withHudeData' and build the needed > flavor of the package. > > What would be the downside of such use, besides it being the use of a > completely different kind than anticipated? Hi Yuri, My reasoning is that options exist to let users configure a port to have one feature or another. The key point there is that users can choose the configuration themselves. Flavors exist to make it easier to produce multiple packages without making slave ports. The key point here is producing multiple packages. Presumably you'd set NO_PACKAGE on the massive data, so producing multiple packages isn't a benefit. If you're not looking for the builders to produce multiple packages, flavors just isn't the optimal paradigm. A NO_BUILD slave port is really easy for people who are normally pkg-only. There's no dependencies, just fetch/extract/install. I'm assuming that Geant4 has a number of dependencies, and it's a much bigger deal for people used to pkg install'ing everything. The other thing you might consider is a simple shell script to fetch and extract the data files into place. net/GeoIP does it like that (though not for size reasons). # Adam -- Adam Weinberger adamw@adamw.org http://www.adamw.org From owner-freebsd-ports@freebsd.org Sun Dec 17 23:30:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9E41E997F3 for ; Sun, 17 Dec 2017 23:30:54 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from viclamta08p.bpe.bigpond.com (viclamta08p.bpe.bigpond.com [203.38.21.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 889972C27 for ; Sun, 17 Dec 2017 23:30:52 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from smtp.telstra.com ([10.10.26.4]) by viclafep01p-svc.bpe.nexus.telstra.com.au with ESMTP id <20171217231752.HZUZ20482.viclafep01p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com> for ; Mon, 18 Dec 2017 10:17:52 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtuddrfeekgddujeefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuuffpveftpgfvgffnuffvtfetnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfgggtgesthdttddttdervdenucfhrhhomhepffgrvhgvucfjohhrshhfrghllhcuoegurghvvgeshhhorhhsfhgrlhhlrdhorhhgqeenucfkphepuddutddrudeguddrudelfedrvdeffeenucfrrghrrghmpehhvghloheprghnvghurhhinhdrhhhorhhsfhgrlhhlrdhorhhgpdhinhgvthepuddutddrudeguddrudelfedrvdeffedpmhgrihhlfhhrohhmpeeouggrvhgvsehhohhrshhfrghllhdrohhr X-RG-VS-CLASS: clean Received: from aneurin.horsfall.org (110.141.193.233) by smtp.telstra.com (9.0.019.22-1) id 5A1F320A03D23923 for freebsd-ports@freebsd.org; Mon, 18 Dec 2017 10:17:52 +1100 Received: from aneurin.horsfall.org (localhost [127.0.0.1]) by aneurin.horsfall.org (8.15.2/8.15.2) with ESMTP id vBHNHq2p007544 for ; Mon, 18 Dec 2017 10:17:52 +1100 (EST) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by aneurin.horsfall.org (8.15.2/8.15.2/Submit) with ESMTP id vBHNHpo9007541 for ; Mon, 18 Dec 2017 10:17:52 +1100 (EST) (envelope-from dave@horsfall.org) X-Authentication-Warning: aneurin.horsfall.org: dave owned process doing -bs Date: Mon, 18 Dec 2017 10:17:51 +1100 (EST) From: Dave Horsfall To: FreeBSD Ports Subject: Procmail got updated! Message-ID: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) X-GPG-Public-Key: http://www.horsfall.org/gpgkey.pub X-GPG-Fingerprint: 05B4 FFBC 0218 B438 66E0 587B EF46 7357 EF5E F58B X-Home-Page: http://www.horsfall.org/ X-Witty-Saying: "chmod 666 the_mode_of_the_beast" MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII 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: Sun, 17 Dec 2017 23:30:54 -0000 Doing my regular update, and... Upgrading procmail from 3.22_9 to 3.22_10... Good grief; who's the masochist who volunteered to support this obscure insecure and hitherto-unsupported scripting language? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." From owner-freebsd-ports@freebsd.org Mon Dec 18 03:38:04 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16E1FE9F794 for ; Mon, 18 Dec 2017 03:38:04 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD53368D28 for ; Mon, 18 Dec 2017 03:38:03 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x232.google.com with SMTP id x28so26794609ita.0 for ; Sun, 17 Dec 2017 19:38:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4jYEa/TO1l6A9wdFKnf2tS55B7RmM+dg0FolvIgQUTg=; b=mnz6X+EX0YnWfqIDZKoQLb/p24Xq9fzlH8EGLDlIXUgWJZ42XcHB3xkdcZ5vJdog2/ vFbDv1BiW8IJIeBmCj0Zm7eHRHiE60C565EVj1O3fBlM7KVP6Iz3u+vteZ6/xNFecez9 XYSmOeE5lxBwwrvMG7yK2V9I1qCYA868ZyeZrScN+xhVs3xUB0UYRQfQA4kYiP/aIClw H0FvAiLBVR19c6HEn6GIVlN6KqDW0O0Q5h4QjyLkHQh8ew+k+FMfM4e3jv8OfGxir7BJ LMVOfzdKhfLNiFkCo/Oq32UakbmrBOe8Y//1wXvyp9V6sSVT37n6yPdLYeq6Lp423Jyh JqpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4jYEa/TO1l6A9wdFKnf2tS55B7RmM+dg0FolvIgQUTg=; b=M7vCUXcEQSheLwyWP+hyjpjt9l6XJ8cjjPZoJHKU1THnOnslSfwD64mgH5v9z1M8v4 Y4794egWUEqKannECQHWfoTj16untYqL7Q0zD7Bf57V24KuoKvm10fw76LpRqvO8IoGb dXPzQNLkUWhufUzVjtHcpKlceynEfKlJ+JaP5UIOvzIz/k4RNEmV8nx/ULa8sd+vGl9E ZjsgZqRL9CKQB4ai9KBzYVjhj9iJ4Ih9zEbDexQK7NxE9WCx13ffEfk3es7jL4G5hnM3 zqUrflW91cg1HPpZovi8bCgIT+cBgP7eicodZLJ6LLrtOoyiOeUtHN/YxJpoKGvaroKQ F+Jg== X-Gm-Message-State: AKGB3mJyXfGqFEeuMBwDM8JODLf/v1/GvlB1zeqww26QzmnO8vSV/IUB 5uqYhgipVQP+G0tMyofWv62XaROjDaEAsU10idI= X-Google-Smtp-Source: ACJfBovUWwtv/BQFzKfb5E/GOPOyO67wsJfNE+BrWQ19BbVuelPhP4Ko/etMRk1xQJP2VhyP+LVEaIg18YwH0LK3/Ew= X-Received: by 10.36.151.198 with SMTP id k189mr19131354ite.100.1513568283019; Sun, 17 Dec 2017 19:38:03 -0800 (PST) MIME-Version: 1.0 References: <784ef8bf-c9ab-80a0-dae2-b1a0445ce9bf@freebsd.org> In-Reply-To: From: blubee blubeeme Date: Mon, 18 Dec 2017 03:37:52 +0000 Message-ID: Subject: Re: OSS Audio To: Sid Cc: Freddie Cash , FreeBSD Ports , Yuri Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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, 18 Dec 2017 03:38:04 -0000 On Mon, Dec 18, 2017, 02:18 Sid wrote: > >> Stefan Esser; Sun Dec 17 13:11:22 UTC 2017 > >> Do you propose to just update the code to what 4Front provides? > > >> This may work for you as individual user, but the 4Front license makes > >> it impossible to commit that version to FreeBSD. (That was the reason > >> to stay at a reasonably licensed version, very long ago.) > > >> Or do you propose a clean-room implementation that in the end is fully > >> compatible with 4Front OSS 4.x, but does not violate their license and > >> intellectual property rights? > > >> You are welcome to start with such a clean-room implementation and it > >> may even be accepted into FreeBSD, once you are ready (provided there > >> really is no risk of legal problems in any part of the world). > > > blubee blubeeme; Sun Dec 17 13:57:40 UTC 2017 > > This is not true. The source code is distributed under different license > > based on the OS. > > Look at audio/oss src build process. > > > If the code is compiled on Linux it has some Linux type gpl license, if > > it's on a *BSD it has BSD license, there's also license that suits other > > platforms as well. > > > There were some closed sourced parts because Hannu was trying different > > license models to pay the bills but instead of supporting him, everyone > > forked his code and left so he went on to do something else. > > http://developer.opensound.com/opensource_oss/licensing.html > It says most of it is available under a FreeBSD license, but there are > parts of it, that are closed sourced. > I'm not sure if any of the closed sourced code is in that download. > If any closed sourced or GPL code is it in, it would have to be forked it > to github, sourceforge or other repository, to include only FreeBSD > licensed code. > If you go grab the source code and just do the build steps you'll see that the license is applied at build time based on the underlying OS. > > > blubee blubeeme; Sun Dec 17 13:57:40 UTC 2017 > > I propose properly implementing 4Font OSS 4.x in the FreeBSD kernel, > > properly using the API as documented on 4Front website. > > Have 4Front OSS the default audio system in FreeBSD > > > Having proper Audio programming guide in the FreeBSD handbook > > ditch sndio and all that other stuff and move forward with a clean start > > and proper documentation for new audio programs. > > If 4Font OSS 4.x comes along, sndio's and portaudio's servers should be > stripped down, to work on top of, and not duplicate OSS's server > implementation, so the API of many programs that already use it, readily > will. I also wish there were a FreeBSD patch for ALSA and other Linuxism > API's to just connect directly to OSS or Sndio's server. Canberra's > (computer sounds output) API especially needs to drop directly to OSS's > sound server. The reason parts of sndio and portaudio should stay > available, is that they've done a lot of work this year to fix most ports > to work with sndio, and keeping compatibility with these two, will make > porting easier from other BSDs, including GNU programs that already got > ported to other BSDs. > This should be possible since most of this code is trying to do stuff that 4Front OSS does already. Please remember that it was Hannu who wrote the first sound driver for Linux and it's his work that most open source audio drivers is based on. He implemented a midi sequencer before the official midi 1.0 spec was finalized. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Mon Dec 18 12:32:38 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4AF8EE85FD0 for ; Mon, 18 Dec 2017 12:32:38 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 366DE784E9 for ; Mon, 18 Dec 2017 12:32:38 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 358BEE85FCE; Mon, 18 Dec 2017 12:32:38 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35443E85FCD for ; Mon, 18 Dec 2017 12:32:38 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2752E784E8 for ; Mon, 18 Dec 2017 12:32:38 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id vBICWcK2060153 for ; Mon, 18 Dec 2017 12:32:38 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id vBICWc88060147; Mon, 18 Dec 2017 12:32:38 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201712181232.vBICWc88060147@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Mon, 18 Dec 2017 12:32:38 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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, 18 Dec 2017 12:32:38 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ audio/xmms-faad | 2.8.6 | 2.8.8 ------------------------------------------------+-----------------+------------ sysutils/fusefs-s3fs | 1.78 | v1.83 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Mon Dec 18 15:26:51 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CB82E93323 for ; Mon, 18 Dec 2017 15:26:51 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B23FF7F7C3 for ; Mon, 18 Dec 2017 15:26:50 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Mon, 18 Dec 2017 16:26:35 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1513610808; bh=d6eBcDxh+0nAJeLSHnVRWr1dk6roOB1MaXsXAR4jjXQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=erWvbEOhkeUdQLt+EP90tmZ59xXrFfn9GVwKEw62FrIMapyFWULHvIUmM0Z6S617T yPCzgt5pKA8ZJoTn9VTiJgXFhZOpDMEQ1dXNkjQ53Zh7p8dFxmDEvLFwM/txTVeGDh DL1Dbzf7gyJiHr5C1ANLQ8E/tJFJEgNPQnfhEaX7lGAI7zBfxIP4aJCgXQsvq47Unn jzQ2QVbN5OFuifwhubpTpo3gilw7eM9ecd/YdymS4gUwMUWOfL/CvZoyV4N5Keyc6B GzIfxReOM44muXfHriwKaOHg3oqXr6lm0mp1OEEJ82ycXG2GKM1bdwQLCR33xHzg+W 7+NTn/aNmDwjQ== Message-ID: <20171218162635.Horde.nOMBnXNRYOuu4Qjj1GnSQBw@webmail.leidinger.net> From: Alexander Leidinger To: Sid Cc: blubee blubeeme , Yuri , Freddie Cash , FreeBSD Ports Subject: Re: OSS Audio References: <784ef8bf-c9ab-80a0-dae2-b1a0445ce9bf@freebsd.org> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_FmHqgz1SdBuLwmvfGBm7YXn"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 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, 18 Dec 2017 15:26:51 -0000 This message is in MIME format and has been PGP signed. --=_FmHqgz1SdBuLwmvfGBm7YXn Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Sid (from Sun, 17 Dec 2017 19:18:23 +0100): >> Having proper Audio programming guide in the FreeBSD handbook >> ditch sndio and all that other stuff and move forward with a clean start >> and proper documentation for new audio programs. > > If 4Font OSS 4.x comes along, sndio's and portaudio's servers should The FreeBSD sound system already implements the OSSv4 API since about=20=20 FreeBSD=208. > be stripped down, to work on top of, and not duplicate OSS's server=20=20 >=20implementation, so the API of many programs that already use it, If they wouldn't use the OSS API on FreeBSD, they wouldn't be able to=20=20 play=20and sound. If they use it to the full extend what is possible and=20= =20 makes=20sense, I don't know. Anyone is free to work with the developers=20= =20 of=20those servers to improve the FreeBSD parts in those programs. > readily will. I also wish there were a FreeBSD patch for ALSA and=20=20 >=20other Linuxism API's to just connect directly to OSS or Sndio's Isn't this what the port audio/alsa-lib is about? > server. Canberra's (computer sounds output) API especially needs to Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_FmHqgz1SdBuLwmvfGBm7YXn Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaN94rAAoJEKrxQhqFIICEzF8P/3fvqHpXBshRho7LQ17RAfYH loW9izQkb4rqNhTUxjk3Wv577jvJuDcnXymYd4hSKDR+OP1DOJ3ypeKtw3Du0dJ1 iogJmhKCxzCtapVQri0OFXzrvZu2t4OXydV1sSCAFJ6WOi2KdZ3qdW1PVZIMXlWI udvKFVu3tUbGK/p6CHY+9zLDWDo2c+lNsGQd4YfU+YNPaAyQMKRjqpb7VGTXNNgo OUwwRGP2ny395t7JxNdaIfvi44MZA0SjxrSer78wLuWV9GA2V1T/NNR5cNcPqJCd QM6k/4LpldBCxFpn895z1JVLfpD1uA7f8aNlPlYycnDE6maU7p62UeMCscfusif/ /08B1bd7koO22Mug5AWQMqr8UGASpnNnQDqk80oXGLp4ErdEg//g9+X8djYKrCju nRS5r/j2oSmrmsdB/fbwRHVPVFLvMBDRZOxOszwKI4IYj+ocT/1/KP7AGc3V9b9+ zJIXQrxFOi7c8f12PTxjJmAAQSqsy6p4LZyMCG+iOf8xRJMfYsVaZA5VnLpQHlz3 nBiCkXCAA1u1c7u+tJ3AmfJtqI0GoydLxGOSE00WmwECimMd5bz3Xf7+SUeOD130 qSiTGe+Yybk1HKelJ6OVvgGQP27M81Nh5VRSsOgzpF8HE/qoOjzNADBkQxz8BcOY i4pjWrETkifiX3+naIyb =bTK+ -----END PGP SIGNATURE----- --=_FmHqgz1SdBuLwmvfGBm7YXn-- From owner-freebsd-ports@freebsd.org Mon Dec 18 16:11:56 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47E24E96D49 for ; Mon, 18 Dec 2017 16:11:56 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E112216F3 for ; Mon, 18 Dec 2017 16:11:54 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Mon, 18 Dec 2017 17:11:20 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1513613505; bh=jDu6lG9N2ms3h+a3N3FCalDow7FASSqC8fqY4nj6+pI=; h=Date:From:To:Subject:References:In-Reply-To; b=m2vA5jO0vB3hbl8du4DLwgnm0NXRumvTj+07R+MsQPM671Pi/jke94qjUBdw1O0lq 0Ms6f/OIX1Pu4iup5WIRZP2+kg+8bH6SicMRyTyA9EaqUuZw8eqJjCVPTT9d0wkiza E9ZMh7IYR+nAvX0mxhAsl8IGJOy0F6tCPsybPxYtaH6JpP9JgD46Dzwabs//0DrHEi +9GTamc70NwuyIrOEEiDhb2cB7Ot586+5EqHMavCDo/8kxA8WATVIQL9eOqZtTU/lF pqLqFeLog1VX2EWvTbSg7RCmGGJ2Fv/5ZJKkxTZMMyjWX6XX076EEltYz6HSsQCUdG 2tgeUcGsBDK7Q== Message-ID: <20171218171120.Horde.s5OngVFuRoftIluNHRvGOV6@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-ports@freebsd.org Subject: Re: OSS Audio References: In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_g0ARV2vhdwQ-vwyuWy6-4GV"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 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, 18 Dec 2017 16:11:56 -0000 This message is in MIME format and has been PGP signed. --=_g0ARV2vhdwQ-vwyuWy6-4GV Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Sid (from Sat, 16 Dec 2017 23:53:17 +0100): > I've had a few misconceptions. > > Bluebee Blubeeme said, 4Front has a modern OSS implementation that=20=20 >=20is under a FreeBSD license. > > The model of Sound on FreeBSD is, three layers: > 1. The API, where programs use libraries (of respective sound=20=20 >=20architecture) to access the sound server. > 2. The sound server: OSS, Sndio, Portaudio, JACK, ALSA, native, etc > 3. FreeBSD's base is always OSS (OpenBSD's driver is sndio); sound=20=20 >=20servers connect to and use this. It's a little bit different. From application to hardware it is like: 5) application 4) maybe some infrastructure layer (jack, portaudio) 3) the API (for linux: ALSA libs, for FreeBSD: opening the device=20=20 nodes=20and issues ioctls =3D the OSS API) 2) the kernel code 1) the hardware So FreeBSD is a target from layer 2 until layer 3. Everything above=20=20 depends=20100% on the application you are using. > The part of OSS in name, that is a mess, is the API structure, and=20=20 >=20various implementations. In FreeBSD for instance, when a program=20=20 >=20uses an OSS API, I hear that developers, need to write so many=20=20 >=20patches, because different OSS frontends are not standardized. Most FreeBSD implements the OSSv4 API. Maybe not in v4.2, but those are=20=20 extensions=20are not really that much important for this discussion. The=20= =20 important=20part is, that we support OSSv4 since about FreeBSD 8, and=20=20 that=20the main part of playing audio is not changed between 4.0 and=20=20 4.2,=20so it doesn't matter much if we talk about the FreeBSD=20=20 implementation=20of OSSv4 or the 4Front implementation of OSSv4.2. The issues which come at hand are so far either at layer 5 or 4. For=20=20 issues=20at layer 3 I have not seen any prove or procedure how to repeat=20= =20 the=20issue so far (and I'm interested to see a procedure so that we can=20= =20 repeat=20the issue(s) people talk about here). Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_g0ARV2vhdwQ-vwyuWy6-4GV Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaN+ioAAoJEKrxQhqFIICEp1IP/2HCKuuX4MMshl1i3+zpVdKG Wn5yZKvQEPhyj2wrBUGtlZdPOLnf9CeVWTg/ZuFbQlzf2hrOOp6o95H3j72shfDF NbyC+NF79YEI4BN3HMGQTyMOG50VCfHlz6dyzgOC1BULVxqJ9oheREbns5i7kt0a edMk1lON5zZ2+jPPTq9Kh2br+VhBCD3RGaJkwQ942j8jeSvRpqfBl/XlPvmMfeXm wF/B/9Ii6Og+TtwNhLq+/vxAM5WUfbh1UD3VW7JTQyOnElf7z93Af6nJu6c/Z08u 3Bbv8Om0Ig5OS57a/lkBYGVVV6WI+OyjyD2XqKCiBHI81A/vrAdtU7Cy6haHMu6g 8gF7frfutoq3H2zI+45nr/UjUcI1enuz8GkNyRDzG2zhtnbpQ6GXCSEQrWWTVPex Z2EZh7RukbFMzsUaSAJMmfkIjofkjdwNDh7lf5sPkGpKushrGs4roF8hYKUiZQVg /5QuxIx4PO5Q1NgJASr+QbFSFbBDC+JSH7RRK8kp/OwZF1hSV+88lV1joF8eIhPU 9jeyM/+dEPBBvH5M4ZVZvQbEvC/J7wXIFtng6wyA/gjUwgfEUCvTnnZeR8EJm3/N PtoxLJhjaJiklHHvF+xEXWxwFS2tAh8AOGsf+R3zrr76PNtOkNhl0uIQa5u8MYoH XkRTwtLC78XC4Tr9stsQ =od8+ -----END PGP SIGNATURE----- --=_g0ARV2vhdwQ-vwyuWy6-4GV-- From owner-freebsd-ports@freebsd.org Mon Dec 18 16:28:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47AD6E984E5 for ; Mon, 18 Dec 2017 16:28:25 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0AAE52788 for ; Mon, 18 Dec 2017 16:28:25 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id l10so10388362ioc.3 for ; Mon, 18 Dec 2017 08:28:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=78nFcM+uI/MpZaLCEYVSP5sIpDkH+kTyx21BdVc+CpE=; b=M/6wc4JYTOnyJiang4cCal7proT/02/bJ2V0ObVsJNq9kNDAtiyf4gqFqDwPKy/Js9 ghystq4ZYiHlKNlorJSHUFAnBWLcKhOjPdEtLdO6mDtRKPRUXX6Lq9ZX63ggI+8Ujtu7 3g00uvzAjnRhwrnLGlZxOJaNyr/AhGK6EBWEuaOylpVNwuUC3PlW9AzbYo1wcGvJV1xO CXe914dxUOea313QtKS5oM/h1H6qNyS7k5uAflLkqq/QboayfhneDcM7msfb8ORrKAHx /QmzkEE8guaM5ypHAkPP6Fvaqz7WeecoeyenIPNEvfxemAS+uqGyuuOtiAREpTSghqbb H7tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=78nFcM+uI/MpZaLCEYVSP5sIpDkH+kTyx21BdVc+CpE=; b=faOXVvjnidaBwF4pEvQw571FP+/BDdyweol5UJl4wUaAR34qNv7zicHEuoPK+DzF3G yvQwn1+JnFP4WVde65kXYe92XdS6I8MMiuoTiFLLP2B1NJ1O+r1mezyArfNe7gBDSYxr S2tiIdFl1ZndRsLrG7ZmiPZVydCi1v74PRQplSdpEuisw6ci8jqfiwxCDT8NhUUIyS5X RC1j74bK/ZvE2ifuZrqGlTLndWTRPgn3xQ2BvM28qVA8X0y4xAvix4UJQOJyDDFaDfIz hlsu9glWpuTpcRLGGFpB/8NJzBkwWufpk5QDPsP5yvI53lWvqSySGdPjk7ESsEbRfWBM nYpQ== X-Gm-Message-State: AKGB3mIVmVF9z2i1BRyp+YqeSNg1Tl7ZqlEursuz4GRQIgDYUiOx3Axs Gbl4VX7kKpHbr5rYTbgud0Fux1bVkR30pIuCzO0= X-Google-Smtp-Source: ACJfBovsSp9G4wmlHMrVKxlhBouN5F5YjWaaQ24Dqm6LD+Ud4jCwOdFYHKn38mP2c11pIIx64o88zcr1ssY6GS4vrPU= X-Received: by 10.107.162.131 with SMTP id l125mr396591ioe.153.1513614504159; Mon, 18 Dec 2017 08:28:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Mon, 18 Dec 2017 08:28:23 -0800 (PST) In-Reply-To: <20171218171120.Horde.s5OngVFuRoftIluNHRvGOV6@webmail.leidinger.net> References: <20171218171120.Horde.s5OngVFuRoftIluNHRvGOV6@webmail.leidinger.net> From: blubee blubeeme Date: Tue, 19 Dec 2017 00:28:23 +0800 Message-ID: Subject: Re: OSS Audio To: Alexander Leidinger Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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, 18 Dec 2017 16:28:25 -0000 On Tue, Dec 19, 2017 at 12:11 AM, Alexander Leidinger < Alexander@leidinger.net> wrote: > > Quoting Sid (from Sat, 16 Dec 2017 23:53:17 +0100): > > I've had a few misconceptions. >> >> Bluebee Blubeeme said, 4Front has a modern OSS implementation that is >> under a FreeBSD license. >> >> The model of Sound on FreeBSD is, three layers: >> 1. The API, where programs use libraries (of respective sound >> architecture) to access the sound server. >> 2. The sound server: OSS, Sndio, Portaudio, JACK, ALSA, native, etc >> 3. FreeBSD's base is always OSS (OpenBSD's driver is sndio); sound >> servers connect to and use this. >> > > It's a little bit different. > > From application to hardware it is like: > 5) application > 4) maybe some infrastructure layer (jack, portaudio) > 3) the API (for linux: ALSA libs, for FreeBSD: opening the device nodes > and issues ioctls = the OSS API) > 2) the kernel code > 1) the hardware > > So FreeBSD is a target from layer 2 until layer 3. Everything above > depends 100% on the application you are using. > > The part of OSS in name, that is a mess, is the API structure, and various >> implementations. In FreeBSD for instance, when a program uses an OSS API, I >> hear that developers, need to write so many patches, because different OSS >> frontends are not standardized. Most >> > > FreeBSD implements the OSSv4 API. Maybe not in v4.2, but those are > extensions are not really that much important for this discussion. The > important part is, that we support OSSv4 since about FreeBSD 8, and that > the main part of playing audio is not changed between 4.0 and 4.2, so it > doesn't matter much if we talk about the FreeBSD implementation of OSSv4 or > the 4Front implementation of OSSv4.2. > > The issues which come at hand are so far either at layer 5 or 4. For > issues at layer 3 I have not seen any prove or procedure how to repeat the > issue so far (and I'm interested to see a procedure so that we can repeat > the issue(s) people talk about here). > > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > there's the alsa-lib from audio/alsa-lib there's https://sourceforge.net/p/opensound/git/ci/master/tree/lib/libsalsa/ from oss that wraps alsa code, would there be issues with any of that in the kernel? From owner-freebsd-ports@freebsd.org Mon Dec 18 18:09:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2B49EA0C58 for ; Mon, 18 Dec 2017 18:09:49 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9768A67B86; Mon, 18 Dec 2017 18:09:48 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.139.137]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LmKag-1f0suG0eSQ-00ZtA4; Mon, 18 Dec 2017 19:09:46 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id D6CE923D416; Mon, 18 Dec 2017 19:09:30 +0100 (CET) Subject: Re: Procmail got updated! To: freebsd-ports@freebsd.org, Sunpoet Po-Chuan Hsieh References: From: Matthias Andree Message-ID: Date: Mon, 18 Dec 2017 19:09:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:W+So+CRdu1iP+gk0rFiGtJz7ooBVM3pyCoh9XO1Baof+Cmc76dq t3IcNhGOG9/TqPjC23K0zF2azpcyV88KZVZHAOt8goGHLsjy9B2JAlteQlZSZwF/DYtl8/F BoxtCYPHMUUym5RY9ElsqGmdNp2SlJ52AlTz+xIgtFqOqM+51RZNZb0WI+MgIFtpmg0oXPI 6WZ07ezGBffLla2s0qbPw== X-UI-Out-Filterresults: notjunk:1;V01:K0:L5+W4zsw3l8=:bH4YVTrkZQlbRoy5oEB/6c /XwYT78MsxbyzaislBfVoicCYc/el6sdEHDEciGZv6BqbnIE4+1C8EhUMyXTFddq+g01oUcQ/ CDsH9TtMx/R5W8xHRMdtT6asFuBHXn2ckUrgw3mHYPdIIMDs6s1f6bte2fhzCio1zV45/ok5y MzUCXg3ZXj0tt20iAJhO0hsIR6ZPryVRQkfSu9ItJ4zU9vGDkDvWV7rmvuN8kCROJO15ndE4Q xgn4ijKmZk+tJ+1bPA4NMQHz5gEsjKRJYGYkF8Q3oyun3Z7hAHu5mpKhB1QwMrTm+rES+pFzk n0Dny5LVCMCl0MxXaIHnOwwV+pPMizjUQQHvhQtJl9BgguX3Pgw3PAe8TKw3fZBEDw7Z5/fJD C+vOEknG1zdKJ+JQ7IlSmUvTK287u+p5uM1MCfM8QdkvPKhMRI4jzdvyVlKydHR2eo4FLNubF ZE62Q15fxBiWpah45h8mlJRbWePRu3d2WrT7AqLYbPxBaCf9HqnaGLCtgdwsPb+21bPtOs6rN qz1oaMClMSXxbUCp3WrCLUXV3XEPpUA6akYbt8xlTPa9D3mBv30HnzDUjvuQZ51eFSdeGPY5I brPrpqIQg3cFpdGA3snsF7oKAyLG6X7b0Skh9NxB95Kzp2uzyp98xJ7hAesSMdNKxjJWU+OM0 iOm0hIERVwuShN6P9ZAjXwTYvrH+RvXjOeRnNf3Pe7ciMB4RPamTkmTz17ptnDyFUwslQ+1st Mht6JNqeF68FCq5mrfEWfThSBuVNevwx1EZrtDAVRxz9wPAq9N/DmZNbPlx6VuhGBGKYymOcI qPuWaWMKb6xNJTsm0JL9AC+eG0e1Wgs8rAkeYEK++NdIqGyHfXk40Em5ssbnXnsJQWRh5Fx 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, 18 Dec 2017 18:09:49 -0000 Am 18.12.2017 um 00:17 schrieb Dave Horsfall: > Doing my regular update, and... > > =C2=A0=C2=A0=C2=A0 Upgrading procmail from 3.22_9 to 3.22_10... > > Good grief; who's the masochist who volunteered to support this > obscure insecure and hitherto-unsupported scripting language? > https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D455800 I'd agree we should pull the plug on the package. We'll be in for the usual "but it works for me" screaming of the irresponsible people who don't care (and most of them won't know that they need to write the exception/error handling themselves in their .procmailrc recipes). Sunpoet, can we mark the port as deprecated given that even the upstream once said it should best be abolished? I can't find the reference now, the procmail.org website displays "Site hosting in transit, information will be back up shortly." From owner-freebsd-ports@freebsd.org Mon Dec 18 19:52:41 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AB4EE81F17 for ; Mon, 18 Dec 2017 19:52:41 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0473F6C0A4 for ; Mon, 18 Dec 2017 19:52:41 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: by mail-io0-x231.google.com with SMTP id e204so11070494iof.12 for ; Mon, 18 Dec 2017 11:52:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/dZYgkp1VyrCUq01g4OdFhztdBByONVpRyan+KID9xg=; b=b/j/gz6ZRzhMSmDYWQaSw6SKaaKPUi1ZlO26eu+zAY11gNDbnAtb7hB7YJFYEi5Nx9 2yfB1Ykw+Q+HWOx1EIMQXnofB3/h/jigXVfV6QROiyUlJbD3Afsh9bmRMnDKBlyvCmGl dekUikyeyZl+eqwZo7npHKOOClSoIaB0uLiB8nbMD9rhhse7l8ycRncIVqECjmG8XPla U42zItWhA1PgMkGd98RvdwujXmyshyF5KSuxGiZlDr0IDVlXE6zZVidfT7ZXhI0/Ljd+ owNA8B+XkZox6WDX9nyLk5nn7zOlSaqEw9jhIobo9ArsyF0J/H/qDPDmZj4oZNKrrxy1 4lAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/dZYgkp1VyrCUq01g4OdFhztdBByONVpRyan+KID9xg=; b=cIgb5SUkbn6sY1D5eqZu3tiN2PLvjTihdJYefgpplxC304xFJTl7EUd+Q2Mpqo1vNg xLzRO3zs5jST7yePyxWWrZAEwMLhLCSMSzjQ+LkDXC8ZO/Q32MbtfTM9/5cf4kXceZqH yVFZA3xch842Hud1TaV3SXe+JjmlAQYayAWx0WwoIlJEQFk9cBHnlc+eW4rZvoszKgcj E2mqOxqeSNr1U62Q3XIEjAdWOtd4cQCp6ME/oL1JdakbXikFYq/9Nu0mtx+OQEU3D/8m MWocKxGRFyC+pALlV9ZF2kCMyQD8OaYuprTVHsC9wpFihEsMNMawo7tZ98NOIMbplwkZ Mrlw== X-Gm-Message-State: AKGB3mIy4SsXI72qbUeNIZIFISuFFivJqO4M/L2IUCHiwPAEZOBo4O1L 9w/Wxn8KG8We+3woaQm3OCWW+IDdRe0RGElIUAZiVw== X-Google-Smtp-Source: ACJfBovpW24IXr/WxnymE/3of5n1RqqHJaRFNsI3K5Pu696JpMo9+T7yhuKSViPqgoRjtNXJrqcKpEGpM80lRXWnH4c= X-Received: by 10.107.83.19 with SMTP id h19mr1097709iob.208.1513626760012; Mon, 18 Dec 2017 11:52:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.9.199 with HTTP; Mon, 18 Dec 2017 11:52:39 -0800 (PST) From: Kurt Buff Date: Mon, 18 Dec 2017 11:52:39 -0800 Message-ID: Subject: A small problem after switching from portmaster to synth To: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 18 Dec 2017 19:52:41 -0000 I'm seeing a lot of this in the daily security email after switching: Checking for packages with mismatched checksums: db5-5.3.28_6: /usr/local/share/doc/db5/api_reference/C/BDB-C_APIReference.pdf On one of my machines, it goes on for hundreds of lines, mostly for postgresql. I am also seeing a lot of this on a couple of my machines: Checking negative group permissions: find: /usr/ports/devel/pijul/Makefile: No such file or directory I've read through the man page for synth, and I've done a fair amount of STFW, but I don't see a way to fix either of these. Can someone suggest a reference, or a plan of action to fix these? Thanks, Kurt From owner-freebsd-ports@freebsd.org Mon Dec 18 21:03:36 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E0EFE87953 for ; Mon, 18 Dec 2017 21:03:36 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 391ED6FB8C for ; Mon, 18 Dec 2017 21:03:36 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x229.google.com with SMTP id t196so11269519iof.0 for ; Mon, 18 Dec 2017 13:03:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OsKtI36s3w5xtix5nwuS+ZRQ5UUizkloa1uVYXHgGIM=; b=a/lZrU7x2VaCpRqNIipMnIdNf+rpOakPpd6GJ82GH2GsWAXvTxWBfpCgdS9dD2WIPZ NvcByhU3oLEsV/5LHaMTaEa5SYaKz6soa2lEprWbBt3T5cVo399zwIYCKE9SjMDO4FVi ah5ThXnNfLYP8W7N2bRPpon0+ZjFrCH0+kPYnP4cgpwCYAOZszY8a5Tj030RmClhnfU/ RWdI/85U1befZk7QQFyF7qODrmm+4KRKf0Z2Ey+hLaNxJuaE9VplteTiUts99dPK1DDn k9wXLwyxfl+YqmdIrwDxX2WqBIXSOBYrz/5IlNCXReHG9FqqlFhYw50+e+X95NY2Aock DOMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OsKtI36s3w5xtix5nwuS+ZRQ5UUizkloa1uVYXHgGIM=; b=pzQxgJ/XTVkJllmkbAiagUz3AcwIFpyWNNtqyUgtjIk6iLyxLvFN1NHIkH8PgQzKAQ Jk+HYQ+JL6MMsaj35s84WojcsGNgxYnepMqNw89MNTSoQN01Mqx83SIhH80TicXT5n0h Mskauk5RxJpSvk50at5oWi8DMFnYKAk3/zdHokDFXUyg8BLvaxOlvHsc9IXz1HIkRL2E OVgmTh642HWDikIJU9ivuZcxlonFGean7+waDyLvyEYOFoXBEXsA/XXcBqJD1IHfRs6g pPI47yF58R0nO7cW0dCmOeW8lYW7WF0MUc0XdQHEtfxt3T8sI+nWtyecPfAS8uljSDzP TRPg== X-Gm-Message-State: AKGB3mJntqJmKGuXZRXAiepO1SPqAzJyxaPM+4k1vyJDtkPVP3fxsLTF WMrV0qWOG3xhAOxcdeQfvsTgwx92/tuukEjXqws= X-Google-Smtp-Source: ACJfBourFAw9Kgs9o225FkpuF7IOTOmK1U94U2zj59dPnq4zLPp+AVbocWgRhTAa6SYC1qYXCdRNlK3vPlnrRJfioKU= X-Received: by 10.107.170.148 with SMTP id g20mr1264556ioj.175.1513631015399; Mon, 18 Dec 2017 13:03:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.180.34 with HTTP; Mon, 18 Dec 2017 13:03:34 -0800 (PST) In-Reply-To: References: From: Adam Vande More Date: Mon, 18 Dec 2017 15:03:34 -0600 Message-ID: Subject: Re: Portmaster error To: Paul Schmehl Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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, 18 Dec 2017 21:03:36 -0000 On Wed, Sep 27, 2017 at 1:04 PM, Paul Schmehl wrote: > --On September 27, 2017 at 10:41:48 AM -0500 Adam Vande More < > amvandemore@gmail.com> wrote: > > >> On Wed, Sep 27, 2017 at 10:22 AM, Paul Schmehl >> wrote: >> >> >> >> I'm running a 10.3-RELEASE instance. I ran portmaster -ad in screen >> yesterday to get all the ports up to date. Today I ran it again, to make >> sure everything was updated. >> >> When I did, I got this error: >> >> portmaster -ad >> ===>>> Gathering distinfo list for installed ports >> >> ===>>> Starting check of installed ports for available updates >> make: "/usr/ports/Mk/bsd.port.mk" line 1462: Cannot open >> /usr/ports/Mk/Uses/execinfo.mk >> make: Fatal errors encountered -- cannot continue >> ===>>> All ports are up to date >> >> Sure enough, execinfo.mk is missing. >> >> I ran portsnap fetch and update to see if that would fix it. It did not. >> >> I didn't find anything about this on the web or in /usr/ports/UDPATING. >> Is this something new? Is there something I can do to fix it other than >> wait? >> >> >> >> >> >> A portsnap extract might workaround it. >> > > I did that, but it did not resolve the problem. execinfo.mk is still > missing. Delete your entire ports tree and try again. execinfo.mk is supposed to be missing, you have something else that is not right. -- Adam From owner-freebsd-ports@freebsd.org Mon Dec 18 21:10:50 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3BC3E882A9 for ; Mon, 18 Dec 2017 21:10:50 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05F5E7009F; Mon, 18 Dec 2017 21:10:49 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vBILCVGj021951; Mon, 18 Dec 2017 13:12:37 -0800 (PST) (envelope-from portmaster@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: , "Sunpoet Po-Chuan Hsieh" In-Reply-To: From: "Chris H" Reply-To: portmaster@BSDforge.com To: "Matthias Andree" Subject: Re: Procmail got updated! Date: Mon, 18 Dec 2017 13:12:37 -0800 Message-Id: <4d451ae9bec7dc16410d348e0f48f4d9@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable 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, 18 Dec 2017 21:10:50 -0000 On Mon, 18 Dec 2017 19:09:30 +0100 "Matthias Andree" said > Am 18=2E12=2E2017 um 00:17 schrieb Dave Horsfall: > > Doing my regular update, and=2E=2E=2E > > > > =C2=A0=C2=A0=C2=A0 Upgrading procmail from 3=2E22_9 to 3=2E22_10=2E=2E=2E > > > > Good grief; who's the masochist who volunteered to support this > > obscure insecure and hitherto-unsupported scripting language? > > > https://svnweb=2Efreebsd=2Eorg/ports?view=3Drevision&revision=3D455800 >=20 > I'd agree we should pull the plug on the package=2E We'll be in for the > usual "but it works for me" screaming of the irresponsible people who > don't care (and most of them won't know that they need to write the > exception/error handling themselves in their =2Eprocmailrc recipes)=2E >=20 > Sunpoet, can we mark the port as deprecated given that even the upstream > once said it should best be abolished? I can't find the reference now, > the procmail=2Eorg website displays "Site hosting in transit, information > will be back up shortly=2E" FWIW procmail=2Eorg has shown that banner since 2015-11 (november, 2015)=2E A safe bet, that they won't be changing that anytime soon=2E :-) --Chris >=20 > _______________________________________________ > freebsd-ports@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd=2Eorg" From owner-freebsd-ports@freebsd.org Mon Dec 18 21:14:19 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7029E886FF for ; Mon, 18 Dec 2017 21:14:19 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (prod2.absolight.net [79.143.243.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 95F4C70430; Mon, 18 Dec 2017 21:14:19 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id EF384BDD2F; Mon, 18 Dec 2017 22:14:15 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id AB254BDD25; Mon, 18 Dec 2017 22:14:15 +0100 (CET) Subject: Re: Can we have multiple flavors for a port? To: Stefan Esser , Matthew Seaman , FreeBSD Ports ML Cc: FreeBSD Port-Manager References: <6ed4ac6e-a075-0fc0-a3da-371a46a9e977@FreeBSD.org> <09760447-455d-5de0-36a9-c978d84cfb72@freebsd.org> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: <6b3d11bf-cb8b-b2f8-1b61-2abdd9006220@FreeBSD.org> Date: Mon, 18 Dec 2017 22:14:03 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <09760447-455d-5de0-36a9-c978d84cfb72@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CGpuLPCMpegN5kuOQUe3sTaELnHk9MKma" 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, 18 Dec 2017 21:14:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CGpuLPCMpegN5kuOQUe3sTaELnHk9MKma Content-Type: multipart/mixed; boundary="Df1miBlrc1n8iSfChUptlaVT52Fe7gMln"; protected-headers="v1" From: Mathieu Arnold To: Stefan Esser , Matthew Seaman , FreeBSD Ports ML Cc: FreeBSD Port-Manager Message-ID: <6b3d11bf-cb8b-b2f8-1b61-2abdd9006220@FreeBSD.org> Subject: Re: Can we have multiple flavors for a port? References: <6ed4ac6e-a075-0fc0-a3da-371a46a9e977@FreeBSD.org> <09760447-455d-5de0-36a9-c978d84cfb72@freebsd.org> In-Reply-To: <09760447-455d-5de0-36a9-c978d84cfb72@freebsd.org> --Df1miBlrc1n8iSfChUptlaVT52Fe7gMln Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 16/12/2017 =C3=A0 15:24, Stefan Esser a =C3=A9crit=C2=A0: > The answer I received was very clear: There can only be 1 flavor per po= rt > and there are no plans to remove that restriction. You missed the part where I said that there would only be 2 or 3 flavors, maybe 4 in some extreme cases per port. No more. --=20 Mathieu Arnold --Df1miBlrc1n8iSfChUptlaVT52Fe7gMln-- --CGpuLPCMpegN5kuOQUe3sTaELnHk9MKma Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJaOC+lXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IgHcP/jk/PkxLsLEq+2lEEx9vkyeM Z0cRKqYuE6TWdSg+gmkyN+DCUqUOyvzmCrk4WXWfiRRKjDlgQuKVZ43Swuan5W1a ZNwdFR/lDhigtlPVx+NFRbyU62IrAomSYbzXoMWk9oZJvL+OLTNbuQWH7d1fwMnO wS4E+VuABa9kcv8cKhSuun2EOrxYldq158M75dLILX6HEmKORUOU01AnsIY9nY9E T+Ezz2o1RNYfo0Wp+QMZ2rqlCfgpeBLdquHnYHGqoGvWTfFyo2/QCZppRrjceCXl P9C8XjV6szoCOh4sgUXDn6i6cEBWHGkS3siwPbLDQurTZwpdvDu9XUtvNXBPcgyv FFHccCi/1qqOgd6oGXRJ8oivwGuLpTkzCtklQC35b/HpNd9lCBRpERUI4PPR5tv6 nzNCer69qUF1THu8rCAP4pDyXMIbAjOTmQ2EP2v5WH89sSSOAQt7hCp6jgJFUW8X dgfEPMS1R8YQooGjRhLp6Rywp8Gvbr288nh4HZV/zdNt7UCYjGfyToaCf0hHe94b NkmxYum8Pgz5ZRHXAYi5R4Y2pSIvReEL++8SFWlS4B+Ke+3zS9ZsJNRK66i+vrf0 iFHT8k+x2cyBkicJUnK4lNaKO8XXdvG/ht1samxvktTsvrM34MrFP6yHwlmbl3rn eU7I+C7iruljOqOWQ9zb =Fzp6 -----END PGP SIGNATURE----- --CGpuLPCMpegN5kuOQUe3sTaELnHk9MKma-- From owner-freebsd-ports@freebsd.org Mon Dec 18 21:40:38 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCE3FE8A247 for ; Mon, 18 Dec 2017 21:40:38 +0000 (UTC) (envelope-from kyle.dippery@uky.edu) Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0081.outbound.protection.outlook.com [104.47.33.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CB757137F for ; Mon, 18 Dec 2017 21:40:37 +0000 (UTC) (envelope-from kyle.dippery@uky.edu) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=luky.onmicrosoft.com; s=selector1-uky-edu; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Xh7kSdMO/Yp4TqUYOBcSLsZbzxwBINCjt4+fNBlB4Io=; b=T3AYvivhpouX4ZIA//OzjICioctNKfvbSA8rOpBbayUgZWjq9MltcRK+UzDUf3TtY/k/jlG7IhrbcSYbjqnxKGPPyG9BId/OJ/3IVtKnb6uopt6mnQ0tzb+2fMGcwir/xhMubRjgd+3A6ZzrKlW+kxIJELfddOf+oZy8xTGf16I= Received: from BLUPR03MB1444.namprd03.prod.outlook.com (10.163.81.153) by BLUPR03MB1444.namprd03.prod.outlook.com (10.163.81.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.323.15; Mon, 18 Dec 2017 21:40:35 +0000 Received: from BLUPR03MB1444.namprd03.prod.outlook.com ([10.163.81.153]) by BLUPR03MB1444.namprd03.prod.outlook.com ([10.163.81.153]) with mapi id 15.20.0323.018; Mon, 18 Dec 2017 21:40:35 +0000 From: "Dippery, Kyle" To: "freebsd-ports@freebsd.org" Subject: Re: A small problem after switching from portmaster to synth Thread-Topic: A small problem after switching from portmaster to synth Thread-Index: AQHTeDnGfDVQ4h25bUeapsn9WDolYaNJmzDS Date: Mon, 18 Dec 2017 21:40:35 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.163.8.81] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BLUPR03MB1444; 6:daE/mp1Zj1vjSu3uTbvv/bRLqdm1ztrfTvQbR3BvvtuOeSIWR2G1FbdXqmpwL98xuLmesLgQjP6XzfSHoKj4yhZwWPyptSI1R6mr/aSRGhH9QLX4RL1/JEcwSP7+rivxrYLsBxu4WRju7KlOhkIBV/X0UbxBvqdATO6TATwz/Zs2crVLMJ6c2pHxD5cNqfacMrejLsqpJrzeCI/obd/cDBf8vlmw8e/NpKt0bmB5SDEQP50pUp9e6utQZELPKClUDPtCk2ytmm7noEQSrgXGNr5KwIHmF9dFKdoQMFSkZRpGQBjivsMDMmT/5Qtyg8QYCdvfEGciR+69cQV5+wNLKEQ1zL1gAFTCY1w21drACA8=; 5:9QVXnLfndafQpYqX+mLlsZ6mbfJn+xXLF3mfAfU4yGynnxONOfFXeh6bZt20LdXx+MDMMn4DzQsjRlqlppsNaYIhYm0L8NIPc0+d4/SWGME+nSsoruSHEj1j5CIAg27+ip4JJhVNcnrU/p/lpCF9a5xnHXZy65Sh+eiFdr2EH5E=; 24:ukB3AnZgJJkOmpLSjF5D4+a6wX+PN5eyj8TIM0kf1YoxuNSKgpc8l+0M2ciQb/tL+H9O6rO1hkL+ILeR+4j9j1P4MdS5eMSaGo0Y/qG547o=; 7:UwTnPNVvYEQg6AbspT9+neglBZopw/imNiUnWWQKBHOpB7PMtcBh41xi/QwiEPJ2xXGuF8PSdA4D5djqRVnmhhmqW+khSFCnfIAEBfbGs0Si3ibJprtqBw2eFRmQaPvviEEXHUjU0MSHY3u4QSOWb1w+RHnMHMlC5UXDtCQn9fWdrs/jeFjs3m+EBvEzj7hYyFNmZ2u3AVq0+8aInbxyiq/jDSrrbyu6Esy4nMjKvSFOvD6vUax7OmhdRBFLfn48 x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 5d980f26-d6bc-4ea3-7212-08d5465ff8da x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(5600026)(4604075)(4534020)(4602075)(4627115)(8989060)(201703031133081)(201702281549075)(8990040)(2017052603307)(7153051); SRVR:BLUPR03MB1444; x-ms-traffictypediagnostic: BLUPR03MB1444: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(192374486261705)(189930954265078)(219752817060721); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231023)(3002001)(6041248)(20161123555025)(20161123560025)(20161123558100)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123562025)(6072148)(201708071742011); SRVR:BLUPR03MB1444; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BLUPR03MB1444; x-forefront-prvs: 0525BB0ADF x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(376002)(39860400002)(396003)(346002)(189003)(199004)(478600001)(8676002)(59450400001)(6436002)(33656002)(6306002)(14454004)(5660300001)(55016002)(2900100001)(5640700003)(2950100002)(81156014)(966005)(75432002)(8936002)(6246003)(6916009)(81166006)(25786009)(74316002)(45080400002)(9686003)(86362001)(66066001)(7736002)(53546011)(53936002)(305945005)(6506007)(316002)(786003)(88552002)(3280700002)(2501003)(2906002)(229853002)(7696005)(99286004)(2351001)(77096006)(106356001)(105586002)(3660700001)(6116002)(97736004)(68736007)(76176011)(102836003)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB1444; H:BLUPR03MB1444.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: uky.edu does not designate permitted sender hosts) authentication-results: spf=none (sender IP is ) smtp.mailfrom=kyle.dippery@uky.edu; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uky.edu X-MS-Exchange-CrossTenant-Network-Message-Id: 5d980f26-d6bc-4ea3-7212-08d5465ff8da X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Dec 2017 21:40:35.2289 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 2b30530b-69b6-4457-b818-481cb53d42ae X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1444 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, 18 Dec 2017 21:40:38 -0000 I don't think this is related to portmaster or synth. The mismatched check= sums list is produced by /usr/local/etc/periodic/security/460.pkg-checksum,= and it seems (for me) to have started after a ports update in mid-November= . The parameter to suppress the output is security_status_pkgchecksum_enable;= set that to "NO" in /etc/periodic.conf, or set security_status_pkgchecksum= _period to "weekly" or "monthly" to get the list less often. But, the parameter described in /etc/defaults/periodic.conf, that looks it = should suppress the output, is security_status_chkportsum_enable. Should = /etc/defaults/periodic.conf be updated to describe the parameter that the s= cript expects? Or are these two different things that I'm not understandin= g? Thanks, Kyle -- Kyle Dippery Engineering Computing Services 219 RMB 859-257-1346 ________________________________________ From: owner-freebsd-ports@freebsd.org on = behalf of Kurt Buff Sent: Monday, December 18, 2017 2:52 PM To: freebsd-ports@freebsd.org Subject: A small problem after switching from portmaster to synth I'm seeing a lot of this in the daily security email after switching: Checking for packages with mismatched checksums: db5-5.3.28_6: /usr/local/share/doc/db5/api_reference/C/BDB-C_APIReference.pdf On one of my machines, it goes on for hundreds of lines, mostly for postgre= sql. I am also seeing a lot of this on a couple of my machines: Checking negative group permissions: find: /usr/ports/devel/pijul/Makefile: No such file or directory I've read through the man page for synth, and I've done a fair amount of STFW, but I don't see a way to fix either of these. Can someone suggest a reference, or a plan of action to fix these? Thanks, Kurt _______________________________________________ freebsd-ports@freebsd.org mailing list https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Flists.fr= eebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-ports&data=3D02%7C01%7Ckyle.dipper= y%40uky.edu%7Cbce06d4c49fd44b9348508d54650e860%7C2b30530b69b64457b818481cb5= 3d42ae%7C0%7C0%7C636492235661238859&sdata=3DI2XySEihgN%2FJaJpx4hLq8YW45conT= bwkHKkMTdRkhqw%3D&reserved=3D0 To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Mon Dec 18 21:51:04 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A7F9E8B29C for ; Mon, 18 Dec 2017 21:51:04 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DC44F71F1A for ; Mon, 18 Dec 2017 21:51:03 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D89F0E8B29B; Mon, 18 Dec 2017 21:51:03 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D611AE8B29A for ; Mon, 18 Dec 2017 21:51:03 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (prod2.absolight.net [79.143.243.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9573571F19 for ; Mon, 18 Dec 2017 21:51:03 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 8A58BBDD31; Mon, 18 Dec 2017 22:51:01 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id 0F4BDBDD2D; Mon, 18 Dec 2017 22:51:01 +0100 (CET) Subject: Re: Option vs. flavor? To: Adam Weinberger , Yuri Cc: "ports@freebsd.org" References: <0CE3611A-F100-4443-93B4-68A0A83F162B@adamw.org> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: <8d13e1fd-bcba-d907-8737-ec8084c76014@FreeBSD.org> Date: Mon, 18 Dec 2017 22:50:58 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <0CE3611A-F100-4443-93B4-68A0A83F162B@adamw.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="0BPRersiE6PHBBfuujfsiCrSOwKxfJIxg" 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, 18 Dec 2017 21:51:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0BPRersiE6PHBBfuujfsiCrSOwKxfJIxg Content-Type: multipart/mixed; boundary="O1eV2NJnbW30aD2GGJtHavKiQ22SffOWD"; protected-headers="v1" From: Mathieu Arnold To: Adam Weinberger , Yuri Cc: "ports@freebsd.org" Message-ID: <8d13e1fd-bcba-d907-8737-ec8084c76014@FreeBSD.org> Subject: Re: Option vs. flavor? References: <0CE3611A-F100-4443-93B4-68A0A83F162B@adamw.org> In-Reply-To: <0CE3611A-F100-4443-93B4-68A0A83F162B@adamw.org> --O1eV2NJnbW30aD2GGJtHavKiQ22SffOWD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 17/12/2017 =C3=A0 15:32, Adam Weinberger a =C3=A9crit=C2=A0: >> On 17 Dec, 2017, at 1:48, Yuri wrote: >> >> On 12/16/17 22:06, Adam Weinberger wrote: >>> Is the port of any use without the data file? If everybody who uses >>> the port needs the data file, I wouldn't make it an option at all. >>> The precedent is that ports with huge data files are marked >>> NO_PACKAGE, so there's no impact on the package builders. Make it >>> non-optional, mark it as NO_PACKAGE, and then the port works for all >>> users. >>> >>> If, however, the port IS real-world usable without the data files, >>> I'd turn the data file into a second port. That way, package people >>> can very easily install the NO_BUILD slave and still install the >>> main program by pkg. >> >> >> Hi Adam, >> >> >> It is usable without data. Portions of the data are recommended to be >> downloaded into the specific directory for particular functions. Of >> course, it's more convenient to just a have all of it installed, and >> users will need all of it for all functions. >> >> This is the large physics package called Geant4 for simulation of the >> passage of particles through matter. https://reviews.freebsd.org/D1350= 4 > > Ah okay. Then I'd say, make a slave port that just > fetches/extracts/installs the data files, and an option in the Geant4 > master port that defaults to off. Set the slave port to NO_PACKAGE. I do not really see any reason to set NO_PACKAGE. There already are big packages in our repositories: -rw-r--r--=C2=A0 2 root=C2=A0 wheel=C2=A0=C2=A0 1,0G 10 d=C3=A9c.=C2=A0 0= 5:49 ufoai-data-2.5.txz -rw-r--r--=C2=A0 2 root=C2=A0 wheel=C2=A0=C2=A0 1,1G 14 d=C3=A9c.=C2=A0 1= 0:06 texlive-docs-20150523.txz -rw-r--r--=C2=A0 2 root=C2=A0 wheel=C2=A0=C2=A0 1,3G 10 d=C3=A9c.=C2=A0 1= 5:30 flightgear-data-2017.3.1.txz -rw-r--r--=C2=A0 2 root=C2=A0 wheel=C2=A0=C2=A0 1,5G 14 d=C3=A9c.=C2=A0 2= 0:24 diaspora-1.1.1_1.txz -rw-r--r--=C2=A0 2 root=C2=A0 wheel=C2=A0=C2=A0 1,7G 10 d=C3=A9c.=C2=A0 0= 5:20 urbanterror-data-4.2.023.txz --=20 Mathieu Arnold --O1eV2NJnbW30aD2GGJtHavKiQ22SffOWD-- --0BPRersiE6PHBBfuujfsiCrSOwKxfJIxg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJaODhEXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85Ia0IP/iLfFmUpBzPNhlqdqkIHMp6q zYvBHLp/YbQiyx/HMaRDrZ8OvE07bIOgWB2BWVzrqAzmrRZUPWWW5oCvlsqSskBs Z36UvrtA394uizlb5qeq0xqxY/VfbNIuuyfbYAanF9ZPa3o51Br+TY14YAmpSkQJ udDp7TWXuWqWpjOCoTkFpZ2DhQNhBSf73ijCmgWaZwLPySzH5H+g15kDT+HYBVE5 NafSIo+yKy9FC3ChU20zcUJC4qwyeGAWnTnHp/5YnhpmcEqUxT+yHjptFczyvGD6 /VIPts0BHdzXVpJN5oTIi5k3iXDUrSoRmtvNIUHqdWd5QEJozoFPjZHdseB5KT5S bdq4V0ks9quTLRAPIAjeaBiLDsE01ovwHBaDQjyL/n/e+A2LLQPvn+oGiC+F2dhE PuwEpiT/OVGl42TLofpX2p++IuQE4VodzQlq44pncSQHHMaLRLuT91TZJGnCk9SD LdjdUOxXOkQwueP8CRr1bBj1fAMQ0VI2Hpr9WtuZl1Dl6Cd+tbJj4Qiyy3xYBD3G Ojs0GdIDLfzuw7TIa8FsqDNKATsmAf+NbL+y6c6dOGxJJdc5nEodKa3U9BFt4DiF DaZ/oAlt00gzjJhZzUrS71hs3ROmNfv/aQ3girFX/xRviuEqdVtlwhkztlqjBYOj uD7eRPjQJCZtmrKhdP5T =sgoR -----END PGP SIGNATURE----- --0BPRersiE6PHBBfuujfsiCrSOwKxfJIxg-- From owner-freebsd-ports@freebsd.org Mon Dec 18 21:56:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F471E8BAA8 for ; Mon, 18 Dec 2017 21:56:54 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 58133727EB; Mon, 18 Dec 2017 21:56:54 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id B42C1BDD25; Mon, 18 Dec 2017 22:56:51 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id 57179BDD1E; Mon, 18 Dec 2017 22:56:51 +0100 (CET) Subject: Re: Can we have multiple flavors for a port? To: Matthew Seaman , FreeBSD Ports ML References: <6ed4ac6e-a075-0fc0-a3da-371a46a9e977@FreeBSD.org> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: <4c380f8c-e590-cf6a-38d6-075db2df63d1@FreeBSD.org> Date: Mon, 18 Dec 2017 22:56:50 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <6ed4ac6e-a075-0fc0-a3da-371a46a9e977@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PxoBNjNR5pUEcjArikllT4rFuFBnhXpB6" 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, 18 Dec 2017 21:56:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PxoBNjNR5pUEcjArikllT4rFuFBnhXpB6 Content-Type: multipart/mixed; boundary="wxrvRm139TiHr6D8vt8sDWSQqjFKpNuV1"; protected-headers="v1" From: Mathieu Arnold To: Matthew Seaman , FreeBSD Ports ML Message-ID: <4c380f8c-e590-cf6a-38d6-075db2df63d1@FreeBSD.org> Subject: Re: Can we have multiple flavors for a port? References: <6ed4ac6e-a075-0fc0-a3da-371a46a9e977@FreeBSD.org> In-Reply-To: <6ed4ac6e-a075-0fc0-a3da-371a46a9e977@FreeBSD.org> --wxrvRm139TiHr6D8vt8sDWSQqjFKpNuV1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 16/12/2017 =C3=A0 14:51, Matthew Seaman a =C3=A9crit=C2=A0: > Given that django-2.0 requires python-3.5+ we end up with the following= > combinations: > > py27 django111 > py36 django111 > py36 django20 So you have: FLAVORS=3D py27_django111 py36_django111 py36_django20 and if BUILD_ALL_PYTHON_FLAVORS is set, you'll need to add py34_django111, py35_django111, py35_django20, but this can be done automatically. > and there's some 104 django ports which will mostly end up needing all > three of these variants built -- so as combinatorial explosions go, it'= s > not particularly earth-shattering. > > However, my questions are: > > - Is it possible or desirable to have multiple flavourings like this?= > > - If so, what should the syntax look like for specifying a particular= > combination? eg. www/py-django-mezzanine@py27+django111 ? > > Cheers, > > Matthew > > --=20 Mathieu Arnold --wxrvRm139TiHr6D8vt8sDWSQqjFKpNuV1-- --PxoBNjNR5pUEcjArikllT4rFuFBnhXpB6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJaODmjXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IN7kP/2O7jORKIYc/GPbKc+3VfCmO wXH1k+1j6CjIYEx0J6OZjj/Kits2Iv1SBbggH4P719+Kc2lDqT93UbKCtqrKsOGo MJE7rdN8ynfMOaFB2J1klObi1+9buA4jGXwDNwMSZkKQgCWbHeGG3YuA77ZO5nK1 pk6250NRjEbd7F0a4qtQejwTOvgARjY4UTqBvOEUDnI1FEPK5DD8u5MxBH+1BKTm nKKUqZZC1r2XQgHOxY6sZtDD2M17VkeIn6bfR+jSukNIEt2ufZEwmAxavDJbRFIj YyND/phEXJvV+OPdWN1tiIKAcHbv+iBAjV+bufBGDQpPD7G3KquwoEWz7hFzn3uq zmC36cP00S5thDC7DxnpxQwDlId5FanvZGAHETqnp1wtAbU5lYpr/GMEw1cymscf MSs2wF0c7pmIh87hbIwBGLQhZGHzwdJHhrfmmfnbsr3NydV6UmzAGfOz2KoslIzM Pa4W/NicQ1jBoWWO7bUzhgLpiJcjB/rgyi90a3ApvGBBDbai3J0dMPx/abxtZKn8 3h/HBqpZpkSNYhZNdX+0LeS8CjnfJBHi2vy2E4MiGEhLwJhqfU36VMAFSMFaUp27 mKy46yYzHSKty3XwWfHCOO61H1NEdxUSxH6wojR2v+QN1Q217Kz/PFnHWZzHgmaq Zr1zHR0pv/RxeYtmyioC =AAn4 -----END PGP SIGNATURE----- --PxoBNjNR5pUEcjArikllT4rFuFBnhXpB6-- From owner-freebsd-ports@freebsd.org Mon Dec 18 22:05:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EA70E8C583 for ; Mon, 18 Dec 2017 22:05:18 +0000 (UTC) (envelope-from lbartoletti@tuxfamily.org) Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) by mx1.freebsd.org (Postfix) with ESMTP id 0038273192 for ; Mon, 18 Dec 2017 22:05:16 +0000 (UTC) (envelope-from lbartoletti@tuxfamily.org) Received: from [192.168.1.14] ([86.200.249.99]) by mwinf5d67 with ME id nZxc1w00P29RLba03Zxcbw; Mon, 18 Dec 2017 22:57:37 +0100 X-ME-Helo: [192.168.1.14] X-ME-Auth: YmFydG9sZXR0aS5sb2ljQG9yYW5nZS5mcg== X-ME-Date: Mon, 18 Dec 2017 22:57:37 +0100 X-ME-IP: 86.200.249.99 Subject: FLAVOR for Qt4 and Qt5 (was Re: Flavor or not for this port?) To: Rainer Hurling Cc: freebsd-ports@freebsd.org References: <46cbd287-186f-9b92-f2a7-d6884c681040@gwdg.de> <37d007c1-0315-5b23-7357-5dc3fcb836fc@gwdg.de> From: "L.Bartoletti" Message-ID: <92d09009-64b3-695a-2282-5acb6ab169f0@tuxfamily.org> Date: Mon, 18 Dec 2017 22:57:36 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <37d007c1-0315-5b23-7357-5dc3fcb836fc@gwdg.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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, 18 Dec 2017 22:05:18 -0000 Hi Rainer, I have made a try with subpackages with success, but I think it's better with flavor (like on OpenBSD). So, I have started to create flavors for this port. For now, I success for qt4 but not yet for qt5. Extract from my Makefile in progress: FLAVORS=    qt5 qt4 FLAVOR?= .if ${FLAVOR:Mqt5} PKGNAMESUFFIX=    -qt5 USE_QT5=    widgets gui core designer gui opengl svg xml buildtools printsupport concurrent PLIST=        ${PKGDIR}/pkg-plist.qt5 PLIST_SUB+=    QT_MKSPECDIR=lib/qt5/mkspecs DOCSDIR=    ${PREFIX}/share/doc/qwt6-qt5 .else PKGNAMESUFFIX=    -qt4 USE_QT4=     corelib gui opengl svg xml moc_build PLIST=        ${PKGDIR}/pkg-plist.qt4 PLIST_SUB+=    QT_MKSPECDIR=lib/qt4/mkspecs DOCSDIR=    ${PREFIX}/share/doc/qwt6-qt4 .endif Ther error for qt5: qwt-qt5-6.1.3 can't be installed: different Qt versions specified via USE_QT[4 5]. Regards. On 17.12.2017 10:12, Rainer Hurling wrote: > Am 02.11.2017 um 07:41 schrieb Rainer Hurling: >> Am 02.11.2017 um 07:13 schrieb L.Bartoletti: >>> Hi, >>> >>> I want to take x11-toolkits/qwt{5,6}-* >>> >>> Both are built for Qt4. I especially need qwt6 for Qt5. Since we have >>> flavors. Is it better to add a Qt5 flavor for Qwt6 or simply add a >>> x11-toolkits/qwt6-qt5 (like security/qtkeychain-qt{4,5} ?) >>> >>> Thanks. >>> >>> Regards. >>> >>> Loïc >> >> Hi Loïc, >> >> Thanks for your dedication. I am very interested in a qwt6-qt5 port, >> since it is needed for the upcoming version 3.0 of graphics/qgis :) >> >> Sorry for my inexperience. In case of adding the qwt6-qt5 as a flavor, >> should we expect any change or restriction in the way, it would be used >> as a dependency of e.g. QGIS? >> >> Thanks for any answer. >> >> Best wishes, >> Rainer > Hi Loïc, > > Again about x11-toolkits/qwt{5,6}-* > > Now, that we have our first real world experiences with FLAVORS, it > seems to be functional to use flavors in this context. Something like > > x11-toolkits/qwt6@qt4 > x11-toolkits/qwt6@qt5 > > A bit tricky could be, that USE_QT* are different in both cases: > > USE_QT4= corelib gui opengl svg xml moc_build > USE_QT5= core gui opengl svg xml printsupport qmake_build widgets > > What do you think? > > Best wishes, > Rainer > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Mon Dec 18 22:09:36 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18B66E8C906 for ; Mon, 18 Dec 2017 22:09:36 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB01373399 for ; Mon, 18 Dec 2017 22:09:35 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa01.server.lan (via HTTP); Mon, 18 Dec 2017 23:09:28 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: freebsd-ports@freebsd.org Subject: Canberra Content-Type: text/plain; charset=UTF-8 Date: Mon, 18 Dec 2017 23:09:28 +0100 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:EomPT/UaGPOyO0a1b19Dai3q2PrS4ajXaevl6wr3JcC slhgKYwvcUDazgX7fLY4vfi8LhHk/yhJh6uh7Z4oejMJ2SUaE6 F5MEuwyWMo5BrdjdvUjBNga8cjf7bhp9gg6Sz3Z8ar5BdfYfsy ZSLj6PBBKlRE70MmlcxQOUlljKGB+vbEoQpjk9L3c89Q63YSRy ZoX/hFRCZ+vPBTKVkF+a/M1k24cbI8t46y4cZUjZcASmP+1cVL Z6IYK1+LONAUjjzYAc5K0zrt8LuEQ9aWsqv564AL1NZEGFtR0R atIXs4= X-UI-Out-Filterresults: notjunk:1;V01:K0:h2uQqjQnFE8=:7GeQI2tS19aCSXjdcWAem8 XdyOEueeyvHRiXyOYgspK56fM7Tl8oe8Fv2LALiKq3m4DsOGRxHq6sh98DF9z7uMUVC/IolsC MYmI4S2tahMilmvmsf7jRUjf/O7ZOWLDRMiWIwIOJDrW0lJyYPTaHecdLF9Py8/UG7SWapfZE DtrMUpizMgHpNjupumkNQa6EWFkYvnSfRA+3zlcFs61wYVpasL3v/Tt66CDtlENl07p7PmTnn ZwOtt3agPGPeX4xwutcEvVmzvD97AqBfPCz1awF8g2n8XRG7Kcs1REs75eb4d40tvlnh9WqlT hozbTZZNbDLDc90iISXL38/kOCIfVRdONmve8LI5dPNDFm1GyWZ1SclNiY07FjBL9nHH4CGCV E6G0B2znq6rynl/Ec4Kygob1vDs2PKzheZWKKCef33ceXI+eClxLL/cElgH+fK0AfVjcipBw8 r+qUvHhpUaY+JA477JARKmhdEO3O9/buQQiNNk0dtZsspPi0jXTWYCRb+9d19GMj2PE5Zn/zs OPged/HX8FtDKXMxBlGgWZbgSTnFeVr3b3WoUszEsSt 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, 18 Dec 2017 22:09:36 -0000 Canberra is an audio application for playing simple sounds like "DING!". For playing sound, I am convinced that graphical dependencies for audio/libcanberra and audio/libcanberra-gtk3 aren't needed: x11-toolkits/gtk30, x11-toolkits/gtk20, accessibility/atk. According to Freshports, both libcanberra and libcanberra-gtk3 refer to the file libcanberra-0.30.tar.xz of the same SHA256 and size. The difference between these two is one pulls in gtk3 as well. Pango is for left to right text, perhaps for displaying audio information to the user. Its description is its "code is platform- and toolkit-independent." For it to display a simple banner or visual it shouldn't require heavy graphical dependencies. Also, Pango should be made into an option for Canberra, so it can definitely be compiled without atk, gtk30 or gtk20. Pango doesn't require these three graphical dependencies, so Canberra especially shouldn't. USE_GNOME should also be a Makefile option in ports that are only about sound (libraries, applications, audio server components) and not graphics. From owner-freebsd-ports@freebsd.org Mon Dec 18 22:11:06 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B4F5E8CB11 for ; Mon, 18 Dec 2017 22:11:06 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D3C3735F3 for ; Mon, 18 Dec 2017 22:11:05 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-qt0-x230.google.com with SMTP id i40so21962537qti.8 for ; Mon, 18 Dec 2017 14:11:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=14xGdvWEooHd39pdw1pprpGh3CasttJ+4iHq5bLgWrw=; b=h/5eSYt9/cChSwfF94ysU/Daj5C49Jau5g4lYSZFKJqXRV+eCh8Xwg5JmEepOTHFHe xLLtmMOmugmUqs/FeQSyXDu2lQMGQmn0Cf18Qpeo0p74b5qHCeDo7HYBS+P9tjBSldNE R4LhEYwtYhj9PozPYVMtBX5qFojJCvARO1vU9y1HpVa7SbIV2TzBBMfbSa0+/0V5KBJH J61K+T5a0u6aId+xmj4YPQylGr2/1Ai+tCz9AvLYlHmRPdQsQ9O5n4vcFznfrfW3NzjX ezPIpgeAzEzCs58+6cuaZMrsGc8UNk3POQLQLmLkMYcCkLG/D84i6lMnaMRCwtZTVyF+ LwEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=14xGdvWEooHd39pdw1pprpGh3CasttJ+4iHq5bLgWrw=; b=ojECdKon6ioh7Li/iKkFsRij02tq3S94TY2q1AgcfAQpP7sZKqwDNSePAVQyms2aGg 0sZwpYSWHhlaXPzWYH4osqfyOS3ku8D2i2V0v1Gl1YA6VYQLqh/7gCNaDrQ4Efu0QkqT 02dP5E1FER9P5XyjplG7YM1nAJvYuKxfPrrDG1C30GpA9RZ6znjmZm6VDaCOxvvHkHNI 7l7VMMBvGXRtaisXpOy/xN+u+Dvs2kSXB2EBnsmaxx/RiFyVaxytl5++wMbWaA9RLpHk Ud4/cxaiE2lDwXpo8+4IYdFoCgJwhQxH3EtFS8Qt8lVnNRCihe5nqv/YdjDh8Mgprz+0 /XQA== X-Gm-Message-State: AKGB3mLS8gW6/SlzPmYF23UK5rPa6o9t6eyWAUvHObR34gQY66Ayjeb5 KTDC8A8HZ+bM+En+kMkUuDW7iXBaWWWWaU+3DA4wFg== X-Google-Smtp-Source: ACJfBotPR8i9EQtknTLR5+wZfOX+c6ANvoNhDFbVOrtbaere/SIyug9W/qrmN24wE59nFCLZziN2Xw3w1zy6xCZ1h+o= X-Received: by 10.200.53.97 with SMTP id z30mr1952231qtb.330.1513635064694; Mon, 18 Dec 2017 14:11:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.86.212 with HTTP; Mon, 18 Dec 2017 14:11:04 -0800 (PST) X-Originating-IP: [203.99.129.1] In-Reply-To: References: From: Jonathan Chen Date: Tue, 19 Dec 2017 11:11:04 +1300 Message-ID: Subject: Re: A small problem after switching from portmaster to synth To: Kurt Buff Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 18 Dec 2017 22:11:06 -0000 On 19 December 2017 at 08:52, Kurt Buff wrote: > I'm seeing a lot of this in the daily security email after switching: > > Checking for packages with mismatched checksums: > db5-5.3.28_6: > /usr/local/share/doc/db5/api_reference/C/BDB-C_APIReference.pdf > > On one of my machines, it goes on for hundreds of lines, mostly for postgresql. This is not a synth issue, but possibly a security issue. The security check is correctly flagging possibly hi-jacked files. You should forcibly reinstall the port to ensure that the artifacts that the port builds is what you've got installed on your host. I have to say that the only lines that have been flagged for me are due to the port binary altering files configuration files, which should have been located in /var instead of /usr/local. Cheers. -- Jonathan Chen From owner-freebsd-ports@freebsd.org Mon Dec 18 22:34:26 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9114AE8E4C9 for ; Mon, 18 Dec 2017 22:34:26 +0000 (UTC) (envelope-from coder@tuxfamily.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7A90F7447E for ; Mon, 18 Dec 2017 22:34:26 +0000 (UTC) (envelope-from coder@tuxfamily.org) Received: by mailman.ysv.freebsd.org (Postfix) id 77030E8E4C7; Mon, 18 Dec 2017 22:34:26 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7692DE8E4C5 for ; Mon, 18 Dec 2017 22:34:26 +0000 (UTC) (envelope-from coder@tuxfamily.org) Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EA5B27447D for ; Mon, 18 Dec 2017 22:34:25 +0000 (UTC) (envelope-from coder@tuxfamily.org) Received: from [192.168.1.14] ([86.200.249.99]) by mwinf5d67 with ME id naaN1w00D29RLba03aaNZ2; Mon, 18 Dec 2017 23:34:23 +0100 X-ME-Helo: [192.168.1.14] X-ME-Auth: YmFydG9sZXR0aS5sb2ljQG9yYW5nZS5mcg== X-ME-Date: Mon, 18 Dec 2017 23:34:23 +0100 X-ME-IP: 86.200.249.99 Subject: Re: pkg flavors breaks "make run-depends-list" To: Lbartoletti , Mathieu Arnold , jamie@thompson.dyslexicfish.net, ports@freebsd.org References: <5a211e3f.75a86.3b51aeec@thompson.dyslexicfish.net> <92e85df7-bc3f-09ae-4dba-238dcdcd9d5e@FreeBSD.org> <20171201123253.5361749.79318.12678@tuxfamily.org> From: lb Message-ID: <99fda0c0-1c9e-0803-4f60-f068fbce8acd@tuxfamily.org> Date: Mon, 18 Dec 2017 23:34:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171201123253.5361749.79318.12678@tuxfamily.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: fr-FR 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, 18 Dec 2017 22:34:26 -0000 Hi, Is it possible to add the flavors into the name returned by build-depends-list? An example: Loic@FreeBSD:/usr/ports|⇒  make -C x11-toolkits/py-qt5-gui build-depends-list FLAVOR=py36 /usr/ports/ports-mgmt/pkg /usr/ports/lang/python36 /usr/ports/devel/py-sip ... Should be /usr/ports/devel/py-sip@py36 Regards. Loïc On 01.12.2017 13:32, Lbartoletti wrote: > Hi Mat‎hieu, > > I personaly use Make depends-list‎ in a python tools ( https://gitlab.com/lbartoletti/portsgraph)  to draw a graph of dependencies from ports. I hope release it a day. > > Regards. > > Envoyé de mon smartphone BlackBerry 10. >   Message d'origine > De: Mathieu Arnold > Envoyé: vendredi 1 décembre 2017 13:19 > À: jamie@thompson.dyslexicfish.net; ports@freebsd.org > Objet: Re: pkg flavors breaks "make run-depends-list" > > Le 01/12/2017 à 10:17, jamie@thompson.dyslexicfish.net a écrit : >> *2* 09:05 (25) "py-pytz" root@thompson# make run-depends-list >> py27-pytz-2017.3,1: "/usr/ports/devel/py-setuptools@py27" non-existent -- dependency list incomplete >> /usr/ports/lang/python27 > I fixed both build and run-depends-list in r455280. > (As we do not really like to maintain things that are not used by > anything in the framework, I would be interested by what you are using > them for exactly.) > From owner-freebsd-ports@freebsd.org Tue Dec 19 00:41:50 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DBC8E96A95 for ; Tue, 19 Dec 2017 00:41:50 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.io-tx.com", Issuer "AlphaSSL CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03FFB79786; Tue, 19 Dec 2017 00:41:49 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (authenticated bits=0) by io-tx.com (8.15.2/8.15.2) with ESMTPSA id vBJ0URdp010291 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Dec 2017 18:30:27 -0600 (CST) (envelope-from ted@io-tx.com) Date: Mon, 18 Dec 2017 18:30:27 -0600 (CST) From: Ted Hatfield To: Matthias Andree cc: freebsd-ports@freebsd.org, Sunpoet Po-Chuan Hsieh Subject: Re: Procmail got updated! In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 X-Virus-Scanned: clamav-milter 0.99.2 at io-tx.com X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=5.0 on io-tx.com tests=ALL_TRUSTED, AWL, T_RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 user=root X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on io-tx.com Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Tue, 19 Dec 2017 00:41:50 -0000 On Mon, 18 Dec 2017, Matthias Andree wrote: > Am 18.12.2017 um 00:17 schrieb Dave Horsfall: >> Doing my regular update, and... >> >>     Upgrading procmail from 3.22_9 to 3.22_10... >> >> Good grief; who's the masochist who volunteered to support this >> obscure insecure and hitherto-unsupported scripting language? >> > https://svnweb.freebsd.org/ports?view=revision&revision=455800 > > I'd agree we should pull the plug on the package. We'll be in for the > usual "but it works for me" screaming of the irresponsible people who > don't care (and most of them won't know that they need to write the > exception/error handling themselves in their .procmailrc recipes). > > Sunpoet, can we mark the port as deprecated given that even the upstream > once said it should best be abolished? I can't find the reference now, > the procmail.org website displays "Site hosting in transit, information > will be back up shortly." > Dear Matthias, As one of the "irresponsible" people who is still using procmail on our systems and has built an number of scripts and customer infrastructure around it I take exception to the term irresponsible. Perhaps the better word is overworked. If I had the time to move to dovecot/sieve or maildrop as a local delivery agent I would have done so by now. Ted Hatfield From owner-freebsd-ports@freebsd.org Tue Dec 19 00:50:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4AEC0E97326 for ; Tue, 19 Dec 2017 00:50:40 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1704D79AEF for ; Tue, 19 Dec 2017 00:50:40 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: by mail-io0-x232.google.com with SMTP id l10so11783361ioc.3 for ; Mon, 18 Dec 2017 16:50:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=TC8uY6rTGBM9E9mUX7T7jwh0DY8ad4vhCnYn3kSF1HQ=; b=GFc1IHSPEz3yw+tWvGVkEh33Befl2ANmeOLw0sIx9tqXtSyfUl7wBYFt23WQdh5nIC Nrzt568Qb18C8WeByurWmi1CfWT5yMSG2GaLoA5Fg9pjd1JVIBQ+A4AAIEVSuTs1iujV a/R+F2kqf2Q0RJz8+zPF7S7mPzMLdDxLUWe1LJSZ0bbN+hJAUQBM5g9I6IGRW4hv6q9f kXLTBKBiQe40Ce9Tt9tDfzFW90s+sVT4fj2NCmj221xfmwB5/HJOqST+5SZfR6yq9gfp eV0+x8XN+prj9SiZJkG3wDMwbNyWTPAMr+LaP4q4ud1b4vl8ZhjgayljX2IzlCxWBSRI SkJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=TC8uY6rTGBM9E9mUX7T7jwh0DY8ad4vhCnYn3kSF1HQ=; b=IoPIrjV266sRile/YBGiurc8Nrgo9vgyxZY/SS+uDdBxp7VfY9T90bUBQEPjVio2wv jSYSoXAErB5y+eSGI5tUC5kV5G6wyB8o7XVCGYrXqUkFrlK6/WjguBtUK1yLhQ8RzlpP 6zC+58XpFplMBeGzJqNPUd+N+mjOdivxdgYf610KSbSOAtFF3w0AiBZ05456fQHHOtqB mvAzpsOEzpCyPbXlpjEJoLc7dNv40Kf4ehtuQVDLAq5SdKLQtHpwT0sb/zcIjNpJOT+b VFqj7pOrYtKjqjr/dTn5lMtiFcgLVQb0x5rynHR7xTwdxNN03zbU/YzDClm8yH5AQYWL S1Wg== X-Gm-Message-State: AKGB3mKj5LQh699h4C0GEYrU29FM7E+JiJGzSZQOPj/5411l5G1r4l+J ae2+yOtwnIYLd63q0BzYi9LWTJ4cdrxCfKmDlf3KTg== X-Google-Smtp-Source: ACJfBovIvqkfDbqkQmz7F/QpgEbxNFKma1xSDG9qlXVm10Y0fSfFYotl2ltr4C+EryMphdM+C5W7dWYweMF91Ei0Wrg= X-Received: by 10.107.32.70 with SMTP id g67mr1990768iog.69.1513644639065; Mon, 18 Dec 2017 16:50:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.9.199 with HTTP; Mon, 18 Dec 2017 16:50:38 -0800 (PST) In-Reply-To: References: From: Kurt Buff Date: Mon, 18 Dec 2017 16:50:38 -0800 Message-ID: Subject: Re: A small problem after switching from portmaster to synth To: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Tue, 19 Dec 2017 00:50:40 -0000 On Mon, Dec 18, 2017 at 2:11 PM, Jonathan Chen wrote: > On 19 December 2017 at 08:52, Kurt Buff wrote: >> I'm seeing a lot of this in the daily security email after switching: >> >> Checking for packages with mismatched checksums: >> db5-5.3.28_6: >> /usr/local/share/doc/db5/api_reference/C/BDB-C_APIReference.pdf >> >> On one of my machines, it goes on for hundreds of lines, mostly for postgresql. > > This is not a synth issue, but possibly a security issue. The security > check is correctly flagging possibly hi-jacked files. You should > forcibly reinstall the port to ensure that the artifacts that the port > builds is what you've got installed on your host. I have to say that > the only lines that have been flagged for me are due to the port > binary altering files configuration files, which should have been > located in /var instead of /usr/local. > > Cheers. > -- > Jonathan Chen I have a file called ports.txt, which I used for portmaster. It contains the master list of ports for this machine, and has the following lines in it: benchmarks/iperf ftp/curl ftp/wget mail/postfix ports-mgmt/pkg ports-mgmt/portmaster security/ike-scan security/nmap security/sslscan www/lynx net/mosh dns/bind-tools security/metasploit sysutils/tmux I tried this, with the following result: root@fbsd01p:~ # synth force /root/ports.txt Regenerating flavor index: this may take a while ... Scanning entire ports tree. progress: 100.00% raised ADA.IO_EXCEPTIONS.NAME_ERROR : file "/var/synth/live_packages/All/" does not exist These are the lines that have me scratching my head on this machine from the daily security email: Checking negative group permissions: find: /usr/ports/devel/pijul/Makefile: No such file or directory find: /usr/ports/devel/pijul/distinfo: No such file or directory find: /usr/ports/devel/pijul/pkg-descr: No such file or directory find: /usr/ports/devel/pijul: No such file or directory find: /usr/ports/devel/ppl/Makefile: No such file or directory find: /usr/ports/devel/ppl/distinfo: No such file or directory find: /usr/ports/devel/ppl/pkg-descr: No such file or directory find: /usr/ports/devel/ppl/pkg-plist: No such file or directory find: /usr/ports/devel/ppl: No such file or directory find: /usr/ports/devel/py-pyopencl/Makefile: No such file or directory find: /usr/ports/devel/py-pyopencl/distinfo: No such file or directory find: /usr/ports/devel/py-pyopencl/files: No such file or directory find: /usr/ports/devel/py-pyopencl/pkg-descr: No such file or directory find: /usr/ports/devel/py-pyopencl: No such file or directory find: /usr/ports/devel/pylint/Makefile: No such file or directory find: /usr/ports/devel/pylint/distinfo: No such file or directory find: /usr/ports/devel/pylint/pkg-descr: No such file or directory find: /usr/ports/devel/pylint/pkg-plist: No such file or directory find: /usr/ports/devel/pylint: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk/Makefile: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk/distinfo: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk/pkg-descr: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk-core/Makefile: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk-core/distinfo: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk-core/pkg-descr: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk-core: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk-resources/Makefile: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk-resources/distinfo: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk-resources/pkg-descr: No such file or directory find: /usr/ports/devel/rubygem-aws-sdk-resources: No such file or directory Checking for packages with mismatched checksums: p5-XML-SAX-0.99_2: /usr/local/lib/perl5/site_perl/XML/SAX/ParserDetails.ini On another machine, it looks like "synth force" is working, but I'm sure it's going to take a while. Kurt From owner-freebsd-ports@freebsd.org Tue Dec 19 02:19:56 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BB34EA03FB for ; Tue, 19 Dec 2017 02:19:56 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 39B347DFE8 for ; Tue, 19 Dec 2017 02:19:56 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa01.server.lan (via HTTP); Tue, 19 Dec 2017 03:19:54 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: freebsd-ports@freebsd.org Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Tue, 19 Dec 2017 03:19:54 +0100 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:t+aFCWMHi8gqvH+k8QXNfKc9+iSBLOv+MsQoYB2f6et 72BWBU20Bw2sgQrbXoLcCUUPF3wLXLddbzb6sTNKLeEYHEfrCE MlNc5OpMOLh1klGW9WuA+V5a/3Zft5A5HGHL0ZD2FAGqOOk20U iiAugio/bXSj6fMVGXBTSCMYfZ+QzOlIzTe6YwgP0r1o07Wzmq MXKUubv79k5fBteO8l4x/EbwZeWsbVCXbxJcNbWHFtP2Yb7weD fSzUviViXHqlqkzKytBhemQWlJY/3JukkpF5GaX9Bt+1SggSOX Ejpy1c= X-UI-Out-Filterresults: notjunk:1;V01:K0:GdusWYK76bI=:PX5L4DCdj2lJzSrHz2Haya 7oxwGaW+G7xWn4F3cAERygVsW3JxI4XCdpI12DtQHlqgCvT6wgQyu1T85+TlW3gmHj4FuslQ3 yDEMF5lj/lx2ZXilkMxewfKMwb33RFmp6IdIYGq98SXR+1qkpo9f5hz2QwDh5MuxMKAT8PEhW MbQ0zRBw57Zmd0lWSfv3OTFZ9sG74wC3MahhWiCbsx33n+PpZ/bf7xYmt25Ysj0XaJt+D6aHQ kS3yBeBhNHmjujasBZn10BxxC2HwQWEa8nqFW2XGXSOAxqBvlF/6G03oRZNHluSAyShe89MzJ Ae4Sj4baSMaw6xbcCtF55AGkbp0s5HAOlHEdB9pd5r0LWDezCzY8tPFRBFCdFF+eESn5rLBqm NVLjNbyJVj14/qTw+OErUK8sLhO+l3T/TxnMmntZwwZ7iF0eLu+H8D/vdBgjCXq0idAWRCUN8 6QHtR2E7ncpnqTByGmls5s1KLtihcsZcTwTYABerbGs6j1pdfExidZAdKqjXa9Tqaz3MT4xmB hviLYvRkx3GNK+IcFB7HoG7cCBv03PTb2ZTgyRDEtZF 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: Tue, 19 Dec 2017 02:19:56 -0000 >Sid; Mon Dec 18 22:09:36 UTC 2017 > Canberra is an audio application for playing simple sounds like "DING!". > For playing sound, I am convinced that graphical dependencies for audio/libcanberra and audio/libcanberra-gtk3 aren't needed: x11-toolkits/gtk30, x11-toolkits/gtk20, accessibility/atk. > According to Freshports, both libcanberra and libcanberra-gtk3 refer to the file libcanberra-0.30.tar.xz of the same SHA256 and size. > The difference between these two is one pulls in gtk3 as well. > Pango is for left to right text, perhaps for displaying audio information to the user. > Its description is its "code is platform- and toolkit-independent." > For it to display a simple banner or visual it shouldn't require heavy graphical dependencies. > Also, Pango should be made into an option for Canberra, so it can definitely be compiled without atk, gtk30 or gtk20. > Pango doesn't require these three graphical dependencies, so Canberra especially shouldn't. > USE_GNOME should also be a Makefile option in ports that are only about sound (libraries, applications, audio server components) and not graphics. libcanberra and libcanberra-gtk3 should be replaced with audio/freedesktop-sound-theme. Pango appears to be a different implementation of Bango, which is not in ports, but here: https://www.freedesktop.org/wiki/Bango/. From owner-freebsd-ports@freebsd.org Tue Dec 19 03:01:07 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8A32EA43AF for ; Tue, 19 Dec 2017 03:01:07 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D03980529 for ; Tue, 19 Dec 2017 03:01:07 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id p139so1086644itb.1 for ; Mon, 18 Dec 2017 19:01:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Hkjg4guzhty0AiLyE6ysALa/dq9qvrGWE2hf4ooZDgQ=; b=CdvoujVGMXFrYggYk2zUkS2fAGCm/jOtOOjbJtGBwMjqa5S5yc/8qqZrmPfUKrOtna u9RSFj2iQl/PXzCYkAlMkdR8z2/8r2tP42zPakHkh3MFP7Y2gKu5PErptkdeHaZG6Itd czt5+ZUmqrpSUf9qH+N1b10pg/JrQDICNl1PM2YXXQUydlJv4GeZ++1eUkxJnNfLbGOf 9WUy6Q/54HxP/E3DimeIhF2Drj3xJh59nvGRxNvRPO7zkugBfNOHaHfk1tg/5jfpdykW aibMaf9JrDf7aKowlHVyzeObwZ6fiGbk8tQYPvdorbp84hOwvASy8OeG7+4uMz28KnKp AxiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Hkjg4guzhty0AiLyE6ysALa/dq9qvrGWE2hf4ooZDgQ=; b=ElEqRFxKJK7Fl2CodC1fOlsf/u0Mbu5L+MznfFBa6Vbo3EiyPgBL20urNbMVI4VTlE KhcdgISlMBpLK+XGiHdXpM8MT13Mg33BlelDFs4tEb/N7QeeNTp/U3gveGeRe5C4GfcK 2zLsHwtZI/q0nnQ29mhTFxryMSCYW6Tg+9gqxeg6uAGpc3u/vWvKYl5AXCBlMNjG24C3 eohnW875RcTmiBRXjc6PhjDbqVOMWZaNd0XJETcbGUruExfk+dBniYyceisMuLqy85L2 oscOb23/Xi3DBqSRUJXh/S2iXT1+DKLKCjbBRLs+2luq8Jl1tknetDkZdQ81SCSkbJgt HzEw== X-Gm-Message-State: AKGB3mKJTwJwCic5Qt4wN1PiwLRtppO1dUIkcBjmUq2AtxIaYCvn9OLs +tWUojJPy++uDENNIhHNMxj66UnCWxsL4J5tf8k= X-Google-Smtp-Source: ACJfBotX00/cii8PCevxZTEONhfnMEUYPj0JAwLCKxSwe8VYR/kmaWaN+nKLu/Do8yiFr7wZVem1LquyBaohgddNtuI= X-Received: by 10.36.221.147 with SMTP id t141mr1469807itf.140.1513652466467; Mon, 18 Dec 2017 19:01:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Mon, 18 Dec 2017 19:01:05 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Tue, 19 Dec 2017 11:01:05 +0800 Message-ID: Subject: Re: Canberra To: Sid Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Tue, 19 Dec 2017 03:01:07 -0000 On Tue, Dec 19, 2017 at 10:19 AM, Sid wrote: > >Sid; Mon Dec 18 22:09:36 UTC 2017 > > Canberra is an audio application for playing simple sounds like "DING!". > > For playing sound, I am convinced that graphical dependencies for > audio/libcanberra and audio/libcanberra-gtk3 aren't needed: > x11-toolkits/gtk30, x11-toolkits/gtk20, accessibility/atk. > > According to Freshports, both libcanberra and libcanberra-gtk3 refer to > the file libcanberra-0.30.tar.xz of the same SHA256 and size. > > The difference between these two is one pulls in gtk3 as well. > > > Pango is for left to right text, perhaps for displaying audio > information to the user. > > Its description is its "code is platform- and toolkit-independent." > > For it to display a simple banner or visual it shouldn't require heavy > graphical dependencies. > > Also, Pango should be made into an option for Canberra, so it can > definitely be compiled without atk, gtk30 or gtk20. > > Pango doesn't require these three graphical dependencies, so Canberra > especially shouldn't. > > USE_GNOME should also be a Makefile option in ports that are only about > sound (libraries, applications, audio server components) and not graphics. > > libcanberra and libcanberra-gtk3 should be replaced with > audio/freedesktop-sound-theme. > Pango appears to be a different implementation of Bango, which is not in > ports, but here: https://www.freedesktop.org/wiki/Bango/. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > quick question, I am porting py-canberra which isn't required but an optional dependency for another port that I am working on. ibus-cangjie. The ibus-cangjie port needs py-gobject anyways; so a whole lot of gtk stuff gets pulled in. I wonder should I leave it as is or make a dependency from this thing you're working on instead? I was waiting for @flavors to calm down before I started working on the port again. From owner-freebsd-ports@freebsd.org Tue Dec 19 03:11:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 659EFEA500C; Tue, 19 Dec 2017 03:11:14 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2297B80E4D; Tue, 19 Dec 2017 03:11:14 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x234.google.com with SMTP id w127so12030920iow.11; Mon, 18 Dec 2017 19:11:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=2YkfHLjpeS0obeVnuuV0yqG+eluQguqU0M6sd496rro=; b=nL2jg8nZmOKbsw7YCAd3lOMtJigBbhLsM9SJrz9UZKI2yrJv5cCVXDM+LKvdVF4vQ6 azJ8PZ5qHoY74ue4j4bahmr3O5j5uEsiNeYionAYmYR368a0Dw7boV9tu1iPVjVCeaMJ aR62XgDfcs6CWyo9F9tB7AcEJrEflz96ZTJXrCKr8qtU0W5tJz/B92HPwqy2ZrrYzPRW 37ZkPSIK0HGR7M/gfrUvuNZy5a5sDlNWJXMaa7AaOhW1UMQwPRZ0iqStmBKUJ54m0Cgr XBK/hC+Cb1XLtT++VUQt8ibl7MEguIzNyzVsVFU4Y2EEi0VZmgzghhyW0z0EjeSKw6aV wTPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=2YkfHLjpeS0obeVnuuV0yqG+eluQguqU0M6sd496rro=; b=g8bFSveiZ38SR4VPIQmIDntNqdAJF64NVMogg17CHU/ImXSTSa9AmSTZW7e77mrqyy D37I+f5V0FHi15YFLGbXv7J4yye2rzBrDEcBhEwH1wmGpuUiwrCyKdw655B46/exmEQG SrmRIH583JaI/1zAYzzkOxNXDSbB1cCNja0X+xEuqCAKMSo2VNYF2xW1mOXTH75/b2aw lHMn37zQUAkOg50JIk3g3G5rfibBYAYzWH8Fn8pney+FeJCPeqyiOMjqGil3j+gX6aYl JxrCu/yquF4PzM9BL/U07CGv1IBN+KVnkh864pvKR4Sd5Qi7rhkaWG69an9qfXYVU8k7 bbgw== X-Gm-Message-State: AKGB3mIiIDTaf7fd3EPynVn7m3fIB/smt/hbSS0yH/YrNrf/UjaJCzhJ m8lVIYuikpGtVL204trcNFl8WzYQzeCpy/KSFJxS2A== X-Google-Smtp-Source: ACJfBos0WakIu/gq72BnE2e9nkGtdrcuelmElLHODD8PuvqVfSgJk+sOFHjlP51lpoQanyGGIBOIbJzAr0+y6+cYB48= X-Received: by 10.107.83.8 with SMTP id h8mr2177088iob.63.1513653073303; Mon, 18 Dec 2017 19:11:13 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.131.163 with HTTP; Mon, 18 Dec 2017 19:10:52 -0800 (PST) In-Reply-To: References: From: Ed Maste Date: Mon, 18 Dec 2017 22:10:52 -0500 X-Google-Sender-Auth: pMmn0pnVUHXgjHw1zIgjFHzBW34 Message-ID: Subject: Re: Ports and LLVM's lld linker To: FreeBSD Ports , freebsd-toolchain@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Tue, 19 Dec 2017 03:11:14 -0000 On 27 November 2017 at 15:39, Ed Maste wrote: > We're making good progress on using LLVM's lld linker as FreeBSD's > /usr/bin/ld, so I'd like to raise awareness of the new linker within > the ports community. With a couple of recent changes in src head (r326831 and r326897) lld is now suitable for use as the base system /usr/bin/ld on amd64 and i386. We're working through ports failures, starting with those responsible for the largest number of skipped ports. The top four, on amd64: port # skipped devel/libunwind 7994 databases/postgresql*-client 230 lang/fpc 76 lang/mono 22 The remaining failures are responsible for no more than 2 skipped ports each. devel/libunwind fails due to the shared object protected visibility symbol preemption issue; Dimitry Andric and I are searching for an appropriate fix. The databases/postgresql*-client failures have been worked around by r456635, adding LLD_UNSAFE=yes so that the port uses ld.bfd. lang/fpc appears to suffer from stricter validation performed by lld: /usr/bin/ld: error: x86_64/units/x86_64-freebsd/i_linux.o: invalid alignment of section headers lang/mono fails because lld defaults to -z text, disallowing relocations in read-only segments (like .text). A workaround is to add -z notext to the link command line, which turns off lld's error for this case and results in the same behaviour as ld.bfd and ld.gold provide by default. Unfortunately usual workarounds (LLD_UNSAFE=yes or LDFLAGS=Wl,-z,notext) fail for both lang/fpc and lang/mono, and it's not immediately obvious to me how their respective builds handle the options. I'll probably need help from acm@ and mono@ for these. For reference the remaining ports failing with lld on amd64 are: archivers/lua51-zlib audio/alure benchmarks/wrk databases/postgres-xl devel/libds devel/libtecla devel/pdcurses devel/ztcl emulators/gem5 ftp/rexx-curl irc/eggdrop irc/eggdrop-devel irc/evangeline lang/rexx-imc lang/rexx-regutil lang/siod lang/smlnj lang/tclX mail/qmail-dk math/rexx-regmath misc/seabios net-im/uTox net/py-netif net/py-netif print/openprinting print/pdftk security/otpw shells/bash-static sysutils/dupd sysutils/e2fsprogs sysutils/installwatch sysutils/unieject www/cgihtml www/dummyflash www/mod_jk www/mozplugger www/tdom From owner-freebsd-ports@freebsd.org Tue Dec 19 04:52:48 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B7E4E860E2 for ; Tue, 19 Dec 2017 04:52:48 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 52C4C649E1 for ; Tue, 19 Dec 2017 04:52:48 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa03.server.lan (via HTTP); Tue, 19 Dec 2017 05:52:45 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: "blubee blubeeme" Cc: "FreeBSD Ports" Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Tue, 19 Dec 2017 05:52:45 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:mjEujOVBNIcX2+YfSSW/xh9RvxMIQBzFh9rivG/rXDN zyFtP79eJyY03tOTBrU4rxAg2Fhs7pApksMycN/nbp64sPNFIL Z4J5fMqqwQbvNgaGt9YIX3R6okBazANY2iOjnY6LHYKEpt5uKU ZD19v2Lw9euyIagkFdEDuL75tTg+TcyyYa3EtlS8ItlealempD D5dsD6fsscP2Xq0eTNYl1SCt4y5IZejMAW8/xZdd68hmfB3rtc ij9ZTx2FbsFuzGUP8yD2NPFHhcHLASxsgmG/g51yzna4VhGJ63 dRb6LQ= X-UI-Out-Filterresults: notjunk:1;V01:K0:40dpUgL61qw=:88CNbNwvtTWGrsU++6Looj C0Nszm/IXq1mwi+mxtgKevjmenMKWzozM2T4xQRcrUtecKsbBVmckbp0rE2Sv9pS1p7tXzBOC MP2eOk8aRSm1L5Ckm7scy8ccuB69jv8gI337WSM+2GSYktFZ5aGF04hxxx6pN+BZxmHGGKzln KtPDC4bBCyY8d0p4aN3ULX6/CwXurzILtdzDsgRgmi5LIPdjntwmQtpPMnaTyIhXsjMn9x/sx Rm0UzsiBtW3c9tSG0MsqppdSnB/uhfOtHTNs5I2rfKM1MKes8S2vhwyO8LdDq84M0mFxWu6Cw X54/RPPqsjldGFyeWtA+i2NnctMSkqJwwLjkTI3uWE1MXIGpUPyfES90bsF40SP7VERzjrgwm RWBcGN8cvmYftxkDR4KTUecaI9nInWY60Ob84o0PurxD6xZJjzGw3kV7PKevDhXCXYkDcdvgN lTRiKZS7RY7JMxpCHQu9OBAHIEtmMlhLp4ZpH18l8wwS6oXizg42OZeG+PwZrXpSSCrjObZZ4 Gdz2efzKdkZOUTRdWzbmTQ0XG0ypRrsnbVqUgYR7zUB 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: Tue, 19 Dec 2017 04:52:48 -0000 devel/pycanberra audio/freedesktop-sound-theme hasn't been tested for most ports that ask for libcanberra, and I haven't tried it on any port yet either. The source for pycanberra may need patches to work with freedesktop-sound-theme. You could include both as options. If they conflict, you'll have to use OPTIONS_RADIO (single choice). In any case, libcanberra should drop gtk requirements, but they may be reluctant to do so. pycanberra's name implies it's for libcanberra. IMO, it's better to clean up as many ports before flavors comes along, because then, there will be more excuses to not remove bloat. blubee blubeeme; Tue Dec 19 03:01:07 UTC 2017 > quick question, I am porting py-canberra which isn't required but an optional dependency for another port that I am working on. > ibus-cangjie. > The ibus-cangjie port needs py-gobject anyways; so a whole lot of gtk stuff gets pulled in. > I wonder should I leave it as is or make a dependency from this thing you're working on instead? > I was waiting for @flavors to calm down before I started working on the port again. >> Canberra is an audio application for playing simple sounds like "DING!". >> For playing sound, I am convinced that graphical dependencies for audio/libcanberra and audio/libcanberra-gtk3 aren't needed: x11-toolkits/gtk30, x11-toolkits/gtk20, accessibility/atk. >> According to Freshports, both libcanberra and libcanberra-gtk3 refer to the file libcanberra-0.30.tar.xz of the same SHA256 and size. >> The difference between these two is one pulls in gtk3 as well. >> Pango is for left to right text, perhaps for displaying audio information to the user. >> Its description is its "code is platform- and toolkit-independent." >> For it to display a simple banner or visual it shouldn't require heavy graphical dependencies. >> Also, Pango should be made into an option for Canberra, so it can definitely be compiled without atk, gtk30 or gtk20. >> Pango doesn't require these three graphical dependencies, so Canberra especially shouldn't. >> USE_GNOME should also be a Makefile option in ports that are only about sound (libraries, applications, audio server components) and not graphics. >> libcanberra and libcanberra-gtk3 should be replaced with audio/freedesktop-sound-theme. >> Pango appears to be a different implementation of Bango, which is not in ports, but here: https://www.freedesktop.org/wiki/Bango/[https://www.freedesktop.org/wiki/Bango/]. From owner-freebsd-ports@freebsd.org Tue Dec 19 04:58:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C85A6E867A0 for ; Tue, 19 Dec 2017 04:58:59 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B67E64C0C for ; Tue, 19 Dec 2017 04:58:59 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x234.google.com with SMTP id a25so4867588uak.3 for ; Mon, 18 Dec 2017 20:58:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=+gROVtv7JqGodARRF2t5dXWSZwVyajQcHeyVjn3tz8Q=; b=OjOF7kKO9zkQrtBbLQ8KOIdFWUd8LepFY2QSUpUuJFfYw9zCJLNxm0Vrcbvf+qVFK2 0wZf6lRRJAAfxER5BR1su8ymmqC0znfUJt9juuKosE3YHqcmVMRK5ll+IX8waTBKUhWE 60EGs43z7qsdSMyxpB7EIZl0UzUBiuwlX1zU9JfPnbVuaG82Ndus+ARlmd5zyBsb50X/ q6K6ruK3WYtH40HtVqkqicEum+b+W3x9bco4TiiTt2fBKtREKNIJIZvJV04uAjmfPJB1 Ic3yVoadlqWB6dleDNXW7uoOJMdWMRFN+DgBvys4w3nvrQct4BQRuXHkFHfDLebLTsSL DI2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=+gROVtv7JqGodARRF2t5dXWSZwVyajQcHeyVjn3tz8Q=; b=mhLXmBHarq1XKeGVP5XGTuo3ExoGsmqhAQrjqwLSoAay08eWkIzjXk0FAhk5yrUIEa ZBNdAXZmAY8nkXGUqhkH8/ogvUD+/MkmunVEFVTP29Nij6+P8N43f6LOQ5q0arvIoq0p cF5mSHz4njGoH1nvrQcscGbLxVKutQ5yg7Lcb6icuRmhLFQwWxZA+934sCFEWjiEmOuW ef/WQCo09/V3x0F2RmEOtEb7xO4ZX4Nawu22OAy/db9UZ5puZYntxLIef+GKJvBl/xiB 7ai4Vcv8q0x3A19QlRY7K36H8bjlvL3ci/hvpk0+krBfXiH1thHzyGueFlg+u/4ecokT celw== X-Gm-Message-State: AKGB3mKXlz+aHb7Pw7JQJbTu8/tEUooR5f7Pu9ErdovVBU0iyNE2O+q/ xY6LBQuizTc1Q3WhDG0T/aciKH77NXR+QQvDtCw= X-Google-Smtp-Source: ACJfBouDgiNjjwy2vHq5CLXRXlBdNRZjHgR50+wQAoOg2KTY1rqVsIse1aVnlg719olvC9FjlKEXcELguXzfwRR2Rnc= X-Received: by 10.176.8.71 with SMTP id b7mr2082451uaf.168.1513659538249; Mon, 18 Dec 2017 20:58:58 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.147.156 with HTTP; Mon, 18 Dec 2017 20:58:57 -0800 (PST) In-Reply-To: References: From: Kevin Oberman Date: Mon, 18 Dec 2017 20:58:57 -0800 X-Google-Sender-Auth: 2wQcCz9Pf8Vj2TF4g8VEiAIAcC8 Message-ID: Subject: Re: A small problem after switching from portmaster to synth To: Kurt Buff Cc: FreeBSD Ports ML Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Tue, 19 Dec 2017 04:58:59 -0000 PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Mon, Dec 18, 2017 at 4:50 PM, Kurt Buff wrote: > On Mon, Dec 18, 2017 at 2:11 PM, Jonathan Chen wrote: > > On 19 December 2017 at 08:52, Kurt Buff wrote: > >> I'm seeing a lot of this in the daily security email after switching: > >> > >> Checking for packages with mismatched checksums: > >> db5-5.3.28_6: > >> /usr/local/share/doc/db5/api_reference/C/BDB-C_APIReference.pdf > >> > >> On one of my machines, it goes on for hundreds of lines, mostly for > postgresql. > > > > This is not a synth issue, but possibly a security issue. The security > > check is correctly flagging possibly hi-jacked files. You should > > forcibly reinstall the port to ensure that the artifacts that the port > > builds is what you've got installed on your host. I have to say that > > the only lines that have been flagged for me are due to the port > > binary altering files configuration files, which should have been > > located in /var instead of /usr/local. > > > > Cheers. > > -- > > Jonathan Chen > I have a file called ports.txt, which I used for portmaster. It > contains the master list of ports for this machine, and has the > following lines in it: > benchmarks/iperf > ftp/curl > ftp/wget > mail/postfix > ports-mgmt/pkg > ports-mgmt/portmaster > security/ike-scan > security/nmap > security/sslscan > www/lynx > net/mosh > dns/bind-tools > security/metasploit > sysutils/tmux > > > I tried this, with the following result: > root@fbsd01p:~ # synth force /root/ports.txt > Regenerating flavor index: this may take a while ... > Scanning entire ports tree. > progress: 100.00% > > raised ADA.IO_EXCEPTIONS.NAME_ERROR : file > "/var/synth/live_packages/All/" does not exist > > These are the lines that have me scratching my head on this machine > from the daily security email: > Checking negative group permissions: > find: /usr/ports/devel/pijul/Makefile: No such file or directory > find: /usr/ports/devel/pijul/distinfo: No such file or directory > find: /usr/ports/devel/pijul/pkg-descr: No such file or directory > find: /usr/ports/devel/pijul: No such file or directory > find: /usr/ports/devel/ppl/Makefile: No such file or directory > find: /usr/ports/devel/ppl/distinfo: No such file or directory > find: /usr/ports/devel/ppl/pkg-descr: No such file or directory > find: /usr/ports/devel/ppl/pkg-plist: No such file or directory > find: /usr/ports/devel/ppl: No such file or directory > find: /usr/ports/devel/py-pyopencl/Makefile: No such file or directory > find: /usr/ports/devel/py-pyopencl/distinfo: No such file or directory > find: /usr/ports/devel/py-pyopencl/files: No such file or directory > find: /usr/ports/devel/py-pyopencl/pkg-descr: No such file or directory > find: /usr/ports/devel/py-pyopencl: No such file or directory > find: /usr/ports/devel/pylint/Makefile: No such file or directory > find: /usr/ports/devel/pylint/distinfo: No such file or directory > find: /usr/ports/devel/pylint/pkg-descr: No such file or directory > find: /usr/ports/devel/pylint/pkg-plist: No such file or directory > find: /usr/ports/devel/pylint: No such file or directory > find: /usr/ports/devel/rubygem-aws-sdk/Makefile: No such file or > directory > find: /usr/ports/devel/rubygem-aws-sdk/distinfo: No such file or > directory > find: /usr/ports/devel/rubygem-aws-sdk/pkg-descr: No such file or > directory > find: /usr/ports/devel/rubygem-aws-sdk: No such file or directory > find: /usr/ports/devel/rubygem-aws-sdk-core/Makefile: No such file > or directory > find: /usr/ports/devel/rubygem-aws-sdk-core/distinfo: No such file > or directory > find: /usr/ports/devel/rubygem-aws-sdk-core/pkg-descr: No such file > or directory > find: /usr/ports/devel/rubygem-aws-sdk-core: No such file or directory > find: /usr/ports/devel/rubygem-aws-sdk-resources/Makefile: No such > file or directory > find: /usr/ports/devel/rubygem-aws-sdk-resources/distinfo: No such > file or directory > find: /usr/ports/devel/rubygem-aws-sdk-resources/pkg-descr: No such > file or directory > find: /usr/ports/devel/rubygem-aws-sdk-resources: No such file or > directory > > Checking for packages with mismatched checksums: > p5-XML-SAX-0.99_2: /usr/local/lib/perl5/site_perl > /XML/SAX/ParserDetails.ini > > On another machine, it looks like "synth force" is working, but I'm > sure it's going to take a while. > > Kurt I also see this with Checking for packages with mismatched checksums: urwfonts-ttf-1.0.7b18_6: /usr/local/share/fonts/urwfonts-ttf/fonts.dir urwfonts-ttf-1.0.7b18_6: /usr/local/share/fonts/urwfonts-ttf/fonts.scale I tried re-installing the port, but the messages have not changed. I really should have dome more to trackit down as it is potentially serious, but have not gotten around to it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com From owner-freebsd-ports@freebsd.org Tue Dec 19 05:07:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE8CAE87095 for ; Tue, 19 Dec 2017 05:07:25 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2EEDC65135; Tue, 19 Dec 2017 05:07:24 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBJ577Xd086160 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Dec 2017 06:07:08 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: ted@io-tx.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id vBJ56uKK021666 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 19 Dec 2017 12:06:56 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Procmail got updated! To: Ted Hatfield , Matthias Andree References: Cc: Sunpoet Po-Chuan Hsieh , freebsd-ports@freebsd.org From: Eugene Grosbein Message-ID: <5A389E6C.8040108@grosbein.net> Date: Tue, 19 Dec 2017 12:06:52 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net 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: Tue, 19 Dec 2017 05:07:25 -0000 19.12.2017 7:30, Ted Hatfield wrote: > > > On Mon, 18 Dec 2017, Matthias Andree wrote: > >> Am 18.12.2017 um 00:17 schrieb Dave Horsfall: >>> Doing my regular update, and... >>> >>> Upgrading procmail from 3.22_9 to 3.22_10... >>> >>> Good grief; who's the masochist who volunteered to support this >>> obscure insecure and hitherto-unsupported scripting language? >>> >> https://svnweb.freebsd.org/ports?view=revision&revision=455800 >> >> I'd agree we should pull the plug on the package. We'll be in for the >> usual "but it works for me" screaming of the irresponsible people who >> don't care (and most of them won't know that they need to write the >> exception/error handling themselves in their .procmailrc recipes). >> >> Sunpoet, can we mark the port as deprecated given that even the upstream >> once said it should best be abolished? I can't find the reference now, >> the procmail.org website displays "Site hosting in transit, information >> will be back up shortly." >> > > Dear Matthias, > > As one of the "irresponsible" people who is still using procmail on our systems and has built an number of scripts and customer infrastructure around it I take exception to the term irresponsible. Perhaps the better word is overworked. If I had the time to move to dovecot/sieve or maildrop as a local delivery agent I would have done so by now. > > Ted Hatfield +1 From owner-freebsd-ports@freebsd.org Tue Dec 19 05:12:07 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AE20E87519 for ; Tue, 19 Dec 2017 05:12:07 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0256465492 for ; Tue, 19 Dec 2017 05:12:06 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id f143so1348818itb.0 for ; Mon, 18 Dec 2017 21:12:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ioddVDVFpUOztFBa1xhRfOHee6DNM57pzZrH4rUtzyE=; b=SdshKKyDFmNNQBJsoTGUrSecmnWZmr4ynFrs0jjU4yU/nXdC41eYvgyYzdOl/sB6aZ LUROzj/+AgO3q5b284x+7uJMFd6yFZPF67tZTy0oTs891oHFDHhOJf/O3PdVZBXtiHU2 40n4OTBB7MuxK5LZ5G8MffkjFegVB2nwJCFYk5A+6UGy66/Etu0LL6+XQJSy1pQP7ngq TMBGjyCvHKDC1ASAsnYvb053puI15U9nbhg8HH5h08o9bd37BKKAHjdBkeiSH4VavwCo GqvP65Pcauz5FCEfxmC52EITZF7KZw+xgctupHNtrYUKAT7OkPZoTuXMy88Sp8vDcJEW fFgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ioddVDVFpUOztFBa1xhRfOHee6DNM57pzZrH4rUtzyE=; b=SoeFuNrwOXmgOv7kKAeVnvX7BMEgik+zxRmwjM+bQsm1s0OUnjnmHRGnvJ424nTqXJ Kbr/57qCfEgA5XaFBd4Rodf6chblToCZQMV0/0pYG8caBtz1KTt6+Vh6wnX2i9ENGa+k ta222wfWC5LzMIa4U9fjee4nCugp2jAqu4PZU91IkFvudAqbAHcS6a3cEbwR/gcki0qX En6+K0pJCvh3vTqW01Y5C0D51+Qg2FiiFv1ZImBMoA/p9JCXOXvzq5WvbFThy/XJNbox Bxwql2c2MrqL2wwiKTonbSIpRT8ixJB4JqLvpU/gYJs9H/m0ejyL+Z0b+72DbXtmpU6l kYSw== X-Gm-Message-State: AKGB3mJR6W53M5WfzHxjBXMRoE8OBZeuAufEZyB6m+l3ogcMZGHO+itL deHE0pqurQmzrGNLEWi8O54O53zypUsHq2jS5hQ= X-Google-Smtp-Source: ACJfBov8B3e9ynOPHUXDVFuxiwxRZ4LWi4BfictwsPJZrRwObyD5gzHOgQ0yQl4J5e0xXk8JDzfnch0z9JsvVsrZ7jU= X-Received: by 10.36.151.198 with SMTP id k189mr1888906ite.100.1513660326151; Mon, 18 Dec 2017 21:12:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Mon, 18 Dec 2017 21:12:05 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Tue, 19 Dec 2017 13:12:05 +0800 Message-ID: Subject: Re: Canberra To: Sid Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Tue, 19 Dec 2017 05:12:07 -0000 On Tue, Dec 19, 2017 at 12:52 PM, Sid wrote: > devel/pycanberra > > audio/freedesktop-sound-theme hasn't been tested for most ports that ask > for libcanberra, and I haven't tried it on any port yet either. The source > for pycanberra may need patches to work with freedesktop-sound-theme. You > could include both as options. If they conflict, you'll have to use > OPTIONS_RADIO (single choice). In any case, libcanberra should drop gtk > requirements, but they may be reluctant to do so. pycanberra's name implies > it's for libcanberra. > > IMO, it's better to clean up as many ports before flavors comes along, > because then, there will be more excuses to not remove bloat. > > blubee blubeeme; Tue Dec 19 03:01:07 UTC 2017 > > quick question, I am porting py-canberra which isn't required but an > optional dependency for another port that I am working on. > > ibus-cangjie. > > > The ibus-cangjie port needs py-gobject anyways; so a whole lot of gtk > stuff gets pulled in. > > I wonder should I leave it as is or make a dependency from this thing > you're working on instead? > > > I was waiting for @flavors to calm down before I started working on the > port again. > > >> Canberra is an audio application for playing simple sounds like "DING!". > >> For playing sound, I am convinced that graphical dependencies for > audio/libcanberra and audio/libcanberra-gtk3 aren't needed: > x11-toolkits/gtk30, x11-toolkits/gtk20, accessibility/atk. > >> According to Freshports, both libcanberra and libcanberra-gtk3 refer to > the file libcanberra-0.30.tar.xz of the same SHA256 and size. > >> The difference between these two is one pulls in gtk3 as well. > > >> Pango is for left to right text, perhaps for displaying audio > information to the user. > >> Its description is its "code is platform- and toolkit-independent." > >> For it to display a simple banner or visual it shouldn't require heavy > graphical dependencies. > >> Also, Pango should be made into an option for Canberra, so it can > definitely be compiled without atk, gtk30 or gtk20. > >> Pango doesn't require these three graphical dependencies, so Canberra > especially shouldn't. > >> USE_GNOME should also be a Makefile option in ports that are only about > sound (libraries, applications, audio server components) and not graphics. > > >> libcanberra and libcanberra-gtk3 should be replaced with > audio/freedesktop-sound-theme. > >> Pango appears to be a different implementation of Bango, which is not > in ports, but here: https://www.freedesktop.org/wiki/Bango/[https://www. > freedesktop.org/wiki/Bango/]. > py-canberra is just a python wrapper for libcanberra, I agree that ports should be cleaned. I'll get back to that in the coming days, I have some soldering and other things keeping me a bit tied up atm. From owner-freebsd-ports@freebsd.org Tue Dec 19 05:57:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0EA2E8A6E2 for ; Tue, 19 Dec 2017 05:57:18 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AE2766E9C for ; Tue, 19 Dec 2017 05:57:18 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa08.server.lan (via HTTP); Tue, 19 Dec 2017 06:57:14 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: "blubee blubeeme" Cc: "FreeBSD Ports" Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Tue, 19 Dec 2017 06:57:14 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:nP6Odp1QNmihokfpe9Px0ENnw9WwwEz/UgdQqZIN+wR YkRwB7nwCQNL4m8Xn8wne4a9CF//31GLU8JHAnf4chFWT4TZzd fccE26MWGtzQVfWg679tosthFQ3IlR/+G8szH6fz6X/zDZLihw lMd8YYjpje5Sdo+vzpKD1s8jmoH4MYKxJqTypMqk7gPPxiQg3r MYIdZjRT7e3NYVbMqeQw0jTq1VWkrNx0egK9qKLKwn8LzkX6jE nUYlPm8ppFeUhjgDNOB7Mi2fYpm7vzITXBPcor8xlUfqe9xTzK ZpXJnk= X-UI-Out-Filterresults: notjunk:1;V01:K0:3CWDW540SeI=:mqdEBoZXsa8nObJP3DphrK PcTQiDsPSo2yDBDYuM5U2skrtwKg/MCKdCblqt49iK9lp7QDZyBOW/SJVdN3nHLtYmh3NdemG RIDGnBM75tNYg5qeYIYdDY+CH6LqzoXu/Lv2EAMIRVFXmDcaj8KJNEolH/lC0kQTDyifiBrxV FTmgI5SVgWBJzYPySE7ElFJb1HPbF5X7cmhehNS0CqkADBNzZEdTRdDk7RefyEiV+z5RgowSF le+oXM+WqTBSbBDuVOWNKKihCaR3kLlJyQtgTSUd+Sgg/cX3z9zeuzRVjPwNIomAPrw5yCiXH e7cgHPf1sQVBFeqDQzxP7DFnYMRJ2yOTaMP3RdCveM4/Xex8b0lMPwtoazhQcWlxFVPn8Yaxu hMpIAS0l/DP8rYPlp05G/3QQxYqcM2vtN0c3HYTd5MSoEvLX/Ynmssdh9gJ6No45cQDvuZQCZ Z+cFVQW2r+EDl4ISIpklvMIuEhD/YbrtJ6KX7tqdc2xhvr1de3diQBRFMtsz835pmIry06rzS ahiqXDugEiTATxF7axDGf2854E9hu1dJjLnb38Oy9Yw 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: Tue, 19 Dec 2017 05:57:18 -0000 The port audio/freedesktop-sound-theme just has sound files, and no libraries. From owner-freebsd-ports@freebsd.org Tue Dec 19 06:04:53 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E1CEE8AEA6 for ; Tue, 19 Dec 2017 06:04:53 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1286467323; Tue, 19 Dec 2017 06:04:52 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from [134.76.11.225] (helo=email.stud.uni-goettingen.de) by mailer.gwdg.de with esmtp (Exim 4.80) (envelope-from ) id 1eRB1A-0003E4-0a; Tue, 19 Dec 2017 07:04:44 +0100 Received: from UM-EXCHT-A01.um.gwdg.de (134.76.9.210) by um-excht-s1.um.gwdg.de (134.76.9.213) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 19 Dec 2017 07:04:43 +0100 Received: from pc028.nfv.nw-fva.de (134.76.242.1) by email.gwdg.de (134.76.9.210) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 19 Dec 2017 07:04:43 +0100 To: , From: Rainer Hurling Subject: devel/R-cran-gsubfn: broken because of missing dependency Message-ID: <9fe24297-1969-6b93-5954-351dfa9306b7@gwdg.de> Date: Tue, 19 Dec 2017 07:04:37 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit X-Spam-Level: - X-Virus-Scanned: (clean) by clamav 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: Tue, 19 Dec 2017 06:04:53 -0000 Hi Steven, devel/R-cran-gsubfn was marked broken recently because it fails in staging with: ** byte-compile and prepare package for lazy loading Warning: S3 methods 'as.character.tclObj', 'as.character.tclVar', 'as.double.tclObj', 'as.integer.tclObj', 'as.logical.tclObj', 'as.raw.tclObj', 'print.tclObj', '[[.tclArray', '[[<-.tclArray', '$.tclArray', '$<-.tclArray', 'names.tclArray', 'names<-.tclArray', 'length.tclArray', 'length<-.tclArray', 'tclObj.tclVar', 'tclObj<-.tclVar', 'tclvalue.default', 'tclvalue.tclObj', 'tclvalue.tclVar', 'tclvalue<-.default', 'tclvalue<-.tclVar', 'close.tkProgressBar' were declared in NAMESPACE but not found Error : package or namespace load failed for 'tcltk': .onLoad failed in loadNamespace() for 'tcltk', details: call: fun(libname, pkgname) error: Tcl/Tk support is not available on this system Error : unable to load R code in package 'gsubfn' ERROR: lazy loading failed for package 'gsubfn' It seems, that tcltk is needed as a dependency from FreeBSD ports. Something like USES=tcl and USES=tk should do the trick? Best regards, Rainer Hurling From owner-freebsd-ports@freebsd.org Tue Dec 19 06:23:57 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D912E8C1AD for ; Tue, 19 Dec 2017 06:23:57 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 83F0567D63 for ; Tue, 19 Dec 2017 06:23:57 +0000 (UTC) (envelope-from se@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 83414E8C1AC; Tue, 19 Dec 2017 06:23:57 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82E20E8C1AB for ; Tue, 19 Dec 2017 06:23:57 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout09.t-online.de (mailout09.t-online.de [194.25.134.84]) (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 468CC67D62; Tue, 19 Dec 2017 06:23:56 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd01.aul.t-online.de (fwd01.aul.t-online.de [172.20.27.147]) by mailout09.t-online.de (Postfix) with SMTP id 56F83425C310; Tue, 19 Dec 2017 07:23:48 +0100 (CET) Received: from Stefans-MBP-2.fritz.box (TzRhXkZeQhfJVkCGPPRiAsLnbFtHg7e7lnCXedjuKbAoytwgBwRwn9DaG+7lkUMwky@[84.154.114.37]) by fwd01.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1eRBJR-0XGMnw0; Tue, 19 Dec 2017 07:23:37 +0100 Subject: Re: pkg flavors breaks "make run-depends-list" To: lb , Lbartoletti , Mathieu Arnold , jamie@thompson.dyslexicfish.net, ports@freebsd.org References: <5a211e3f.75a86.3b51aeec@thompson.dyslexicfish.net> <92e85df7-bc3f-09ae-4dba-238dcdcd9d5e@FreeBSD.org> <20171201123253.5361749.79318.12678@tuxfamily.org> <99fda0c0-1c9e-0803-4f60-f068fbce8acd@tuxfamily.org> From: Stefan Esser Message-ID: Date: Tue, 19 Dec 2017 07:23:36 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <99fda0c0-1c9e-0803-4f60-f068fbce8acd@tuxfamily.org> Content-Type: text/plain; charset=UTF-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-ID: TzRhXkZeQhfJVkCGPPRiAsLnbFtHg7e7lnCXedjuKbAoytwgBwRwn9DaG+7lkUMwky X-TOI-MSGID: 00fe2370-6849-445b-9f72-64050fc72397 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: Tue, 19 Dec 2017 06:23:57 -0000 Am 18.12.17 um 23:34 schrieb lb: > Hi, > > Is it possible to add the flavors into the name returned by build-depends-list? > > An example: > > Loic@FreeBSD:/usr/ports|⇒  make -C x11-toolkits/py-qt5-gui build-depends-list > FLAVOR=py36 > /usr/ports/ports-mgmt/pkg > /usr/ports/lang/python36 > /usr/ports/devel/py-sip > ... > > Should be /usr/ports/devel/py-sip@py36 I have already proposed the same (with patch), see https://reviews.freebsd.org/D13535 You can download the patch for testing from: https://reviews.freebsd.org/D13535?download=true Regards, STefan From owner-freebsd-ports@freebsd.org Tue Dec 19 06:47:27 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0529E8DFCC for ; Tue, 19 Dec 2017 06:47:27 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B055A68D42 for ; Tue, 19 Dec 2017 06:47:27 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=mz7VzWjRIvKLt5JUYKSEibtjY25NHgTlmbsOB1Qa/zw=; b=TBnwdPVxbqTa6OOJRwVVYhEcqdcwSfMQHXlCyydWBcH5EEkB+LkTvlaXcoaQaeiQQ4jZqf1Cjzw17o1AoR2pb4js3yuHbtS80tAze/vAc60aEKxctUP4GMsawKzTqVB6VGVz+4xwpvf4JNCESIh2uNUarZ/oac4k7rV6Wtg8WUA=; Received: from paris.xoc.tele2net.at ([213.90.36.7]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1eRBgT-0001ba-4o for freebsd-ports@freebsd.org; Tue, 19 Dec 2017 07:47:25 +0100 Received: from 91-115-91-196.adsl.highway.telekom.at ([91.115.91.196] helo=[10.0.0.93]) by paris.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1eRBgT-0008AV-1D for freebsd-ports@freebsd.org; Tue, 19 Dec 2017 07:47:25 +0100 To: freebsd-ports@freebsd.org References: Subject: Re: A small problem after switching from portmaster to synth From: Walter Schwarzenfeld Message-ID: Date: Tue, 19 Dec 2017 07:47:19 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 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: Tue, 19 Dec 2017 06:47:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224407 From owner-freebsd-ports@freebsd.org Tue Dec 19 07:21:53 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B73DDE90593 for ; Tue, 19 Dec 2017 07:21:53 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 77C5B6A046 for ; Tue, 19 Dec 2017 07:21:53 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=PMv50j2m9eEe5akgO27szeDYaHACYIfc/k6C9javuT4=; b=ZtOreUV4YWo/PNM/PQ1vbvfqMC7YezTfmi4VxH3fdH7neFtOUt9n1YYDWNZdBOwnkvLA97zPLvw2ceeqyZ7OhJ2aJ7LSf5jkmMZtWGDwgk18DfoJKSSSWtAcXiAUFNWUp/wx4T/WLaFUuVrgthpyqYEVybnmMFt1rS2yZl1/wfI=; Received: from patricia.xoc.tele2net.at ([213.90.36.9]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1eRCDm-0005nQ-Iy for freebsd-ports@freebsd.org; Tue, 19 Dec 2017 08:21:50 +0100 Received: from 91-115-91-196.adsl.highway.telekom.at ([91.115.91.196] helo=[10.0.0.93]) by patricia.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1eRCDm-00081p-FM for freebsd-ports@freebsd.org; Tue, 19 Dec 2017 08:21:50 +0100 To: freebsd-ports@freebsd.org References: <9fe24297-1969-6b93-5954-351dfa9306b7@gwdg.de> Subject: Re: devel/R-cran-gsubfn: broken because of missing dependency From: Walter Schwarzenfeld Message-ID: <00945d91-f273-3ac4-042d-e3eb504dd0e2@utanet.at> Date: Tue, 19 Dec 2017 08:21:46 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <9fe24297-1969-6b93-5954-351dfa9306b7@gwdg.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 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: Tue, 19 Dec 2017 07:21:53 -0000 Is in math/R the option tcl/tk=on? From owner-freebsd-ports@freebsd.org Tue Dec 19 07:24:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6D85E908D3 for ; Tue, 19 Dec 2017 07:24:25 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 745E76A272 for ; Tue, 19 Dec 2017 07:24:25 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa03.server.lan (via HTTP); Tue, 19 Dec 2017 08:24:21 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: freebsd-ports@freebsd.org, gurenchan@gmail.com Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Tue, 19 Dec 2017 08:24:21 +0100 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:mYAGppUNgg3K36rcy8qB/L2zx5T+kf2E3Dn2JawBXnD AQGyKeESNrjmXE3DFVHcno9a5Cpj8DiXQBLCFF81nPSjNLUp1f kXSIbTJ+NU8J0xQIfnyZRGoQqqugnK1OJabHrYWIK7tPXbJ3MR 45XvvUEx2gmBmvyFyMmMNWRVtp7FuGRZE4/M+JVD7a2j6d8eAN LvBVWTRnTvNhLR887AXF5T4spySiRszQ2JJz7cY7qWAm/0zdvn izLNjdmWXNMR+i2Ju6cpgrx8GrYgHmjBzc/5uOxzLdLG8y8h5l OUz83Y= X-UI-Out-Filterresults: notjunk:1;V01:K0:tYTl//bppck=:/RQqUgBJlCJkjXfaOzFdtP llQBZNL86rC5T6JrNgUjiYV7jejAjmOMRiofHpDyy/n1Cp6jF9XCUgZInyeAwI5sSITidgfds jRUx6zB5SL0zlxMG7B1vLudMBReexXxZXWaAGSpkHmhn4acyc/qUUQE/oVjG3AqL9NM9/yfnT legtJ3NngAEK4ECxMMJMDNw+cfkrrmKM28i3jzf9mMB9YmRpG/NbOOxVmEn8U921qja9/wR+e xHMxaUJjztQltqZ2nta5kbVPvWOqhRiHjLTycxSwY9yMzPg2uBEwJ4/f1cu0g9HcFoJ4at5H6 wvlk6N6uGLcI5DR/1Unl6bVfcpKkwRZoq6074ObpeVgJyXAv0TgcRT0IrbhkWtmWOcfaYTojv VuMA6RznVo8k+zWVkkNBF43DyYU6LJL/1fez9HEJ9p1odvd5Cfybc43K8UrZcZSwVEE8sKTnf xvB3i9F5MUUeLFUP77OQSlIgYhqtg3YfTYopqz5dZz8/3yVe541macZVODEHhHrSvy7fyOLtn HnaOVva4mWGGJHaAuwLNv1zjUbjYqrKHeG6uh6N6Ysa 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: Tue, 19 Dec 2017 07:24:25 -0000 > blubee blubeeme > I am porting py-canberra which isn't required but an > optional dependency for another port that I am working on. > I wonder should I leave it as is or make a dependency from this thing you're working on instead? > blubee blubeeme > py-canberra is just a python wrapper for libcanberra Perhaps audio/libcanberra should be a dependency of devel/pycanberra. audio/libcanberra-gtk3 looks like it has options and requests for unnecessary dependencies. > Sid > Canberra is an audio application for playing simple sounds like "DING!". > For playing sound, I am convinced that graphical dependencies for audio/libcanberra and audio/libcanberra-gtk3 aren't needed: x11-toolkits/gtk30, x11-toolkits/gtk20, accessibility/atk. > According to Freshports, both libcanberra and libcanberra-gtk3 refer to the file libcanberra-0.30.tar.xz of the same SHA256 and size. > The difference between these two is one pulls in gtk3 as well. libcanberra-gtk3 also has options for pulseaudio, and gstreamer. > Pango is for left to right text, perhaps for displaying audio information to the user. > Its description is its "code is platform- and toolkit-independent." > For it to display a simple banner or visual it shouldn't require heavy graphical dependencies. > Also, Pango should be made into an option for Canberra, so it can definitely be compiled without atk, gtk30 or gtk20. > Pango doesn't require these three graphical dependencies, so Canberra especially shouldn't. > The port audio/freedesktop-sound-theme just has sound files, and no libraries. pango and freedesktop-sound-themes should be options for libcanberra. I'm convinced that gtk30, gtk20, atk, pulseaudio, and gstreamer shouldn't be options or required in libcanberra or libcanberra-gtk3. (pango and atk are not in the Makefiles, but Freshports shows them.) libcanberra-gtk3 should be merged back into libcanberra. I've only tested removing all of these options for one port that asked for both canberra libraries, and it compiled and played sound. Thank you. From owner-freebsd-ports@freebsd.org Tue Dec 19 07:30:41 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88D40E90F11 for ; Tue, 19 Dec 2017 07:30:41 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F7C86A524 for ; Tue, 19 Dec 2017 07:30:41 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x233.google.com with SMTP id x28so1678451ita.0 for ; Mon, 18 Dec 2017 23:30:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fpuBZi0u3N7U7PJHOA62xmFWn0tqyava+wGjyqdj5RY=; b=OvMkIbb0bNwkoqb0hLLj1bWwJZqaBaVwexb91IUt7PsWPwJjTg6INHETWF9MD8jW10 BQ5tlZ+3onUqsig1jnEUx1MFGSr5VKxqoQZcLbwJUS2MH4/vDJshYHzySxD6v9DZQReZ 566n6cv2SwtlJZJZ15h5dYVAlW6osTLxrqYw5WlWJxzNYmy0AtN3bJH1BORcbkuX+G7n p/T/Q8rIXY8426fvqfQsEbSP4NZ/wpDVF0eTGKVx7lIn6G8oEEhub9VhxjbqCb7jLPsg xzj4NK1ATOnRIs5YSKHeTzlPlTwv/F7c+mOIgNm+LKKI4jN6MhwyhltLtmc9SDCTp68F Xx2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fpuBZi0u3N7U7PJHOA62xmFWn0tqyava+wGjyqdj5RY=; b=Soi+G+W06aSpSHEWWbzphJx2+mLycsIz3XJacyExfTC3SpNT8S/iBXVnfDeMIcZcBy sANdQb0XAMxWoCIRNhgGjFs+TJCCqbUfFb5wGc2aYVbMb51EZxGekyZyBSf3fwueIrPO 0tuYp4bZH25x3nqBg1gQ+z220BFbq3VEF9OE4C84Cw7Xo9ryWvwfSWhYRK/r8hNx7FDg 7pkEe7fRbouT5S0rxiCGzPfDGVNb31qZpZiqhViMjpBl2TE1bPDjJMa86poCUIp8TDXd PFcUmvNUvp/jM6jT64KkijrK5oPJ0BelZ1p67B9NbpxqncXl9UVMYtMtR7CxdsJ5I6La GJkg== X-Gm-Message-State: AKGB3mI3oqjuakFEepVZjBSeawAcbVd2l5DOYLGv6v1ODaVS4keVaec3 vtWhTSgBNXgXQpj45lvlkSC1WH3NuI4+rzx5xh8= X-Google-Smtp-Source: ACJfBosHbBM6d8T4zPKBGvPznkEkGta9+5n5p7ILOqiKghpfuqnVREUHs7LsZsv7sOpu4KHMsogKP/igFOnZQX96pkY= X-Received: by 10.36.151.198 with SMTP id k189mr2255617ite.100.1513668640509; Mon, 18 Dec 2017 23:30:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Mon, 18 Dec 2017 23:30:40 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Tue, 19 Dec 2017 15:30:40 +0800 Message-ID: Subject: Re: Canberra To: Sid Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Tue, 19 Dec 2017 07:30:41 -0000 On Tue, Dec 19, 2017 at 3:24 PM, Sid wrote: > > blubee blubeeme > > I am porting py-canberra which isn't required but an > > optional dependency for another port that I am working on. > > > I wonder should I leave it as is or make a dependency from this thing > you're working on instead? > > > blubee blubeeme > > py-canberra is just a python wrapper for libcanberra > > Perhaps audio/libcanberra should be a dependency of devel/pycanberra. > audio/libcanberra-gtk3 looks like it has options and requests for > unnecessary dependencies. > > > Sid > > Canberra is an audio application for playing simple sounds like "DING!". > > For playing sound, I am convinced that graphical dependencies for > audio/libcanberra and audio/libcanberra-gtk3 aren't needed: > x11-toolkits/gtk30, x11-toolkits/gtk20, accessibility/atk. > > According to Freshports, both libcanberra and libcanberra-gtk3 refer to > the file libcanberra-0.30.tar.xz of the same SHA256 and size. > > The difference between these two is one pulls in gtk3 as well. > > libcanberra-gtk3 also has options for pulseaudio, and gstreamer. > > > Pango is for left to right text, perhaps for displaying audio > information to the user. > > Its description is its "code is platform- and toolkit-independent." > > For it to display a simple banner or visual it shouldn't require heavy > graphical dependencies. > > Also, Pango should be made into an option for Canberra, so it can > definitely be compiled without atk, gtk30 or gtk20. > > Pango doesn't require these three graphical dependencies, so Canberra > especially shouldn't. > > > The port audio/freedesktop-sound-theme just has sound files, and no > libraries. > > pango and freedesktop-sound-themes should be options for libcanberra. > > I'm convinced that gtk30, gtk20, atk, pulseaudio, and gstreamer shouldn't > be options or required in libcanberra or libcanberra-gtk3. (pango and atk > are not in the Makefiles, but Freshports shows them.) > libcanberra-gtk3 should be merged back into libcanberra. I've only tested > removing all of these options for one port that asked for both canberra > libraries, and it compiled and played sound. > > > Thank you. > That's good to know and I should most likely be able to implement the same in py-canberra or leave it off all together. It's mostly used for python bindings into the gnome DE which might not be running, definitely not running in my use case. From owner-freebsd-ports@freebsd.org Tue Dec 19 07:32:56 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF516E9134B for ; Tue, 19 Dec 2017 07:32:56 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 915E46A8B9 for ; Tue, 19 Dec 2017 07:32:56 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=o3e1MpWC2l+Kds4VWebUQLF/uJx4x6+Y//z+iNiogT8=; b=CSp4oCdTj1Fj/g+wIAUODm2vAiJMnuQgcyL/mvAmN6Wq/w3syXD9leSCeJW1cubC8PKUQSsddmLP4MUGszho/Bs0AmMoweMRm1Qfp5+lKxODIlbT308yjoZ4a8ZFT5BvckxJ16N4DtL2sGiefAX4SdmYTHLiXcQeG/0PL+LYuSY=; Received: from paris.xoc.tele2net.at ([213.90.36.7]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1eRCOT-0007Al-8x for freebsd-ports@freebsd.org; Tue, 19 Dec 2017 08:32:53 +0100 Received: from 91-115-91-196.adsl.highway.telekom.at ([91.115.91.196] helo=[10.0.0.93]) by paris.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1eRCOT-0002MX-6M for freebsd-ports@freebsd.org; Tue, 19 Dec 2017 08:32:53 +0100 To: freebsd-ports@freebsd.org References: <00945d91-f273-3ac4-042d-e3eb504dd0e2@utanet.at> Subject: Re: devel/R-cran-gsubfn: broken because of missing dependency From: Walter Schwarzenfeld Message-ID: <091a2fea-870d-2088-e700-ec52efe5e919@utanet.at> Date: Tue, 19 Dec 2017 08:32:51 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <00945d91-f273-3ac4-042d-e3eb504dd0e2@utanet.at> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 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: Tue, 19 Dec 2017 07:32:56 -0000 On my system (with tcl/tk in math/R=on) no problem (10.4amd64). From owner-freebsd-ports@freebsd.org Tue Dec 19 09:26:27 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66352E99934 for ; Tue, 19 Dec 2017 09:26:27 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A3B56F0BB for ; Tue, 19 Dec 2017 09:26:27 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Tue, 19 Dec 2017 10:25:59 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1513675582; bh=Da/DxgnoOT9ZxaWCLt+b4jBQ92Mo+cYVuu0TUI3+Hz0=; h=Date:From:To:Subject:References:In-Reply-To; b=n51dA+Y5RGIYA5ozI0F5XwZ0iP8/7nLCY8ao1TFkCvmtNbpP6b4f+h0EknJVXsFZy mMybUBA+dZqcfXQ9hAESLIeoBO3gFCgBeRtVbBPcTshAvCKdLt84xz1vfbR5ox6kdb 27a393WXDHui+lh8eWxSdIemyRl3LEfqGVFnBavwC3ZsVzm9VJvFfl6F3uKcZHhcan DjPcPSUJpkAl+OSkv+RpdGE9niuhYSXdIZyGzTfujfx9pSMvLTCKaQ8be03TsdcNVp JefI5JYkwWgpfW6PxpXLN3spAfRS7EDBHOaKJtictn7MdV9gxalXlgg4mpVOXzytkt 4isZmHrD9Z08A== Message-ID: <20171219102559.Horde.AyGpeFFY29vx2tNY8v16f4u@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-ports@freebsd.org Subject: Re: OSS Audio References: <20171218171120.Horde.s5OngVFuRoftIluNHRvGOV6@webmail.leidinger.net> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_L8xRG9vGpacMtcrGnYjhSXs"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 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: Tue, 19 Dec 2017 09:26:27 -0000 This message is in MIME format and has been PGP signed. --=_L8xRG9vGpacMtcrGnYjhSXs Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting blubee blubeeme (from Tue, 19 Dec 2017=20=20 00:28:23=20+0800): > there's the alsa-lib from audio/alsa-lib > there's https://sourceforge.net/p/opensound/git/ci/master/tree/lib/libsal= sa/ > from oss that wraps alsa code, would there be issues with any of that in > the kernel? Yes there would be an issue. It doesn't belong into the kernel. It's=20=20 an=20userland library. It belongs into the userland (where it is right=20= =20 now)=20=3D /usr/local/lib or /usr/lib. And to answer the question which may come if it makes sense to include=20= =20 it=20into the FreeBSD basesystem (userland) instead of having it in the=20= =20 ports=20collection: right now (without any program in the FreeBSD base=20= =20 system)=20it doesn't make sense. If there is a program which makes use=20= =20 of=20alsa-lib which shall be imported into the FreeBSD basesystem (not=20= =20 discussing=20right now if such a program makes sense in the FreeBSD=20=20 basesystem=20as we don't have an explicit example to look at), then it=20= =20 makes=20sense. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_L8xRG9vGpacMtcrGnYjhSXs Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaONsnAAoJEKrxQhqFIICEgdIQAICttpIguCdx7nWNZCevVEbN Z43auBIn8lu+uAA7fJS0ciphGvdaDJGqYnOFdXmNOwIfP0lxTvC+D2ud4mSm+C1G wJ8FEU21zzaTPhIs7FT9zx69niGIebZVVkGq0oZQ/cWCrF8RMHqdmWt4z/0ddAHo 9a9fQvP2tIdHmpEbnEdlf0RvG0vBcLsAGZY5l1XcDHuSiLkhEZV/rVvHjzmDIRnc yoNuYSGwK1bBAlqsZR40dPImFtKl3X4bOuNqNroRXJ03xekRmESiWCfB1SUy/yJy gN01B+DK7OTbygKC2Op8INhMWqkKVpoJpAlubNBeG6E6Iml030fI/75p9uyHI8z+ nK/PMOHpT4PO0YhTtmWRKaVE+JQCrFyD0VwXk6lbYWw7iLI5+/cpgZz5v7fTnDJG 1zAHkSk6IEv4gihpvldSkk8u3kJtwUZSZTIuM+j5nppnPZD7ksri8TyYVDnIqWMG OrkQvk3/CXBZwNb142OgFczVC4sbpXHu2Q753f2JN9lHZQDe7TSJFbsLxh+7mV+z H9cdtacNeyFmvJ4GVWlAAIZPyWdOqRA2mgM98hGQwkmD+twEyHahjzv/GG3n0Tvu RHYT89EiEk1rPe4e8DdBMy5Vin0fOBA5kXUrxvIw+XIFxo+RVYBcNWxQ386Ro9hJ iPeJTLcO9+wXPPOTcgzw =NnIp -----END PGP SIGNATURE----- --=_L8xRG9vGpacMtcrGnYjhSXs-- From owner-freebsd-ports@freebsd.org Tue Dec 19 10:44:51 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C51EE9ED53 for ; Tue, 19 Dec 2017 10:44:51 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E58C572607 for ; Tue, 19 Dec 2017 10:44:50 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from [134.76.11.225] (helo=email.stud.uni-goettingen.de) by mailer.gwdg.de with esmtp (Exim 4.80) (envelope-from ) id 1eRFOB-0003in-VZ; Tue, 19 Dec 2017 11:44:47 +0100 Received: from UM-EXCHT-A02.um.gwdg.de (134.76.9.211) by um-excht-s1.um.gwdg.de (134.76.9.213) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 19 Dec 2017 11:44:47 +0100 Received: from pc028.nfv.nw-fva.de (134.76.242.1) by email.gwdg.de (134.76.9.211) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 19 Dec 2017 11:44:46 +0100 Subject: Re: devel/R-cran-gsubfn: broken because of missing dependency To: Walter Schwarzenfeld , References: <9fe24297-1969-6b93-5954-351dfa9306b7@gwdg.de> <00945d91-f273-3ac4-042d-e3eb504dd0e2@utanet.at> From: Rainer Hurling Message-ID: <4431c59f-6b4b-ba8d-44f8-99b78d365127@gwdg.de> Date: Tue, 19 Dec 2017 11:44:46 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <00945d91-f273-3ac4-042d-e3eb504dd0e2@utanet.at> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit X-Spam-Level: - X-Virus-Scanned: (clean) by clamav 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: Tue, 19 Dec 2017 10:44:51 -0000 Am 19.12.2017 um 08:21 schrieb Walter Schwarzenfeld: > Is in math/R the option tcl/tk=on? Hi Walter, I think, you are right. pkg-fallout[1] seems to have problems with building devel/R-cran-gsubfn, because default setting for math/R option 'TCLTK' is disabled. This have to be enabled by default, if the build of devel/R-cran-gsubfn should work automatically. Thanks for the pointer. [1] http://svnweb.freebsd.org/changeset/ports/456684 From owner-freebsd-ports@freebsd.org Tue Dec 19 11:06:51 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F38CE9FFCE for ; Tue, 19 Dec 2017 11:06:51 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from smtp.burggraben.net (smtp.burggraben.net [IPv6:2a01:4f8:140:50a2::3:1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "ns.exwg.net", Issuer "Christoph Moench-Tegeder" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 167B9731C3 for ; Tue, 19 Dec 2017 11:06:50 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from localhost (localhost [127.0.0.1]) by smtp.burggraben.net (Postfix) with ESMTP id DAE6E6002F0 for ; Tue, 19 Dec 2017 12:06:47 +0100 (CET) X-Spam-Scanned: by amavisd-new at exwg.net Received: from smtp.burggraben.net ([127.0.0.1]) by localhost (ns.burggraben.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWJAHoRjsdpA for ; Tue, 19 Dec 2017 12:06:36 +0100 (CET) Received: from elch.exwg.net (dslb-188-099-232-023.188.099.pools.vodafone-ip.de [188.99.232.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "elch.exwg.net", Issuer "Christoph Moench-Tegeder" (verified OK)) by smtp.burggraben.net (Postfix) with ESMTPS for ; Tue, 19 Dec 2017 12:06:36 +0100 (CET) Received: by elch.exwg.net (Postfix, from userid 1000) id 93C7630211; Tue, 19 Dec 2017 12:06:35 +0100 (CET) Date: Tue, 19 Dec 2017 12:06:35 +0100 From: Christoph Moench-Tegeder To: freebsd-ports@freebsd.org Subject: Re: Procmail got updated! Message-ID: <20171219110635.GA1793@elch.exwg.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) 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: Tue, 19 Dec 2017 11:06:51 -0000 ## Matthias Andree (matthias.andree@gmx.de): > Sunpoet, can we mark the port as deprecated given that even the upstream > once said it should best be abolished? I can't find the reference now, Here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769938#11 https://marc.info/?l=openbsd-ports&m=141634350915839&w=2 Regards, Christoph -- Spare Space From owner-freebsd-ports@freebsd.org Tue Dec 19 12:22:21 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 193E1EA4FE5 for ; Tue, 19 Dec 2017 12:22:21 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id F0F6376103 for ; Tue, 19 Dec 2017 12:22:20 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id F0664EA4FE3; Tue, 19 Dec 2017 12:22:20 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F01A1EA4FE2 for ; Tue, 19 Dec 2017 12:22:20 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E12F076101 for ; Tue, 19 Dec 2017 12:22:20 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id vBJCMKbo061077 for ; Tue, 19 Dec 2017 12:22:20 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id vBJCMKaB061075; Tue, 19 Dec 2017 12:22:20 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201712191222.vBJCMKaB061075@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Tue, 19 Dec 2017 12:22:20 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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: Tue, 19 Dec 2017 12:22:21 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ astro/py-pyfits | 3.4 | 3.5 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Tue Dec 19 16:47:35 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C59E4E8F55C for ; Tue, 19 Dec 2017 16:47:35 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [209.237.23.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B9AA680E27 for ; Tue, 19 Dec 2017 16:47:35 +0000 (UTC) (envelope-from marquis@roble.com) Received: from roble.com (roble.com [209.237.23.50]) by mx5.roble.com (Postfix) with ESMTP id A7BBF4B496 for ; Tue, 19 Dec 2017 08:47:28 -0800 (PST) Date: Tue, 19 Dec 2017 08:47:28 -0800 (PST) From: Roger Marquis To: freebsd-ports@freebsd.org Subject: Re: Procmail got updated! Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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: Tue, 19 Dec 2017 16:47:35 -0000 > As one of the "irresponsible" people who is still using procmail on our > systems and has built an number of scripts and customer infrastructure > around it I take exception to the term irresponsible. Perhaps the better > word is overworked. If I had the time to move to dovecot/sieve or maildrop > as a local delivery agent I would have done so by now. Can certainly sympathize depending on the threat model, but how is that any different from Equifax' not having time to patch Struts or not having time to change the oil in your car or to brush your teeth ... Roger From owner-freebsd-ports@freebsd.org Tue Dec 19 17:13:37 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4042EE913A9 for ; Tue, 19 Dec 2017 17:13:37 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0605B13AD for ; Tue, 19 Dec 2017 17:13:37 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id t1so3557685ite.5 for ; Tue, 19 Dec 2017 09:13:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EKTJQuLGgLx/jUGU1OOIxqxexOzhBa+Z+aMUBEtKXuI=; b=s0PYvKHLPDNG2I5hbY8p+7WR7H/v/J0zeVWLcLfsOJOFJxdv15L9Wf+GH3DClE1C0X JTnwGk8q1F2A/KHZmvmxet6ckTegmQhCKzhqpBUMuEz69BNN0jQyISiv86ZuzpUy13o4 Ivt0FbYUs7XDcVM7O+YiEK68dF3AvMM59/GSb6Gc9TLyfZ370VW0YqGUJ99MWFV7wzCy 7INkz+LtaCjI3dkdm24CSVeGrCE8vRHdqBkr/qGM/TD9ibPzhMkfHpwEM7jeHKgzkBGd NWYt0dvWiTR9Gi9KBcRo0K80TtZOeqzRUuKhb3LbqZkoE1KBhrAydLXQ+6PSAEWAsIbw Altw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EKTJQuLGgLx/jUGU1OOIxqxexOzhBa+Z+aMUBEtKXuI=; b=n4t70NgqbUusuR18d79IW/vpcAQIIaPN/K2DjBh96k5QTCElYtCnQWpUdMkJWs2uEO cL3k8Y6ocJVw6BK96/FGDlv98G8xOLjPzrYuIarpJyhZWUMKUGFc9spHVfRMe5knFcRC NjuULyByXOTjVTmgvI+O+v3oUBjw5ryFan6d2wh734owxzJrS3RWbH5fP3WjugZ1JaJc adkpBfSOOCt4xIACJ1rhOgYgYH9odyI4RT9fL5XPig5W2OatHEmT4oZjrO6HNUpahVgj qbzPHs17yA9CM1YKNC6A+UJJm4J2t5XYw1Hn2SAYn5JBbAeUerpeUF10pQH9Qytyv4aH RZhg== X-Gm-Message-State: AKGB3mIfTHKwqvQXrOABUM8j4JGanMHB6hKazZcitlSo4ySascOwXmBZ XiTi3l/p01e/efEw+41K2//ZoxnuhPglPyDCAvdOPA== X-Google-Smtp-Source: ACJfBouBDqCOeFFOg1mVVvvqs6h5mKOF3o65KUUFMYBFvJ1LMIy7tjus7L6n/K8Ui3bTDnlcQyU/C+BhyEamb7UkYC4= X-Received: by 10.36.103.213 with SMTP id u204mr3997158itc.91.1513703616369; Tue, 19 Dec 2017 09:13:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.180.34 with HTTP; Tue, 19 Dec 2017 09:13:35 -0800 (PST) In-Reply-To: References: From: Adam Vande More Date: Tue, 19 Dec 2017 11:13:35 -0600 Message-ID: Subject: Re: Procmail got updated! To: Roger Marquis Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Tue, 19 Dec 2017 17:13:37 -0000 On Tue, Dec 19, 2017 at 10:47 AM, Roger Marquis wrote: > As one of the "irresponsible" people who is still using procmail on our >> systems and has built an number of scripts and customer infrastructure >> around it I take exception to the term irresponsible. Perhaps the better >> word is overworked. If I had the time to move to dovecot/sieve or maildrop >> as a local delivery agent I would have done so by now. >> > > Can certainly sympathize depending on the threat model, but how is that > any different from Equifax' not having time to patch Struts or not > having time to change the oil in your car or to brush your teeth ... > That's a non-sequitur if I understand the response correctly. Procmail IS patched and I assume applied. So yes mom, teeth are brushed. https://svnweb.freebsd.org/ports/head/mail/procmail/files/patch-src-formisc.c?view=log -- Adam From owner-freebsd-ports@freebsd.org Tue Dec 19 17:26:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09457E92207 for ; Tue, 19 Dec 2017 17:26:49 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [209.237.23.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EFCF61DCC for ; Tue, 19 Dec 2017 17:26:48 +0000 (UTC) (envelope-from marquis@roble.com) Received: from roble.com (roble.com [209.237.23.50]) by mx5.roble.com (Postfix) with ESMTP id 9E5384B5CA; Tue, 19 Dec 2017 09:26:47 -0800 (PST) Date: Tue, 19 Dec 2017 09:26:47 -0800 (PST) From: Roger Marquis To: Adam Vande More cc: FreeBSD Ports Subject: Re: Procmail got updated! In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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: Tue, 19 Dec 2017 17:26:49 -0000 >> Can certainly sympathize depending on the threat model, but how is that >> any different from Equifax' not having time to patch Struts or not >> having time to change the oil in your car or to brush your teeth ... > > That's a non-sequitur if I understand the response correctly. Procmail IS > patched and I assume applied. So yes mom, teeth are brushed. Correct from a 'known risk only' perspective but isn't code that is a) largely unauditable and b) hasn't been maintained for a long time considered vulnerable regardless of published vulnerabilities? Perhaps not unlike brushing your teeth only when the dentist finds a cavity, it doesn't fundamentally change the risk model. Roger From owner-freebsd-ports@freebsd.org Tue Dec 19 17:43:50 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFC0AE93191 for ; Tue, 19 Dec 2017 17:43:50 +0000 (UTC) (envelope-from lbartoletti@tuxfamily.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B9D25289A for ; Tue, 19 Dec 2017 17:43:50 +0000 (UTC) (envelope-from lbartoletti@tuxfamily.org) Received: by mailman.ysv.freebsd.org (Postfix) id B6524E93190; Tue, 19 Dec 2017 17:43:50 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5F86E9318F for ; Tue, 19 Dec 2017 17:43:50 +0000 (UTC) (envelope-from lbartoletti@tuxfamily.org) Received: from smtp.smtpout.orange.fr (smtp07.smtpout.orange.fr [80.12.242.129]) by mx1.freebsd.org (Postfix) with ESMTP id 598A72898 for ; Tue, 19 Dec 2017 17:43:49 +0000 (UTC) (envelope-from lbartoletti@tuxfamily.org) Received: from [192.168.1.14] ([86.200.249.99]) by mwinf5d14 with ME id ntc81w00G29RLba03tc8AX; Tue, 19 Dec 2017 18:36:10 +0100 X-ME-Helo: [192.168.1.14] X-ME-Auth: YmFydG9sZXR0aS5sb2ljQG9yYW5nZS5mcg== X-ME-Date: Tue, 19 Dec 2017 18:36:10 +0100 X-ME-IP: 86.200.249.99 Subject: Re: pkg flavors breaks "make run-depends-list" To: Stefan Esser , Lbartoletti , Mathieu Arnold , jamie@thompson.dyslexicfish.net, ports@freebsd.org References: <5a211e3f.75a86.3b51aeec@thompson.dyslexicfish.net> <92e85df7-bc3f-09ae-4dba-238dcdcd9d5e@FreeBSD.org> <20171201123253.5361749.79318.12678@tuxfamily.org> <99fda0c0-1c9e-0803-4f60-f068fbce8acd@tuxfamily.org> From: "L.Bartoletti" Message-ID: <2a62c1c4-d77f-c9d2-03bf-a9efd4e28e9d@tuxfamily.org> Date: Tue, 19 Dec 2017 18:36:07 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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: Tue, 19 Dec 2017 17:43:50 -0000 Thanks Stefan, I will try it! Regards Loïc On 19.12.2017 07:23, Stefan Esser wrote: > Am 18.12.17 um 23:34 schrieb lb: >> Hi, >> >> Is it possible to add the flavors into the name returned by build-depends-list? >> >> An example: >> >> Loic@FreeBSD:/usr/ports|⇒  make -C x11-toolkits/py-qt5-gui build-depends-list >> FLAVOR=py36 >> /usr/ports/ports-mgmt/pkg >> /usr/ports/lang/python36 >> /usr/ports/devel/py-sip >> ... >> >> Should be /usr/ports/devel/py-sip@py36 > I have already proposed the same (with patch), see > > https://reviews.freebsd.org/D13535 > > You can download the patch for testing from: > > https://reviews.freebsd.org/D13535?download=true > > Regards, STefan > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Tue Dec 19 18:04:07 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AE20E946BB for ; Tue, 19 Dec 2017 18:04:07 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 80ED6376F; Tue, 19 Dec 2017 18:04:05 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.101.158]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MGEv5-1eFY8F0iQx-00FAtq; Tue, 19 Dec 2017 19:03:04 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id DF5A123D416; Tue, 19 Dec 2017 19:03:00 +0100 (CET) Subject: Re: Procmail got updated! To: Ted Hatfield , freebsd-ports@freebsd.org, Eugene Grosbein Cc: Sunpoet Po-Chuan Hsieh References: From: Matthias Andree Message-ID: Date: Tue, 19 Dec 2017 19:03:00 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE X-Provags-ID: V03:K0:E26v0DNTYAuEUfPEb+WHX1dJ2WHznzC75Na3ZgbbC9wHUezlLVm ZQ6hcM+d7BtRE+iUVuPBIREnPsyC78zbcJ/3lBmzgixZcx3mMifSKbUQVJFVoOo8GafvKYl J7I4O6fut0mHavmGf65P2OerWHUdL6zntDEN1MZ08/cf4b5730QhLXb4AQE4DNLLYmq3O3g TSxNLMeLEa0MICNm3D3DA== X-UI-Out-Filterresults: notjunk:1;V01:K0:4VwiUJnhC+U=:JYbhzMHkzhazo/eVVOpb9f NjWwXQML8jZc7GAA0PfI6XWxldQAbtyOgYzER9hlOUg+kxuvCJQfjz+e24+r6rP+kGx8JDiow A2us/wwvq/5MeXSkfyggsKC9DMnccFPkih6xS+zpVEZAxAyQ7hzNtadhsltEkYzYpH0hQbHLM brTiRakCIKW3DzYG1vsS7bpnEszmKL0QpAn2rvQzMJQj4uyGfkBvlWI5cT19P9za/iuVbUoPe R0PesS/Rp4AcIiC4X9OrgtcNr3xFzpc39qlVPI+N63bvTtMELX+IMCJkBcUsQ6EkwxEng0NIw DNBuYUrJOB8A1JFxht4YSIks6S8oki+iHC6Eb0ncUsY6nVkPhc5ZE8C58l78/aTT7OMFRVJcT ymh0jsDi+aOEStYYI3fOpYfZQRS2J9yOibPi1a4Seg7/AApD5dHnocxA3ybAjQDousEIrsGje YYe5D4NThn/CFi5gxH6sfNMHP88XRnbIRrI+K/DLHulKA9or/jXk9rIw9adaEWDzzFwSi9duf aj5YTA8saldWCev56hT8i/swB9ZS3HSOol93DTemf2XU1XPDQjIs45j+hPBrXxkbUmWqGID7n BX3eW8auarWOqQs/st8+5h68skAucfDU7DcbaM0BKNXyXywjg1EcfiBXFCxSIRB/RejyGTB9X PaXHVSzN1EWL1i1WrJ9Hdxb2X34AHMAWELLhLQx15dOLJvy1CaHt+oWX+B2ZM92bvbppC/7VR 9EOgrvuik06YlfuxvAWxHDGcmDSgpt6iJxL1xnK/CLXXhiAHcJXAI+zEER9C6eDwffQFy7JXO xHpx1GLf63i2ZZNo1fGcxHkLNQUXXiLPx6GSCy4/tIc2w0wbwQ= 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: Tue, 19 Dec 2017 18:04:07 -0000 Am 19.12.2017 um 01:30 schrieb Ted Hatfield: > > > On Mon, 18 Dec 2017, Matthias Andree wrote: > >> Am 18.12.2017 um 00:17 schrieb Dave Horsfall: >>> Doing my regular update, and... >>> >>> =C2=A0=C2=A0=C2=A0 Upgrading procmail from 3.22_9 to 3.22_10... >>> >>> Good grief; who's the masochist who volunteered to support this >>> obscure insecure and hitherto-unsupported scripting language? >>> >> https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D455800 >> >> I'd agree we should pull the plug on the package. We'll be in for the >> usual "but it works for me" screaming of the irresponsible people who >> don't care (and most of them won't know that they need to write the >> exception/error handling themselves in their .procmailrc recipes). >> >> Sunpoet, can we mark the port as deprecated given that even the upstre= am >> once said it should best be abolished? I can't find the reference now,= >> the procmail.org website displays "Site hosting in transit, informatio= n >> will be back up shortly." >> > > Dear Matthias, > > As one of the "irresponsible" people who is still using procmail on > our systems and has built an number of scripts and customer > infrastructure around it I take exception to the term irresponsible.=C2= =A0 > Perhaps the better word is overworked.=C2=A0 If I had the time to move = to > dovecot/sieve or maildrop as a local delivery agent I would have done > so by now. > > Ted Hatfield Dear Ted, Eugene, I think if the procmail language were a bit more "regular", someone would have written converter scripts long ago by now. Other than that, I find it hard to believe that people don't have time for over x in [3; 17] years to migrate, which in many cases would in my book be more a situation of "I don't want to..." rather than "I am unable to...". I don't mean to judge your situation, just that to me it looks a matter that you have not yet found it important enough to bother.= Given that the former maintainer asked OpenBSD to pull the plug on the port already 37 months ago (see here ) after findings from fuzzing, and now to see security updates to a defunct upstream port, I don't think we should keep the port around for much longer. The expiration I was proposing isn't "axe it out now", we would not normally do that, and it's at the maintainer's (i. e. sunpoet@'s) discretion what expiration date, if any, will be set. But the question if we as downstream packagers/providers want to step in for a package abolished by the upstream almost a generation ago, is one that needs serious consideration. I wouldn't endorse that the project waste time on decrepit ports for which decent alternatives exist. Best, Matthias From owner-freebsd-ports@freebsd.org Tue Dec 19 19:40:52 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85D76E9AF7E for ; Tue, 19 Dec 2017 19:40:52 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.io-tx.com", Issuer "AlphaSSL CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 51F4C67CFF; Tue, 19 Dec 2017 19:40:52 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (authenticated bits=0) by io-tx.com (8.15.2/8.15.2) with ESMTPSA id vBJJejdo018778 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Dec 2017 13:40:46 -0600 (CST) (envelope-from ted@io-tx.com) Date: Tue, 19 Dec 2017 13:40:45 -0600 (CST) From: Ted Hatfield To: Matthias Andree cc: freebsd-ports@freebsd.org, Eugene Grosbein , Sunpoet Po-Chuan Hsieh Subject: Re: Procmail got updated! In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-ID: X-Virus-Scanned: clamav-milter 0.99.2 at io-tx.com X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=5.0 on io-tx.com tests=ALL_TRUSTED, AWL, T_RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 user=root X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on io-tx.com Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Tue, 19 Dec 2017 19:40:52 -0000 On Tue, 19 Dec 2017, Matthias Andree wrote: > Am 19.12.2017 um 01:30 schrieb Ted Hatfield: >> >> >> On Mon, 18 Dec 2017, Matthias Andree wrote: >> >>> Am 18.12.2017 um 00:17 schrieb Dave Horsfall: >>>> Doing my regular update, and... >>>> >>>>     Upgrading procmail from 3.22_9 to 3.22_10... >>>> >>>> Good grief; who's the masochist who volunteered to support this >>>> obscure insecure and hitherto-unsupported scripting language? >>>> >>> https://svnweb.freebsd.org/ports?view=revision&revision=455800 >>> >>> I'd agree we should pull the plug on the package. We'll be in for the >>> usual "but it works for me" screaming of the irresponsible people who >>> don't care (and most of them won't know that they need to write the >>> exception/error handling themselves in their .procmailrc recipes). >>> >>> Sunpoet, can we mark the port as deprecated given that even the upstream >>> once said it should best be abolished? I can't find the reference now, >>> the procmail.org website displays "Site hosting in transit, information >>> will be back up shortly." >>> >> >> Dear Matthias, >> >> As one of the "irresponsible" people who is still using procmail on >> our systems and has built an number of scripts and customer >> infrastructure around it I take exception to the term irresponsible.  >> Perhaps the better word is overworked.  If I had the time to move to >> dovecot/sieve or maildrop as a local delivery agent I would have done >> so by now. >> >> Ted Hatfield > > Dear Ted, Eugene, > > I think if the procmail language were a bit more "regular", someone > would have written converter scripts long ago by now. > > Other than that, I find it hard to believe that people don't have time > for over x in [3; 17] years to migrate, which in many cases would in my > book be more a situation of "I don't want to..." rather than "I am > unable to...". I don't mean to judge your situation, just that to me it > looks a matter that you have not yet found it important enough to bother. > > Given that the former maintainer asked OpenBSD to pull the plug on the > port already 37 months ago (see here > ) after > findings from fuzzing, and now to see security updates to a defunct > upstream port, I don't think we should keep the port around for much > longer. The expiration I was proposing isn't "axe it out now", we would > not normally do that, and it's at the maintainer's (i. e. sunpoet@'s) > discretion what expiration date, if any, will be set. > > But the question if we as downstream packagers/providers want to step in > for a package abolished by the upstream almost a generation ago, is one > that needs serious consideration. I wouldn't endorse that the project > waste time on decrepit ports for which decent alternatives exist. > > > Best, > Matthias > Matthias, My response wasn't meant to disprove your argument. There is a valid case behind dropping support for procmail and you are welcome to make that argument. >From my point of view (and I bet quite a few others) I've been using a software product provided by the port maintainers for quite a long time. During that time I've kept my software up to date and patched. As far as I am concerned I've done my due dilligence. If you want to make an argument against maintaining procmail I completely understand that. I just don't think that denigrating others while making your argument is the way to go about it. Ted Hatfield From owner-freebsd-ports@freebsd.org Tue Dec 19 19:48:48 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 689E1E9B7C3 for ; Tue, 19 Dec 2017 19:48:48 +0000 (UTC) (envelope-from lbartoletti@tuxfamily.org) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D64036836E for ; Tue, 19 Dec 2017 19:48:46 +0000 (UTC) (envelope-from lbartoletti@tuxfamily.org) Received: from [192.168.1.14] ([86.200.249.99]) by mwinf5d62 with ME id nvoc1w00N29RLba03vocJE; Tue, 19 Dec 2017 20:48:38 +0100 X-ME-Helo: [192.168.1.14] X-ME-Auth: YmFydG9sZXR0aS5sb2ljQG9yYW5nZS5mcg== X-ME-Date: Tue, 19 Dec 2017 20:48:38 +0100 X-ME-IP: 86.200.249.99 Subject: Re: FLAVOR for Qt4 and Qt5 (was Re: Flavor or not for this port?) From: "L.Bartoletti" To: Rainer Hurling Cc: freebsd-ports@freebsd.org References: <46cbd287-186f-9b92-f2a7-d6884c681040@gwdg.de> <37d007c1-0315-5b23-7357-5dc3fcb836fc@gwdg.de> <92d09009-64b3-695a-2282-5acb6ab169f0@tuxfamily.org> Message-ID: Date: Tue, 19 Dec 2017 20:48:36 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <92d09009-64b3-695a-2282-5acb6ab169f0@tuxfamily.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: fr-FR 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: Tue, 19 Dec 2017 19:48:48 -0000 Hi, Here's my WIP https://gitlab.com/lbartoletti/freebsd_ports/tree/master/qwt6 Regards On 18.12.2017 22:57, L.Bartoletti wrote: > Hi Rainer, > > I have made a try with subpackages with success, but I think it's > better with flavor (like on OpenBSD). > > So, I have started to create flavors for this port. > > For now, I success for qt4 but not yet for qt5. > > Extract from my Makefile in progress: > > FLAVORS=    qt5 qt4 > FLAVOR?= > > .if ${FLAVOR:Mqt5} > PKGNAMESUFFIX=    -qt5 > USE_QT5=    widgets gui core designer gui opengl svg xml buildtools > printsupport concurrent > PLIST=        ${PKGDIR}/pkg-plist.qt5 > PLIST_SUB+=    QT_MKSPECDIR=lib/qt5/mkspecs > DOCSDIR=    ${PREFIX}/share/doc/qwt6-qt5 > .else > PKGNAMESUFFIX=    -qt4 > USE_QT4=     corelib gui opengl svg xml moc_build > PLIST=        ${PKGDIR}/pkg-plist.qt4 > PLIST_SUB+=    QT_MKSPECDIR=lib/qt4/mkspecs > DOCSDIR=    ${PREFIX}/share/doc/qwt6-qt4 > .endif > > Ther error for qt5: > > qwt-qt5-6.1.3 can't be installed: different Qt versions specified via > USE_QT[4 5]. > > Regards. > > On 17.12.2017 10:12, Rainer Hurling wrote: >> Am 02.11.2017 um 07:41 schrieb Rainer Hurling: >>> Am 02.11.2017 um 07:13 schrieb L.Bartoletti: >>>> Hi, >>>> >>>> I want to take x11-toolkits/qwt{5,6}-* >>>> >>>> Both are built for Qt4. I especially need qwt6 for Qt5. Since we have >>>> flavors. Is it better to add a Qt5 flavor for Qwt6 or simply add a >>>> x11-toolkits/qwt6-qt5 (like security/qtkeychain-qt{4,5} ?) >>>> >>>> Thanks. >>>> >>>> Regards. >>>> >>>> Loïc >>> >>> Hi Loïc, >>> >>> Thanks for your dedication. I am very interested in a qwt6-qt5 port, >>> since it is needed for the upcoming version 3.0 of graphics/qgis :) >>> >>> Sorry for my inexperience. In case of adding the qwt6-qt5 as a flavor, >>> should we expect any change or restriction in the way, it would be used >>> as a dependency of e.g. QGIS? >>> >>> Thanks for any answer. >>> >>> Best wishes, >>> Rainer >> Hi Loïc, >> >> Again about x11-toolkits/qwt{5,6}-* >> >> Now, that we have our first real world experiences with FLAVORS, it >> seems to be functional to use flavors in this context. Something like >> >> x11-toolkits/qwt6@qt4 >> x11-toolkits/qwt6@qt5 >> >> A bit tricky could be, that USE_QT* are different in both cases: >> >> USE_QT4= corelib gui opengl svg xml moc_build >> USE_QT5= core gui opengl svg xml printsupport qmake_build widgets >> >> What do you think? >> >> Best wishes, >> Rainer >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Tue Dec 19 21:31:19 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2F87EA18B1 for ; Tue, 19 Dec 2017 21:31:19 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-100.reflexion.net [208.70.210.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6FFD06C401 for ; Tue, 19 Dec 2017 21:31:18 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 28768 invoked from network); 19 Dec 2017 21:31:12 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 19 Dec 2017 21:31:12 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Tue, 19 Dec 2017 16:31:12 -0500 (EST) Received: (qmail 30184 invoked from network); 19 Dec 2017 21:31:12 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 19 Dec 2017 21:31:12 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 89B0BEC922F; Tue, 19 Dec 2017 13:31:11 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: rpi2 V1.1 vs. hard coded max_execution_time figures in /usr/local/share/poudriere/common.sh (package; also: extract, install, deinstall) Message-Id: Date: Tue, 19 Dec 2017 13:31:10 -0800 To: Bryan Drewery , Freebsd-arm , FreeBSD Ports X-Mailer: Apple Mail (2.3273) 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: Tue, 19 Dec 2017 21:31:19 -0000 I tied building devel/llvm50 on a rpi2 V1.1 via poudriere and it got as far as: . . . =================================================== ===> Building package for llvm50-5.0.0_6 =>> Killing timed out build after 7200 seconds This was for: ---Begin OPTIONS List--- ===> The following configuration options are available for llvm50-5.0.0_6: CLANG=on: Build clang DOCS=on: Build and/or install documentation EXTRAS=on: Extra clang tools LIT=on: Install lit and FileCheck test tools LLD=on: Install lld, the LLVM linker LLDB=on: Install lldb, the LLVM debugger But I had set in /usr/local/etc/poudriere.conf : # This defines the max time (in seconds) that a command may run for a build # before it is killed for taking too long. Default: 86400 #MAX_EXECUTION_TIME=86400 MAX_EXECUTION_TIME=432000 # This defines the time (in seconds) before a command is considered to # be in a runaway state for having no output on stdout. Default: 7200 #NOHANG_TIME=7200 NOHANG_TIME=28800 The magic 7200 is from /usr/local/share/poudriere/common.sh : package) max_execution_time=7200 . . . There is also a lack of control over: extract) max_execution_time=3600 . . . install) max_execution_time=3600 . . . deinstall) max_execution_time=3600 . . . The rpi2 is now busy constructing a bsdtar when it could have had a llvm50 package. (I wonder if the bsdtar takes less time than the package would have taken.) As stands the only way to allow such large builds on the rpi2 is to edit: /usr/local/share/poudriere/common.sh after each poudriere installation/update. The following large things did manage to build packages: lang/gcc7 devel/cmake (indirect from selecting devel/llvm50) (I avoid WITH_DEBUG for devel/llvm50 in all environments: that build is massive, needing between 24 GiBytes and 26 GiBytes for RAM+SWAP on a powerpc64, if I remember right.) Other than the hard coded max_execution_time examples I've no found any fundmental problems with using poudriere when configured as indicated below. (Being willing to give it the time it needed.) For these experiments I've used: NO_ZFS=yes USE_TMPFS=no PARALLEL_JOBS=1 ALLOW_MAKE_JOBS=yes MAX_EXECUTION_TIME=432000 NOHANG_TIME=28800 For what I tried I've not had to use MAKE_JOBS_NUMBER_LIMIT?= or MAKE_JOBS_NUMBER?= . (Say, in /usr/local/etc/poudriere.d/make.conf testing the likes of .if ${.CURDIR:M*/devel/llvm*} code.) The rpi2 has world, kernel, and its dtb file via a USB SSD Stick, not from a usdcard. The usdcard is very minimal as far as its UFS / file system goes: /etc/fstab (redirecting to the USB SSD) /boot/* (with /boot/kernel/ empty and /boot/dtb/ empty) The USB SSD stick has: # df -m Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/da0p1 195378 31305 148443 17% / devfs 0 0 0 100% /dev (/dev/da0p1 has a UFS file system.) # swapinfo Device 1K-blocks Used Avail Capacity /dev/da0p2 1572864 16876 1555988 1% === Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Wed Dec 20 01:20:36 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A324E887C1 for ; Wed, 20 Dec 2017 01:20:36 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1740E74DDB for ; Wed, 20 Dec 2017 01:20:36 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=Xus0Hzd0K4nqYxUHNNwIFe7roYPqfnKkTRNweBkCWjc=; b=KjX8McGMk5Ittp0/5TVaJLvSKbILejLmkvy/ePnfrPDMh50l6iTpSJhV48GdTRdhcsxvjHHikJfXLik14I3mx5aMEVBa2p7XJg/qdQAJuqS8XG++57VOruHJBW07jH7aRshGO7vLP9ofWh6Ma34+lSWae2zJu2v8O2AHrhHkXtk=; Received: from plenty.xoc.tele2net.at ([213.90.36.8]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1eRT3i-00046M-4V for freebsd-ports@freebsd.org; Wed, 20 Dec 2017 02:20:34 +0100 Received: from 194-96-164-234.adsl.highway.telekom.at ([194.96.164.234] helo=[10.0.0.93]) by plenty.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1eRT3i-00020z-1u for freebsd-ports@freebsd.org; Wed, 20 Dec 2017 02:20:34 +0100 To: freebsd-ports@freebsd.org References: <4431c59f-6b4b-ba8d-44f8-99b78d365127@gwdg.de> Subject: Re: devel/R-cran-gsubfn: broken because of missing dependency From: Walter Schwarzenfeld Message-ID: Date: Wed, 20 Dec 2017 02:20:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <4431c59f-6b4b-ba8d-44f8-99b78d365127@gwdg.de> Content-Language: en-US X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 01:20:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224472 From owner-freebsd-ports@freebsd.org Wed Dec 20 05:28:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86945E95ACC for ; Wed, 20 Dec 2017 05:28:18 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from disroot.org (bs-one.disroot.org [178.21.23.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DE7B7D969 for ; Wed, 20 Dec 2017 05:28:17 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 81BE22A3CB for ; Wed, 20 Dec 2017 06:20:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1513747215; bh=EPX7iO702LgwaEarbjCpW/k6Wy2SLPPQcKNfJK7/E8k=; h=Date:From:Subject:To; b=vxEQJLJTHAaN+xc6Undl+7YeX8jUTIu2nHKz4J2tCfyCPIlbkjhWmdXTx2d1ozTic hLfLcVoVfqtCiVpCLC1oprT4xpriZg79NYT3LMTEtdNV8GrljOLOrI8ymvseNTXMGf Xaz+aesqIKrdm1Y8y+EPoJiOGw/DhtUO+zWxibQc= X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpmRFpvFP1ZA for ; Wed, 20 Dec 2017 06:20:13 +0100 (CET) Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1513747213; bh=EPX7iO702LgwaEarbjCpW/k6Wy2SLPPQcKNfJK7/E8k=; h=Date:From:Subject:To; b=gMxBPL3n16IEXguNMX0rT1UhwZzYtiupZ3Qv7h5YgTzgDt+tCUip96ZcFOYy1WQMP FclxhSR1+Bm96tlAhxB1HkfQZIpKU4ePxl6xYsPjuYG9xQpRVfrb3Si1KVN1n9utvV MaXWO7jxlmSnxbvPDS25sro/9rl41bLkSSQV4Do8= Date: Wed, 20 Dec 2017 05:20:13 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: "emilia" Message-ID: Subject: Xorg server update To: freebsd-ports@freebsd.org 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: Wed, 20 Dec 2017 05:28:18 -0000 Hello there, some time ago i saw a patch mentioned on a FreeBSD mailing l= ist to update the X11 server.=0AIf I remember correclty it would automati= cally handle new device nodes in /dev/input/,=0Athis would be a real cool= feature because e.g wacom tablets that use webcamd could 'just work' wit= hout X11 configs needed.=0ADoes anyone have some info what happend to the= patch?=0A=0A=0Aregards,=0Aemilia From owner-freebsd-ports@freebsd.org Wed Dec 20 05:40:42 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C93B8E9650D for ; Wed, 20 Dec 2017 05:40:42 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE1FD7DEA3; Wed, 20 Dec 2017 05:40:41 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBK5eTco097130 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 20 Dec 2017 06:40:29 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: matthias.andree@gmx.de Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id vBK5ePU0017449; Wed, 20 Dec 2017 12:40:25 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Procmail got updated! To: Matthias Andree , Ted Hatfield , freebsd-ports@freebsd.org References: Cc: Sunpoet Po-Chuan Hsieh From: Eugene Grosbein Message-ID: <5A39F7C9.1030800@grosbein.net> Date: Wed, 20 Dec 2017 12:40:25 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_Q_PLUS autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_Q_PLUS Date: is over 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** 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: Wed, 20 Dec 2017 05:40:42 -0000 On 20.12.2017 01:03, Matthias Andree wrote: > Dear Ted, Eugene, [skip] What happened with old good "Tools, not policy" thing? From owner-freebsd-ports@freebsd.org Wed Dec 20 07:04:08 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BCEBE9A70E for ; Wed, 20 Dec 2017 07:04:08 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ED5FC80A9C for ; Wed, 20 Dec 2017 07:04:07 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa08.server.lan (via HTTP); Wed, 20 Dec 2017 08:04:00 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: freebsd-ports@freebsd.org Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Wed, 20 Dec 2017 08:04:00 +0100 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:f/6vLXXfvtK0cX6Vbihc+m0bUaAUVaSjhdUW+Y3kLI3 PN8jr3AdqiRMXwTtsqXgsM2fL48PaNL7kd0iOpdWFab+u2Qi/H 6cSq8MLcbKHf16qqxaGCxmwOziTOZWkcZlfu8IykGreqJRtgMb LMZBquN5XvcXs04HbbxfJHgMOocbEBWe9+ac7ileoyNrkh55jp 0i+nc/cD8J4XYj/Rgoy30YoV3SNEyIuz/P7Oz2ejStT0JTNjRK ja32jzc/mrgM5TV567fiss42AVRnToaJV8bALzt5qWtJ6JwgSZ uYZTlE= X-UI-Out-Filterresults: notjunk:1;V01:K0:JLBGeZ8dbIw=:O8SgtGdkeeItRQoHk/b2V4 R4XyP77hl6RmIGtYbDo2vzzTwNEi9PeXCAKz6QebprLtKgsA6FHjcwfHfRqgdN6xR0gB/UjUe 8eDbfBqt55oICkf9Ll2RcXMm3P+9wkUOoqVEoKZtVQxxLVGJ4nDriHh7VxeUwHm0++7ip4/j8 u4GlYoby8cl+jQPXsVd4d5YNH/GZsptw3v9q6Ujn0J7GAbXI8cV1HCHc9ElU0y7vMT6B2Oz2N 7C6k3UZVlDYA6hKnqar0+PWqk6jVpn96watthP0KqXAmoJtiHBa7u9n3ZCwpLt7HosLTz6/iT FS/4CMRMM9iiD1tOwyCHKcvswZ1MDHf1Eoe3WKgjAykeqifNFNjSB0u2FeqxVHM4trGVzf+yU 2XoBZtKz9tKPsFnH6FsxaXjmSKikWQzgDL1wNQIAMd/+uYCYl78ywNKWwpmnUB/W2M45gT1vc tYQxBYx+Q8G06E15vh/hnoNmbug2EUDGiQ2IQbyyMOxxcwX4q3WH9xNCgqRhhoCC/c1JI0CNP BBtGO0dmCP76OtI4BGMBywOs0Gv3ZG5qEhdDzsAZ/WO 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: Wed, 20 Dec 2017 07:04:08 -0000 According to http://0pointer.de/lennart/projects/libcanberra/#status updated September 2012 "libcanberra is mostly feature complete. For now however it includes backends only for ALSA, PulseAudio, OSS and GStreamer." "The OSS driver is incomplete: only sound files that are in a format natively understood by the sound card are supported. If the sample type, channel map or sampling rate of the sound file are not supported by the sound card no automatic conversion will take place and the file will not be played. Also note that the OSS backend is most likely incompatible with OSS4, due to subtle incompatibilities between OSS4 and the OSS 3.x." "It is recommended to always take the "shortest" path from libcanberra to the audio device. I.e. don't use the GStreamer plugin if libcanberra supports the final output target natively. Besides being more resource-friendly and less error-prone, some advanced functionality might get lost with each layer you add to your stack. For example: while you could use libcanberra's Gstreamer backend to output to a PulseAudio server this will not be able to make use of sample cacheing or will be able to attach additional meta data to the sounds played, which might be necessary for effects like positional event sounds." From owner-freebsd-ports@freebsd.org Wed Dec 20 07:26:43 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 265CAE9BA30 for ; Wed, 20 Dec 2017 07:26:43 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E135218CA for ; Wed, 20 Dec 2017 07:26:42 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id 87so12130065ior.5 for ; Tue, 19 Dec 2017 23:26:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=c1e0SmpC/JQtPKPTi+LLXrKsrlSdAHV7lpTdWzArWr4=; b=CkRrlkRO4SQPXKB9MDS0V68cwtNAoN561l1tam9z5oER8GUZEE95vlS2tRO0pVe0Pb 8evl/P00W+qp/rLVRE53hRgYdMLdjnJ5EsnQ3FaiMXAkEz3NlRbRZA4wkOIHCiIoLJhc LM1tng/n+U3HR16vFhP8ON2JYYkmjMtt7NO1ESEpuuIVuar961UDtLeSepBrFyAZR2GG frqkr3OEkU9e2JB4W4fG0nRDe2wKL8DVJ1bzwXHkjuyAUvlWnO1wAoSCS19XThYZuYsD WR6qlUo4DGXXlXiBv4qMF1kZMd9PsaWXzq5B9b/c0C0J+tUPrpDnqIKgVIOfVOmmtcAx Sv7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=c1e0SmpC/JQtPKPTi+LLXrKsrlSdAHV7lpTdWzArWr4=; b=V+ZanVVaowEGE16C/GRKjlGOIWZbkPiGFjclc+YrPc54YWrJYOIzwtN+I/QzfGUEOS jiG/h+CU0IEumk4lWXPvFXojfaAk4A6bSKKZ6fXjbAfdCc6Fwb9Cu+L/wgWO79R2oeFA DqwUYPMUL0pin7ry+QysZ37rj/bCg+Jw6rZwjPeZ+NuXQMAtjs2lEMNsn43BHmHdvz18 qi3tNx0eTyTZEgeU3KG27+uEAiQx/nPOEF19AwdOZ5e+LrABk8lx8pp1uKmtq5l9Ld64 rdExmZLIFpCXOdL6LGLcEYzu2qzgOEyc0+YCB3SO5XIusd99QKG00/04EWR0Oifk9+A8 mcnA== X-Gm-Message-State: AKGB3mJloocTTsFCnWbkl3SyXG8TPrtsIKqXsoI0m5iG+mECyWtraL6P EIgJQ0UzSF0eOfFwe008a0AFT5xuVXBVGO7iSf4= X-Google-Smtp-Source: ACJfBothhO3OxwfrdQBf179zySbO6dzbsXEQEdo+TKSXLXwWyeJHlOxa4IteQJtWCjn7wYTCzMlzVNoFHDs5YSXj9mw= X-Received: by 10.107.157.82 with SMTP id g79mr7184611ioe.296.1513754802169; Tue, 19 Dec 2017 23:26:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Tue, 19 Dec 2017 23:26:41 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Wed, 20 Dec 2017 15:26:41 +0800 Message-ID: Subject: Re: Canberra To: Sid Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 07:26:43 -0000 On Wed, Dec 20, 2017 at 3:04 PM, Sid wrote: > According to http://0pointer.de/lennart/projects/libcanberra/#status > updated September 2012 > > "libcanberra is mostly feature complete. For now however it includes > backends only for ALSA, PulseAudio, OSS and GStreamer." > > "The OSS driver is incomplete: only sound files that are in a format > natively understood by the sound card are supported. If the sample type, > channel map or sampling rate of the sound file are not supported by the > sound card no automatic conversion will take place and the file will not be > played. Also note that the OSS backend is most likely incompatible with > OSS4, due to subtle incompatibilities between OSS4 and the OSS 3.x." > > "It is recommended to always take the "shortest" path from libcanberra to > the audio device. I.e. don't use the GStreamer plugin if libcanberra > supports the final output target natively. Besides being more > resource-friendly and less error-prone, some advanced functionality might > get lost with each layer you add to your stack. For example: while you > could use libcanberra's Gstreamer backend to output to a PulseAudio server > this will not be able to make use of sample cacheing or will be able to > attach additional meta data to the sounds played, which might be necessary > for effects like positional event sounds." > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > @Sid I know this. These are just some of the reasons why I wanted to make sure that the OSS in FreeBSD is actually up to snuff because working on fixing issues like these the easiest route is; just use ALSA or some such crap which is unacceptable to me if it can use OSS. When devs take the easiest path then instead of fixing the root issues, problems are compounded; just like the example you gave of layering pulse on top of gstreamer, those "solutions" are brittle and will inevitably break. I'd like to have a solid foundation and build from there, not be constantly trying to re-implement the wheel. This is just one OPTIONAL dependency for a piece of software that I want to port and this software isn't even audio related, it's an ibus plugin. From owner-freebsd-ports@freebsd.org Wed Dec 20 07:56:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8FCAE9D499 for ; Wed, 20 Dec 2017 07:56:14 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA28C291C for ; Wed, 20 Dec 2017 07:56:14 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=PcRv06YrK1CsZ83E2sJ58yhW5PomD0S6YW0Yz0zCZZ0=; b=MRnKiDP1voSIq9RuX2iSUPpK98cUKRnBk0JoH1kATQ+cVh7I/ZZQS+mMheJvjSbwZ6L+4ZGf+KiB0RVnTWgU5551O6UJdihC4pxnq/jPcceeNi8Ig4vfYRAuBSsCwE0LvL4tcAW2pAz1+h3hZZ7cGWgf1TdIOObM3hKz7gtQGdo=; Received: from plenty.xoc.tele2net.at ([213.90.36.8]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1eRZEY-000851-Sg for freebsd-ports@freebsd.org; Wed, 20 Dec 2017 08:56:10 +0100 Received: from 194-96-164-234.adsl.highway.telekom.at ([194.96.164.234] helo=[10.0.0.93]) by plenty.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1eRZEY-0006Uz-QQ for freebsd-ports@freebsd.org; Wed, 20 Dec 2017 08:56:10 +0100 To: freebsd-ports@freebsd.org References: Subject: Re: Xorg server update From: Walter Schwarzenfeld Message-ID: <67b3c866-6310-7e9b-b5d9-f0409032ea33@utanet.at> Date: Wed, 20 Dec 2017 08:56:06 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 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: Wed, 20 Dec 2017 07:56:15 -0000 Seems on a long way: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678 From owner-freebsd-ports@freebsd.org Wed Dec 20 09:21:02 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E38BFEA1CBD for ; Wed, 20 Dec 2017 09:21:02 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8292A64553 for ; Wed, 20 Dec 2017 09:21:02 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id f140so8362303wmd.2 for ; Wed, 20 Dec 2017 01:21:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=GtL3tbK4JrSvNUyaEI+SJR3BXMABvJmYXeUopT2xT7s=; b=sL5CFy5rFoxOP0B6bQMV1qlYnM7aZ6THIj8Fzz0OUni54AgiE8L4rSBGZJPQPL5G+p AGyvywdcctEVjLxTsaBYV7PgILtvmAACQ2JF+4UYRWwIiTP7G+CUtVOF4djPRto6e7o9 Yi2zY0+y1fEb3HkzehNnjCZ6q3IfS2R73ZI4H+Hvik0EZAM5Z+fcgb0/uJAjT0IoX7qe ImGtw2Xrhfc0xYXCyLJACfDT740auN2RTIkJLtBdSq0Fy6naV1dIWk4T4XTcFONwh0+M 5QAl7LHNnsOG10bppylKzTnOhIve+fyzX0YEzgshQECe5Rey6Hoiknb1fMnnN4PrW73i JadA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=GtL3tbK4JrSvNUyaEI+SJR3BXMABvJmYXeUopT2xT7s=; b=hJ62A0Gy3bMJum0tteYchVfPV9MQtLC4QxA7Ls9OLciV5xqOGbgGw8rU7vYctsNEpT HccKtSmZtRdz1dOeJ9KLr484qpKCordsLJxfwHIICz+mwCFZltOY8lqMV66B0b7WSA7I wrCpFLlZDsuPFcLutoGg2cMWEIcvtzJ8qwBWXhueDAekxm2EkggWdyHIJmdwsI8PzGYX yBMPkGnyxiwPGdK/AtPnA3hUyk8/HxXEodRzKM70mmB/lWSqEHLJRs2RRzvWkEogG4yk NMKPD8RLKGCFCRbrIQhE43MKTWmizsdQAyUxVqBb7mxaOSauepwGJ3Jw0Xv3zIxG251r /8dA== X-Gm-Message-State: AKGB3mKnJ4Lkyk14cEMcdUFTNO+G0MOCZQ9ZvH1hVoZkoehlcghpdVYd YPHkZbKVvj9EYW3FL6chf438MVqIMjN0WV2BGseJyg== X-Google-Smtp-Source: ACJfBospWekC8mNJrbtN+VNxMp3rZoorrrrHXbU5zGGirEeK0/kc02BQ81/nJig43mtxFMDy2UayYMxUAPbhbhjKCnA= X-Received: by 10.28.92.146 with SMTP id q140mr6581156wmb.41.1513761660796; Wed, 20 Dec 2017 01:21:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.197.68 with HTTP; Wed, 20 Dec 2017 01:20:20 -0800 (PST) From: Johannes Lundberg Date: Wed, 20 Dec 2017 09:20:20 +0000 Message-ID: Subject: Vote: making wayland=on default To: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Wed, 20 Dec 2017 09:21:03 -0000 Hi I want to suggest that we enable wayland by default. In current state having some parts of wayland in ports is basically useless the end-users themselves re-build gtk30 and mesa-libs with wayland enabled. libwayland-egl.so from mesa-libs and the extra libraries and headers from gtk30 adds like a few KB, a drop in the ocean compared to xorg packages. (might be something more that I missed) Personally I see no reason not to make it default on, even with flavors coming up. For any Desktop user (as well as embedded devices like IVI-systems and whatnot), Wayland is the future. There's no escaping that. Wayland has been quite usable on FreeBSD for over a year now but access to it is limited due to the extra efforts required to use it. If we are to compare with the other guys, several Linux distros are already switching to wayland-based compositors as default window server. What do you think? /Johannes From owner-freebsd-ports@freebsd.org Wed Dec 20 09:27:42 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA827EA221E for ; Wed, 20 Dec 2017 09:27:42 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 71AC86498C for ; Wed, 20 Dec 2017 09:27:42 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa14.server.lan (via HTTP); Wed, 20 Dec 2017 10:27:38 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: "blubee blubeeme" Cc: "FreeBSD Ports" Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Wed, 20 Dec 2017 10:27:38 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:xQYcTR+oGh6gYEipv0nT5oGsEVln+8OXFXjutyofljZ i0NT/gvInSCtRP08GDuqHxpvOTgkleciqgAnYyyHiyH0TX438o dc5sUBNa6xGZDUTbVkd1oV0ovKy5Hko5AajiFuED1PfS97juSr WAnaPelE+IFZKzCk51IayQ/PsRgehbBR3gZSSKxdoQypp4W48q jOj4gDbUbER7sQFpGNBtPWY7aghzovQ66oN7lghYmWRnspxI5z Palpr17GjCClLlG1oyDgDnIexcsU30Zvxk8WNQNy1JLK6VXa85 pIL3Eo= X-UI-Out-Filterresults: notjunk:1;V01:K0:Q+wPUAh+mXI=:vhPsd2xTysr8OXc7ZuKQKs 9sj60QWf39pgzDkE4c5+VOrsGtur6Xi54vCiQFlm5MK7tWM9ofg1gnWnHejUoERDGoPZmfLYV 8DeV26EV8erHDehSC3onfeKM+jnEhcIYAi/YzsHSdm8uz3aEDPcNhbH5Bbzr3b1Vrjdc3UHwb FCAA6DcCIkk91Q/aJD3Sj9Cr17uUHu5hlr0qVhG07Tj9U4tLVhEjFsw0ubOlrahbm8j07K/Ws j8U4VMwNM43reIOaPHXP4a/NL/hjUADOB0j9RXuoZ+FCGGxt4EvQu4p6lwxOBtfh4B9UqrCrR AtEzvj7rvU/8t062MJhiYTpyJcEwaY/jlc5FwP16eB+mqWJ8jh+W7bpc1pgL3ZHvpYYJiih2M dK/+5eZorHQVOQ56KGunj4dgw1fxERj8FYLI7plkxP7yvwByQVZmcNm/uhsBA+U2FY/fCr8H9 edGl7yhliVaBgIFcPqVnDQJxuTif9+SoKkxd1qBd3AYlPHAyNsuuFaCoR04FQiCKKO6qnntH5 tjEnUZVVMraZ0HVsPhHI94S36baYuFiM/dW0FozpcTp 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: Wed, 20 Dec 2017 09:27:42 -0000 The problem with libcanberra is around pulseaudio and gstreamer. It is also with how gtk, a Visual Graphical toolkit, is mixed in with an Audio application. I didn't say you didn't know about it, I was just putting it out there. They've done a good job of cleaning up and fixing ALSA to work on top of OSS: the most obvious problems with that are fixed. Pulseaudio hasn't been cleaned up, which it is better for applications to avoid it all together, and I don't know if Pulseaudio is worth fixing. It is really a travesty that a simple program that plays simple sounds like "Ding!" has to be this complicated, when OSS, and sndio work, and even when something as complicated as ALSA was simplified enough to work efficiently on top of OSS. "When devs take the easiest path..." This is the Linuxism route, to pile on. I don't even consider that the easiest path, a lazy path instead, considering its usual outcome, of requiring hours to compile something which should compile in 5 minutes. FreeBSD and other BSD's have largely simplified many of these issues, recently. > blubee blubeeme; Wed Dec 20 07:26:43 UTC 2017 > I know this. > These are just some of the reasons why I wanted to make sure that the OSS in FreeBSD is actually up to snuff because working on fixing issues like these the easiest route is; just use ALSA or some such crap which is unacceptable to me if it can use OSS. > When devs take the easiest path then instead of fixing the root issues, problems are compounded; just like the example you gave of layering pulse on top of gstreamer, those "solutions" are brittle and will inevitably break. > I'd like to have a solid foundation and build from there, not be constantly trying to re-implement the wheel. > This is just one OPTIONAL dependency for a piece of software that I want to port and this software isn't even audio related, it's an ibus plugin. Sid; Wed Dec 20 07:04:08 UTC 2017 >> According to http://0pointer.de/lennart/projects/libcanberra/#status[http://0pointer.de/lennart/projects/libcanberra/#status] updated September 2012 >> "libcanberra is mostly feature complete. For now however it includes backends only for ALSA, PulseAudio, OSS and GStreamer." >> "The OSS driver is incomplete: only sound files that are in a format natively understood by the sound card are supported. If the sample type, channel map or sampling rate of the sound file are not supported by the sound card no automatic conversion will take place and the file will not be played. Also note that the OSS backend is most likely incompatible with OSS4, due to subtle incompatibilities between OSS4 and the OSS 3.x." >> "It is recommended to always take the "shortest" path from libcanberra to the audio device. I.e. don't use the GStreamer plugin if libcanberra supports the final output target natively. Besides being more resource-friendly and less error-prone, some advanced functionality might get lost with each layer you add to your stack. For example: while you could use libcanberra's Gstreamer backend to output to a PulseAudio server this will not be able to make use of sample cacheing or will be able to attach additional meta data to the sounds played, which might be necessary for effects like positional event sounds." From owner-freebsd-ports@freebsd.org Wed Dec 20 09:47:13 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B427EA31D2 for ; Wed, 20 Dec 2017 09:47:13 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9F85653D6 for ; Wed, 20 Dec 2017 09:47:12 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x229.google.com with SMTP id 87so12516473ior.5 for ; Wed, 20 Dec 2017 01:47:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jmr8sIQiaaaJZ7snsDiLPwTEKvlRDxoZtvre77TJ0+8=; b=QPY0hg5n7pIS2AEn3DqjG8RY3vLnp2XCi9A9SHoyTW3je0Dl9T4wYzlgm6t764kq8h xb+iWsyMlAug0A5YwKRcyZQTcPm5fG1dLg9bU1fkB5HbeQYWDW/+BJ1YLuFolIjKWVDP n/ApWiyb4ZYy1nU4hv6k02Ercj6tia7KhRyqXmmIQEMdLnQe1KN2H4LvCbA1SNEU6CjT XoTj3VfeqiiVSZv2F742HXPR2J2ScUFVc5DmTqVAutnxp72iFK0pcdOqsMygpfu32kOh A0yYF4/7+pARiefzBLT+NsscQ2b52q0FPda/DabTVlz+EdKnOA+9fydvVFQQx3MLeHwf Epqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jmr8sIQiaaaJZ7snsDiLPwTEKvlRDxoZtvre77TJ0+8=; b=DZRyZasauqr14qNxWAmH+G44FQoCCpgVZeVn0ASaIlOa4j3olJ+sP4i407G9Dz/gZZ 1XH9qGXPZ2pto6yfHBOtmjvd1kmq5kz6+AI1vTsARlXMkhyaOJHHYAZ8zuhhKIjN5Qeo X4SbBbHd0ZAup80souHoO3OQ3Gq6ehZ6VsmAaSTBxv1BHU++407o//v+L5UO5RAp+u78 JtZnCMWuDVu5G4Xpk2X6cCi4Zzpu/va18eZCfL+XZPnU7vMgXhZZUY4p/9Akn5xX3ByU QRs+FwqH4coM5ZED9u0iL/Gm/j8Fr43xpziKFCvnVMoxdw8YttlACjKDJtwaeIeFE1xf nZzQ== X-Gm-Message-State: AKGB3mL96xfyGJN0jGeUn+rdYagOD7NknnXYgK0xWaNqjl+Y1NfoVzU5 ZwWTGbWXKJtMWPDYliNc2OfiPTwnFNIWv+ueSrc= X-Google-Smtp-Source: ACJfBoslWUBjZJfQDAl8YeSxzi9Zso7E45qycGcSgQrmbygt9yM4ilfo9iFO2CPmSmibYveJVslIq+W1R0mUoS4eVgY= X-Received: by 10.107.18.35 with SMTP id a35mr3662559ioj.291.1513763231975; Wed, 20 Dec 2017 01:47:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Wed, 20 Dec 2017 01:47:11 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Wed, 20 Dec 2017 17:47:11 +0800 Message-ID: Subject: Re: Canberra To: Sid Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 09:47:13 -0000 On Wed, Dec 20, 2017 at 5:27 PM, Sid wrote: > The problem with libcanberra is around pulseaudio and gstreamer. It is > also with how gtk, a Visual Graphical toolkit, is mixed in with an Audio > application. > > I didn't say you didn't know about it, I was just putting it out there. > They've done a good job of cleaning up and fixing ALSA to work on top of > OSS: the most obvious problems with that are fixed. Pulseaudio hasn't been > cleaned up, which it is better for applications to avoid it all together, > and I don't know if Pulseaudio is worth fixing. > > It is really a travesty that a simple program that plays simple sounds > like "Ding!" has to be this complicated, when OSS, and sndio work, and even > when something as complicated as ALSA was simplified enough to work > efficiently on top of OSS. > > "When devs take the easiest path..." This is the Linuxism route, to pile > on. I don't even consider that the easiest path, a lazy path instead, > considering its usual outcome, of requiring hours to compile something > which should compile in 5 minutes. FreeBSD and other BSD's have largely > simplified many of these issues, recently. > > > blubee blubeeme; Wed Dec 20 07:26:43 UTC 2017 > > I know this. > > These are just some of the reasons why I wanted to make sure that the > OSS in FreeBSD is actually up to snuff > because working on fixing issues like these the easiest route is; just use > ALSA or some such crap which is > unacceptable to me if it can use OSS. > > > When devs take the easiest path then instead of fixing the root issues, > problems are compounded; > just like the example you gave of layering pulse on top of gstreamer, > those "solutions" are brittle and will > inevitably break. > > > I'd like to have a solid foundation and build from there, not be > constantly trying to re-implement the wheel. > > > This is just one OPTIONAL dependency for a piece of software that I want > to port and this software isn't > even audio related, it's an ibus plugin. > > Sid; Wed Dec 20 07:04:08 UTC 2017 > > >> According to http://0pointer.de/lennart/projects/libcanberra/#status[ > http://0pointer.de/lennart/projects/libcanberra/#status] updated > September 2012 > > >> "libcanberra is mostly feature complete. For now however it includes > backends only for ALSA, PulseAudio, OSS and GStreamer." > > >> "The OSS driver is incomplete: only sound files that are in a format > natively understood by the sound card are supported. If the sample type, > channel map or sampling rate of the sound file are not supported by the > sound card no automatic conversion will take place and the file will not be > played. Also note that the OSS backend is most likely incompatible with > OSS4, due to subtle incompatibilities between OSS4 and the OSS 3.x." > > >> "It is recommended to always take the "shortest" path from libcanberra > to the audio device. I.e. don't use the GStreamer plugin if libcanberra > supports the final output target natively. Besides being more > resource-friendly and less error-prone, some advanced functionality might > get lost with each layer you add to your stack. For example: while you > could use libcanberra's Gstreamer backend to output to a PulseAudio server > this will not be able to make use of sample cacheing or will be able to > attach additional meta data to the sounds played, which might be necessary > for effects like positional event sounds." > > I'll work on it but let me get the port in the tree first, then I can refine it. Just as i've done with my previous ports. From owner-freebsd-ports@freebsd.org Wed Dec 20 10:49:39 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BE86E80036 for ; Wed, 20 Dec 2017 10:49:39 +0000 (UTC) (envelope-from cheffo@freebsd-bg.org) Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 58CB067522 for ; Wed, 20 Dec 2017 10:49:39 +0000 (UTC) (envelope-from cheffo@freebsd-bg.org) Received: by mail-vk0-x22e.google.com with SMTP id k132so4187190vke.10 for ; Wed, 20 Dec 2017 02:49:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd-bg-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=oh3N3iCuletZOAg0LM9hChcSrF3JLihVWBYc99hNhO0=; b=uX/jeFR0jF6zEk0PsweHagsMzcmG2maDSR53ID+dUdb/ISkMuRoraGvhDlXAErKlpX aYypSqtzBL7IcrjxAtsDUjjL3AAf6bEcsd2fzmbR1NO96vQoAFabhAZBl2DRZkQwnslJ UYh4aUKpPyGoO3osGoSnA8JZPgb0pfvIt2oPIxg1RyulGXr15V3h33xvixP3yqmc4Kah CAYctOjhw+qKk1IGP9L5l/zjsTqGBIwP7+vIWHACFLZKamvAuxrzKxBz1tPIKQHxZEL9 ozds0fnR5cvIr/zE2COmdGELDXfd2CnF7d+mJM0t8TXzjjneVuYrfiaJO8nl3eyEo4ZR Whlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oh3N3iCuletZOAg0LM9hChcSrF3JLihVWBYc99hNhO0=; b=ZAI8y+HxisJ7ZYVJtT5FfznYhEdxJ2/RMiCKp0UQfRf13dEUDF+i2K3e2XgkKW/nCM /g08KjnHB7OCZal3ctIMY5u8g59gg91FGzTnYpvehxs6+SfxDLjmbzsVr1O7dfsKQeCl GmShRY3QYcJNMKjllqTqY0K88XLoJF+sLinfCH9roGHJN1TvTHgipm7hSALv3h1Y6aUY ULSca4DNpDF4flJUGa014mkcUOLohF6hdw2Cr1fLagPUleGCv7Kh/hpOnuPYhdeL45Lw CfdiC9TmAxddzd/+9FpzKsqXK5Init+Z67mADcKJOE2j/Dysw6NIkAkspYYWeX5OeZEr noFw== X-Gm-Message-State: AKGB3mJdS3LqS5dBklMzjXU7UdT4JZRPtH4jmrUkBAZTw4RLR67igsMf 0bbXTc2QNaLyFtOewlLwZs1ePr137WXI4kBYqzL/ITqWLaw= X-Google-Smtp-Source: ACJfBovUr5z4OGIebULbfEfdtDbk/6HxIN82T9F4yqXhZI5JSN0alHIuoK7uvkA4MnOhIHa8pjBdFg1nbpJmsEk2sEA= X-Received: by 10.31.4.69 with SMTP id 66mr6546058vke.118.1513766977819; Wed, 20 Dec 2017 02:49:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.191.144 with HTTP; Wed, 20 Dec 2017 02:49:37 -0800 (PST) From: Stefan Lambrev Date: Wed, 20 Dec 2017 12:49:37 +0200 Message-ID: Subject: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224205 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 10:49:39 -0000 Hi, Can a port commiter look into this - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224205 ? From owner-freebsd-ports@freebsd.org Wed Dec 20 10:55:37 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6732FE8066A for ; Wed, 20 Dec 2017 10:55:37 +0000 (UTC) (envelope-from ros@bebik.net) Received: from smtp.osorio.me (smtp.osorio.me [5.196.94.126]) by mx1.freebsd.org (Postfix) with ESMTP id 36BE167947 for ; Wed, 20 Dec 2017 10:55:36 +0000 (UTC) (envelope-from ros@bebik.net) Received: from [172.16.33.187] (unknown [213.174.108.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.osorio.me (Postfix) with ESMTPSA id EC6FB319B2 for ; Wed, 20 Dec 2017 10:55:35 +0000 (UTC) From: Rodrigo Osorio Subject: Re: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224205 To: freebsd-ports@freebsd.org References: Message-ID: Date: Wed, 20 Dec 2017 11:55:35 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Wed, 20 Dec 2017 10:55:37 -0000 On 12/20/17 11:49, Stefan Lambrev wrote: > Hi, > > Can a port commiter look into this - > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224205 ? > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" I take it. Cheers - rodrigo From owner-freebsd-ports@freebsd.org Wed Dec 20 11:44:11 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C415E83105 for ; Wed, 20 Dec 2017 11:44:11 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-oln040092010036.outbound.protection.outlook.com [40.92.10.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45D916933F for ; Wed, 20 Dec 2017 11:44:10 +0000 (UTC) (envelope-from carmel_ny@outlook.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=erdznKb8c5t+O8JvAtgbh4CTjpHMIZyGuh8FlvKYn1w=; b=M8sgq4SGDQlLxDOFOnLDGSu9UbVCWMn4EY4tSMwFFOGZGUHPbRFm3ev5fNuBL6S/9j0hVsnoEHXoa6Dx0ADfep1hRSDBBNUtc31lCzmJdV1khCepUFJwVIepbvLTsTDDGZm90b8h4xhiwJNGflsHMzx7Nb5ijdzgHPZn9+iY/cGfw6eIrIfL7JufYtv/xxV+pEQwG2B8rj63bHJyPuRgNZcq7z6lZVCZljmMVwlyb7z133Sknc5ceBd6p1TzbS/ZDVGRp9uxk5hg27XxWVYRggk4frdSSyhxSBYoGSeS69z+k7ALDcLoTlNp6c71AXKCjrkQWSfSQNW7zBgVgJaZig== Received: from SN1NAM04FT040.eop-NAM04.prod.protection.outlook.com (10.152.88.52) by SN1NAM04HT237.eop-NAM04.prod.protection.outlook.com (10.152.89.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.282.5; Wed, 20 Dec 2017 11:44:09 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.88.56) by SN1NAM04FT040.mail.protection.outlook.com (10.152.89.1) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.302.6 via Frontend Transport; Wed, 20 Dec 2017 11:44:09 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) with mapi id 15.20.0345.013; Wed, 20 Dec 2017 11:44:09 +0000 From: Carmel NY To: FreeBSD Subject: Re: Vote: making wayland=on default Thread-Topic: Vote: making wayland=on default Thread-Index: AQHTeYfYxnAEqt0WWkyBd/gx9vxbyA== Date: Wed, 20 Dec 2017 11:44:08 +0000 Message-ID: References: In-Reply-To: Reply-To: FreeBSD Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:033293530E628578DE0D58AA876EFEF8A8B4B6AA4E8001CE19DB1D8BBA82E24E; UpperCasedChecksum:33831C14A1E077C1BCC81D675DC8608AEC136EC5E86DD2597EE284B38E8F1734; SizeAsReceived:7043; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [ZMDHyi7yVEcBud/uB8/0pwefpXtoDrG7] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN1NAM04HT237; 6:CxFos+0Cmdf0f3Mb8tUIMPFIBD3a86SFtL0vDk89NO0qGJ4SE9cjdkozJSj4TriGKmPIl0XYTHBKPU+TWd/lVcCM3UTA7BKhlopuPMFMGnp0+pMPTfETrF9eKfxkyxYZBccs2y3PzoXua5QfIaoZiszuasti2wgJuOlVl/ULgPugn66mMGM0hDyocu1UA01ohADAdTRf+ftxDlTFPZYAc6TOQCaj74xtOQVRGEEi9vBwMEuiPMkRhsXQLVI30AoXo6KdAsS4WAdSGd7e4kgENMHHOQPg9tkCHWImmpuDJK4FWlKXHRZMwcPD9LAqRIIYfpq9gqo4VL6/w0S4RqTby4TIdB+uyLUpE8RCvbETAz4=; 5:oIPxS6Tb4YhfXvAMq05FDPwoUmfQFDYvnp6NgLTaLhB71L2mjfbKTOovMWHgV+7sZ7b4Llp9vCX39xQnQdcshXfS+UNNP6EzFw+daTrAv/Qy5nEZt72r2SA7Jh7TFvdopN2rGKQjYAtEVb2Uzl7q/5SeLEXG9DvwQLDrX0nlz+s=; 24:fft+wWsKS21Km6X7ZoNl3SbadLZjzSzwpPgol090udh+NZJMxJ66lGlTvlm+waGUt+FxZLHKMQVJam/Z8juFDi4Q6jPnpfINnfWuO4D7fqs=; 7:5nrBa/Pl7DJJhHRSM3400lmZ8LzFI5KTzKpo9gPGQsJMwg9wZ3xFaURl6+ozETteKG1Iy/RY+c/Ev3WEFMX++fsaOeeO+4LEdkqt3j0aoomSuAfTdX371VNleyncEnuoP3gLdc+nRNByAuiC38u2OjpQrCYpW8fYaW6Mzn6P9QlDMxKZnswPffb/UXGLC/UpoEvxFKkxLCIBx4OWMUO8u9NVJE5sdpsZLIEAEchWtcZZWOOEhFyR6J5bwo3Wsfw+ x-incomingheadercount: 47 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:SN1NAM04HT237; x-ms-traffictypediagnostic: SN1NAM04HT237: x-ms-office365-filtering-correlation-id: fcda9cea-e8c6-4de7-0628-08d5479efacc x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:SN1NAM04HT237; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:SN1NAM04HT237; x-forefront-prvs: 0527DFA348 x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SN1NAM04HT237; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-ID: <4775ACDB8FFDF14D971C408D683B2692@namprd20.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: fcda9cea-e8c6-4de7-0628-08d5479efacc X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Dec 2017 11:44:09.0560 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT237 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: Wed, 20 Dec 2017 11:44:11 -0000 On Wed, 20 Dec 2017 09:20:20 +0000, Johannes Lundberg stated: >Hi > >I want to suggest that we enable wayland by default. In current state >having some parts of wayland in ports is basically useless the >end-users themselves re-build gtk30 and mesa-libs with wayland >enabled. > >libwayland-egl.so from mesa-libs and the extra libraries and headers >from gtk30 adds like a few KB, a drop in the ocean compared to xorg >packages. (might be something more that I missed) > >Personally I see no reason not to make it default on, even with >flavors coming up. For any Desktop user (as well as embedded devices >like IVI-systems and whatnot), Wayland is the future. There's no >escaping that. > >Wayland has been quite usable on FreeBSD for over a year now but >access to it is limited due to the extra efforts required to use it. > >If we are to compare with the other guys, several Linux distros are >already switching to wayland-based compositors as default window >server. > >What do you think? The normal scenario would be for FreeBSD to wait until other distros have throughly vetted the application/protocol/device/other and then consider adding it to the basic FreeBSD structure. Unfortunately, by that time the target has moved on and FreeBSD is as all too often late to the party. I am considering firing up an older PC I have laying around,install the latest version of FreeBSD and then trying out a few application that are presently not available or like "wayland" need some massaging. It all depen= ds if I can actually get some free time. Wayland does look promising though, I hate "X". --=20 Carmel From owner-freebsd-ports@freebsd.org Wed Dec 20 12:00:23 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18AAEE84178 for ; Wed, 20 Dec 2017 12:00:23 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DC9169B0D for ; Wed, 20 Dec 2017 12:00:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id t8so9343597wmc.3 for ; Wed, 20 Dec 2017 04:00:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=NjJVFCzNdsV6/bW5PAHtJgKkP6uIhStUV5Uw+VjfefI=; b=J6/zV6QR0HvX4zUJHNviQrcASrQayCH0iVnVZ3PrOcQJmn7zCJS4UxQwU1W1Dr0uUl Ts2Qq0rZ1asAbw6QbmrP85G9GLwdGTBj4SJbHJSe4lEYP+LcKgSqfyhxT5wkEtWFaX7d rshwghXfA4fP6RnEqvQlC15DM1RHyiynQn0PQK+QdPH6csDhT5p6z6tYcmDdVdj9BA6P PzYrzhJsRPAMwT2mrr7SoiSvhD4I9pxAay0di25bKRxYrhZZzxs3kNp2GvA3Xoyf/4lw 58YYnGnr9D3nrnGR3P1rEAlSoBpCMzBKngkYqxMNtbbn/e6uR2JiUJBHhIGfx1F9deNW bvTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=NjJVFCzNdsV6/bW5PAHtJgKkP6uIhStUV5Uw+VjfefI=; b=EkTXbh10H9Klktjax/GWg3MpiQWE8DMEg/e76xRpZ0zKJua/EI7vJgPwoZdCgWhopq x6wdOBeB2MnMxDl+ufImZmKSaVJzDVuuF3kTT1Rfj9bGTQJCirwQ+9UyZr2s744NZskY bIi8k4bswUfTH9SDdm4S/6Gc1Xb6N5+hQ5aAWd2yvBBzJG4l00/WHYiv0iXLtdfHQe7z 4zo4bbBWeC3krJjI0Kr/qCAwzkTMWfWzmImjlM+vFZ7c2vLGx9Y9d7bQGvlvRZw69u93 eJywT/kNflyaZMJPA1T/Mz4Q34JtmIboKF8nkEtUPxI5wXFHasSEGGyCOcT/SdHHQH/8 QSEA== X-Gm-Message-State: AKGB3mLyy2WWWVyiq5Ca4m/nDL7GPMkrzkt2N6wb7GV+YSVfWa/1D1CY uskpJAnF0Gqp+jToTh5HaURVbTyvW3dXqvP7JvI= X-Google-Smtp-Source: ACJfBoteKcJ0D/zWToe+551ms3jNw59M9urm5xFH3Wx7qOh83fvGfJU1vZGXqpzE9Ue9COaJk5HUXxbiuRo9jL/1Jq0= X-Received: by 10.28.92.146 with SMTP id q140mr7034954wmb.41.1513771220870; Wed, 20 Dec 2017 04:00:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.197.68 with HTTP; Wed, 20 Dec 2017 03:59:40 -0800 (PST) In-Reply-To: References: From: Johannes Lundberg Date: Wed, 20 Dec 2017 11:59:40 +0000 Message-ID: Subject: Re: Vote: making wayland=on default To: FreeBSD Content-Type: text/plain; charset="UTF-8" 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: Wed, 20 Dec 2017 12:00:23 -0000 > > The normal scenario would be for FreeBSD to wait until other distros have > throughly vetted the application/protocol/device/other and then consider > adding it to the basic FreeBSD structure. Unfortunately, by that time the > target has moved on and FreeBSD is as all too often late to the party. > Just to be clear. We're not talking about replacing X as the default choice (if there's such a thing on FreeBSD). We simply want to make Wayland more accessible to people who want to try it out or make it their default desktop. From owner-freebsd-ports@freebsd.org Wed Dec 20 12:08:29 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94236E84B7D for ; Wed, 20 Dec 2017 12:08:29 +0000 (UTC) (envelope-from lenzi.sergio@gmail.com) Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 491EA6A039 for ; Wed, 20 Dec 2017 12:08:29 +0000 (UTC) (envelope-from lenzi.sergio@gmail.com) Received: by mail-qt0-x22e.google.com with SMTP id k19so27936816qtj.6 for ; Wed, 20 Dec 2017 04:08:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references :disposition-notification-to:mime-version; bh=UWUcY/gKk8qbfLEu/7O+UdBEJ50wZVu7QsPx+pfDYEM=; b=hBl9oqSpVWI4uvuGIzomy/ZX2MN6O+lxhfJsocxao5A6oec+uVAYdHZQurvhlXoVs/ AR/VJBjrk+9FAcNJTTh9srARxrYlxPtd2GyQENXgc1jptHavhB4Vjb6sI6RVvTpRy/+Z WKQOgOf9VUTSMskPhVdILvkZvt6R0QWuAeGXLalz4vNTvZ2pj3c8loxC/Tf0fg1jZL4i 7O4eE5dVF0EjBc3FZZluDzL2RUTvlLXmErqLAB4rkd5H6n657eKyBZsMqMoiqvuYeCqE HgkoA/P6IZis6fOIXlRuYXuJ1eq6+b9mY8AEk9CesqDrlW19h4/fdrmHxc5ocaU9xTic rq9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:disposition-notification-to:mime-version; bh=UWUcY/gKk8qbfLEu/7O+UdBEJ50wZVu7QsPx+pfDYEM=; b=HyzWrMK6zNxJNNulHfNRYq+4r5+ZovbWSovTO1yV1gapYubfdNeiuTHrL1FxGmEdf8 G2eN3USiO61C1eaksqb+5BKch0r+OApcbdhUsKWPbvKLYTuxi25sk80uSwJjyIpCygXX RNRNvJ4WeZTNRcnuYrw2rHbkwmscvwgOokcfdCIzseG21ZlSf7Z984II+5m3ScW3wMIz U/+nr1dY/FfMQZrRPVUmGSz3r1IpK7WJDhuaLQ/+FlMju+ZJO9wRZKlXH954NHpGJhLn T5g6p0muj7ErWrOsDE4pQGzXCPx99d+7v2uF74Ayu4Qddh6ELgvDs4Dwhd8NP5Mw9+/K Vm/w== X-Gm-Message-State: AKGB3mLmp734kFwu61viuLx9rHBUTfJzf2L4AVi+bWsvNcfzG6tvUfkd LYCcT9+y1Ec+gGe4su3sliYu9Q== X-Google-Smtp-Source: ACJfBosvvY3eIg+CEUkGNyftaBCVoaNXWSfWVkSyt1wlOt6tWIVxRgM2stqMC463KWd5XvTU8pQ/rA== X-Received: by 10.200.1.20 with SMTP id e20mr9512756qtg.2.1513771708120; Wed, 20 Dec 2017 04:08:28 -0800 (PST) Received: from [192.168.1.108] ([201.81.137.158]) by smtp.googlemail.com with ESMTPSA id s4sm10762726qkd.66.2017.12.20.04.08.26 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 20 Dec 2017 04:08:27 -0800 (PST) Message-ID: <1513771702.23135.0.camel@gmail.com> Subject: some fix needed still From: Sergio de Almeida Lenzi To: Ports FreeBSD Date: Wed, 20 Dec 2017 10:08:22 -0200 In-Reply-To: References: <36151973-c15f-c331-e9bd-5f574c0da6a7@freebsd.org> X-Mailer: Evolution 3.24.2 FreeBSD GNOME Team Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 12:08:29 -0000 Version portmaster-3.17.11_9 when you are in the port directory, the portmaster build wrong path /usr/ports/ports instead of /usr/ports ========================================================= [root@VMS /usr/ports/x11-themes/kf5-oxygen-icons5]# portmaster ===>>> No /usr/ports/ports/Mk exists, and no information ===>>> about ports/Mk can be found in /usr/ports/MOVED ===>>> No valid installed port, or port directory given ===>>> Try portmaster --help [root@VMS /usr/ports/x11-themes/kf5-oxygen-icons5]# From owner-freebsd-ports@freebsd.org Wed Dec 20 12:32:52 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07317E8612D for ; Wed, 20 Dec 2017 12:32:52 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DA80B6AFAE; Wed, 20 Dec 2017 12:32:51 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 2E725187EF; Wed, 20 Dec 2017 12:32:51 +0000 (UTC) Date: Wed, 20 Dec 2017 13:32:50 +0100 From: Baptiste Daroussin To: Johannes Lundberg Cc: freebsd-ports@freebsd.org Subject: Re: Vote: making wayland=on default Message-ID: <20171220123250.hzbxaz6qbfb2wzrh@ivaldir.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vqlztm2luzuituzk" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171208 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: Wed, 20 Dec 2017 12:32:52 -0000 --vqlztm2luzuituzk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 20, 2017 at 09:20:20AM +0000, Johannes Lundberg wrote: > Hi >=20 > I want to suggest that we enable wayland by default. In current state > having some parts of wayland in ports is basically useless the > end-users themselves re-build gtk30 and mesa-libs with wayland > enabled. >=20 > libwayland-egl.so from mesa-libs and the extra libraries and headers > from gtk30 adds like a few KB, a drop in the ocean compared to xorg > packages. (might be something more that I missed) >=20 > Personally I see no reason not to make it default on, even with > flavors coming up. For any Desktop user (as well as embedded devices > like IVI-systems and whatnot), Wayland is the future. There's no > escaping that. >=20 > Wayland has been quite usable on FreeBSD for over a year now but > access to it is limited due to the extra efforts required to use it. >=20 > If we are to compare with the other guys, several Linux distros are > already switching to wayland-based compositors as default window > server. >=20 > What do you think? >=20 I agree on that, we should activate wayland everywhere by defualt, as it do= es not prevent at all from having a fully fonctionnal regular X working as wel= l. All wayland option should be on, and this as nothing to do with flavors :) Please do it :) Best regards, Bapt --vqlztm2luzuituzk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlo6WFsACgkQY4mL3PG3 PlrxYBAAzzC0uJ5w6boH0P/EcMLX4CTomv/92vjsKQdwnW6Rk1i+OEpJpJRAccuC ipYwczG9opw86vvWfjxWHMyo7iZGJG5LmsBIpuJCeur7E05uYF9/d0bKedsxPzEX KAz9AvO9wO6mFr5z4GSPuW65xRq2hS8jK/JMY5OuVm4vz9aF+0MRRul16koY7U+O FlK8rZvx3gR5x6VH5+lu1vJjuEd1PxNy4VTaIZ4ntbuaKgbkMwTIdz2KEQ7pN0P9 A71j8kmjpim3FVQRFSDnrFXnPHsECzJ6upM0kZXfw3RsxokZbkwO1AtidX2YnQ11 BzSCOCt6aZjvpejwPdvRtnUqHfraZa5fIZ30cwW73QLH4A6dUBIbv1FcNj6VD7nq WJAGuFGY59+3Mrj/e/PBIS/58GZ01h13gM7OZdu1YjUTfqik0Du3irdnlODCbEdL oDmUViFoQxW4mqMurnoBwdn5Vv8zESg47NTxbXkNwSF/RWx7s9ffMjfeTExRud9y 5zwixYIf3wi+8Yu8bzbrUYqcimU//psoebTZyJTanqL1i8r8XPc3d5KkV3ioumtn K8jJqx2Tv/kN0Tiwv2x0zcECi5dpSrkitOCJr6+X7s/A6sI0kCky3T/p5E8dWg0J NPP2WkPSzGG/HTxQIZewxMUofVhNxaXXYV0b3hp5lxnDYZMzWrk= =rmP0 -----END PGP SIGNATURE----- --vqlztm2luzuituzk-- From owner-freebsd-ports@freebsd.org Wed Dec 20 13:02:52 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53BB8E87B89 for ; Wed, 20 Dec 2017 13:02:52 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id A62936C33D for ; Wed, 20 Dec 2017 13:02:50 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 94661 invoked by uid 89); 20 Dec 2017 12:56:07 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@46.244.226.155) by mail.grem.de with ESMTPA; 20 Dec 2017 12:56:07 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Vote: making wayland=on default From: Michael Gmelin X-Mailer: iPhone Mail (14G60) In-Reply-To: <20171220123250.hzbxaz6qbfb2wzrh@ivaldir.net> Date: Wed, 20 Dec 2017 13:56:06 +0100 Cc: Johannes Lundberg , freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <47CA1ED8-A95E-4BD8-99EE-639AE466B9CB@grem.de> References: <20171220123250.hzbxaz6qbfb2wzrh@ivaldir.net> To: Baptiste Daroussin 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: Wed, 20 Dec 2017 13:02:52 -0000 > On 20. Dec 2017, at 13:32, Baptiste Daroussin wrote: >=20 >> On Wed, Dec 20, 2017 at 09:20:20AM +0000, Johannes Lundberg wrote: >> Hi >>=20 >> I want to suggest that we enable wayland by default. In current state >> having some parts of wayland in ports is basically useless the >> end-users themselves re-build gtk30 and mesa-libs with wayland >> enabled. >>=20 >> libwayland-egl.so from mesa-libs and the extra libraries and headers >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >> packages. (might be something more that I missed) >>=20 >> Personally I see no reason not to make it default on, even with >> flavors coming up. For any Desktop user (as well as embedded devices >> like IVI-systems and whatnot), Wayland is the future. There's no >> escaping that. >>=20 >> Wayland has been quite usable on FreeBSD for over a year now but >> access to it is limited due to the extra efforts required to use it. >>=20 >> If we are to compare with the other guys, several Linux distros are >> already switching to wayland-based compositors as default window >> server. >>=20 >> What do you think? >>=20 >=20 > I agree on that, we should activate wayland everywhere by defualt, as it d= oes > not prevent at all from having a fully fonctionnal regular X working as we= ll. >=20 > All wayland option should be on, and this as nothing to do with flavors :)= >=20 > Please do it :) >=20 > Best regards, > Bapt I add my "vote" from the X11 list: Yes please, I had exactly that problem ye= sterday. Best, Michael= From owner-freebsd-ports@freebsd.org Wed Dec 20 13:08:45 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39707E87F71 for ; Wed, 20 Dec 2017 13:08:45 +0000 (UTC) (envelope-from tommi.pernila@gmail.com) Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E512C6C519; Wed, 20 Dec 2017 13:08:44 +0000 (UTC) (envelope-from tommi.pernila@gmail.com) Received: by mail-qk0-x22d.google.com with SMTP id x7so9152588qkb.0; Wed, 20 Dec 2017 05:08:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=LIy83D434l1I+LwasRk06Re0/FGjEXWy5mbtpdciQcI=; b=uBf4g+9vTei9Plt5fC0V0NRcxmK/PfsPZ9SpmPE7PkYECMlq+oXAX7rRfO9i1cZfZx gIPRVNK71/PBMvKZyT27Fr1hoDfojwbLKfCuomVCIKF8KstYrD3Osas/NXhhoi6+CeAw KN38fdmNr7C3SeuPSQknaJWd2jMFgxd9w0O9S2QQWJWy/6z2uceyZ3zwIc0Md2oGkeNs vzH4Dx2UtA6Z97yOD5T0eQvT8naVWAFWNDNXIcJbwO4Gl3XDZc00pCLZ3024Q7UzklV3 m1Ja+/OIBayUCcKE0KEQuV6AkovNgPSBqhC2nG9Fudn8UPassZU9B1Xhh+1JAIAJuy5F v4Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=LIy83D434l1I+LwasRk06Re0/FGjEXWy5mbtpdciQcI=; b=lJOj17nfGH7IrBb2PvTYDGHFA1YdvguZVGo+yC0MPsDIMzQ6V08qrapsku1HO0DOtO aMI8C/jT0UWFX+VynaaaJ+JwzAL24hL9V2ZaJko+aH4xH+MWoitUlNXL3DyuvzeP+cb1 i5RGY4nJbXocAWbzhHzr8no95SuObhStwG4LdOzz99W9e6pWJlwaoLQfhAo2+uv3Jzjd UHfpyhb1ujj4MRiAbXIQoaS4GqpgSjvid/Ths1UJCn4MBg3mc54PE0502ofLB1mvxytI TFWsnLbBQfy4JBGgh76YEyTQ/cSeCihyrWuclp8c4B2Oi6cLL4BTl9IdIwCfFqXRz8TO Myig== X-Gm-Message-State: AKGB3mL7UYcHR4tHLFkW9vu9y1pibi1brSxzdQiY4X3S86zXZvftEykO 51iqlHGuugUlWOo0msIc1cytOP1WB7ocrq/KPt5yMA== X-Google-Smtp-Source: ACJfBouaEMPyxrWVSS2enYDjBX+WvSvcMrC1LAZgw1ty4fCq5mAsNeSfjTUSWmUtRisZAjiWIaYNbItYlzTBNuqoThI= X-Received: by 10.55.221.20 with SMTP id n20mr9777957qki.181.1513775323902; Wed, 20 Dec 2017 05:08:43 -0800 (PST) MIME-Version: 1.0 Sender: tommi.pernila@gmail.com Received: by 10.200.27.41 with HTTP; Wed, 20 Dec 2017 05:08:42 -0800 (PST) In-Reply-To: <47CA1ED8-A95E-4BD8-99EE-639AE466B9CB@grem.de> References: <20171220123250.hzbxaz6qbfb2wzrh@ivaldir.net> <47CA1ED8-A95E-4BD8-99EE-639AE466B9CB@grem.de> From: Tommi Pernila Date: Wed, 20 Dec 2017 15:08:42 +0200 X-Google-Sender-Auth: 2sgyUd3plDehqoSTOBVQXZiKFTY Message-ID: Subject: Re: Vote: making wayland=on default To: Michael Gmelin Cc: Baptiste Daroussin , Johannes Lundberg , freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 13:08:45 -0000 Looking forward to testing Wayland more on FreeBSD. So yes please! -Tommi On Wed, Dec 20, 2017 at 2:56 PM, Michael Gmelin wrote: > > > > On 20. Dec 2017, at 13:32, Baptiste Daroussin wrote: > > > >> On Wed, Dec 20, 2017 at 09:20:20AM +0000, Johannes Lundberg wrote: > >> Hi > >> > >> I want to suggest that we enable wayland by default. In current state > >> having some parts of wayland in ports is basically useless the > >> end-users themselves re-build gtk30 and mesa-libs with wayland > >> enabled. > >> > >> libwayland-egl.so from mesa-libs and the extra libraries and headers > >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg > >> packages. (might be something more that I missed) > >> > >> Personally I see no reason not to make it default on, even with > >> flavors coming up. For any Desktop user (as well as embedded devices > >> like IVI-systems and whatnot), Wayland is the future. There's no > >> escaping that. > >> > >> Wayland has been quite usable on FreeBSD for over a year now but > >> access to it is limited due to the extra efforts required to use it. > >> > >> If we are to compare with the other guys, several Linux distros are > >> already switching to wayland-based compositors as default window > >> server. > >> > >> What do you think? > >> > > > > I agree on that, we should activate wayland everywhere by defualt, as it > does > > not prevent at all from having a fully fonctionnal regular X working as > well. > > > > All wayland option should be on, and this as nothing to do with flavors > :) > > > > Please do it :) > > > > Best regards, > > Bapt > > I add my "vote" from the X11 list: Yes please, I had exactly that problem > yesterday. > > Best, > Michael > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Wed Dec 20 13:31:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC760E893C8 for ; Wed, 20 Dec 2017 13:31:49 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D4306D6F1 for ; Wed, 20 Dec 2017 13:31:49 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id l19so9937914wrc.2 for ; Wed, 20 Dec 2017 05:31:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uvA3fGAsdpLDdGT7prfLw2pioa5b3oG//gCXXxhEucc=; b=HqZAe2zbPhVdWfsLxVo+6iabwjDb7us2UirRJ+0DksyrIl5rK2rr+HAvxYAoxhtbWj PijdaW8UztjA761id3My2pBQG3T7YZLdNGyqCQ6KlbUzW7IOmlwGxMUtQcxRNKmr+Dfl /mRSwDc/LN4Ql84BAiKX38/Qwk4sKD37JrMPzTJJTzdlgW1J90nwOMyKg0klsQNn3bNZ rWLwF5c2f+1MoLmaPPd5GLTXx21gZrcwFm63K4zRdZScScG6CcCqpkjYxIOmR8Zsj6c3 mUTRAuUals5NX8wyeBbAdUsIDzHmTMITWeJdscCiTkUynAgMZb+qkABkjv9ScPfRVMlX kDZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uvA3fGAsdpLDdGT7prfLw2pioa5b3oG//gCXXxhEucc=; b=Zb5TkDD5af/Ej9H1OfFty+WsoDmURQHEA7N8UY9J/twWToShIYB2z4GikH8ugJNdrA UJddI86vOLE2HDKWZxtHfGkLz90ostQpDbhBHZj6JxlBxOf7Wt9qaZgN69X1qUj4pOaB DMmjnYa7U+fO4x9biJbOIcWW3fiIMs2HRL/4IWbqBvKrSDSmZZnwL70qmZbCtVp0PUsC tuDd1TVleY4BeeoR5xLQMKP5oRjBULqwfilmkDc+UrhLZBo1qSZ01cXGrmjH9DGWYwRM eH9/r9yRDQVidOUg6M8i5yiUb1N+o+/PL2fP7SmVlgadmy27NS7f35Wr/TTlDQuGwXpH bn+g== X-Gm-Message-State: AKGB3mJqFxTUl2oVvcXHxrEhkjXjmAfoG0KqTTWbcRncWkS0gl8n8fr0 18VO3umWMvOr9xLXFzEa4XlansLlxUwWBZq0UmCv/A== X-Google-Smtp-Source: ACJfBot+GtUyG647L4M7S8CYeL3OSla214YMwGP3b5GbLRMSGCNh6ORw9oVQqJ9Rx/7OLz9nAhCfKJvfS6aVVQNLfLo= X-Received: by 10.223.128.195 with SMTP id 61mr740582wrl.122.1513776706555; Wed, 20 Dec 2017 05:31:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.197.68 with HTTP; Wed, 20 Dec 2017 05:31:06 -0800 (PST) In-Reply-To: <0ecaf46d-e7bc-04cd-212a-bc0606cc7eec@evnbug.org> References: <0ecaf46d-e7bc-04cd-212a-bc0606cc7eec@evnbug.org> From: Johannes Lundberg Date: Wed, 20 Dec 2017 13:31:06 +0000 Message-ID: Subject: Re: Vote: making wayland=on default To: FreeBSD Cc: antranigv Content-Type: text/plain; charset="UTF-8" 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: Wed, 20 Dec 2017 13:31:49 -0000 On Wed, Dec 20, 2017 at 1:13 PM, antranigv wrote: > Hi! > > Trying to understand the changes that would be made by making wayland=on > by default. > > I see a lot of people moving to Wayland from X, but if we do wayland=on, > what will this mean to Xorg people? from the first thing I got is larger > binaries for gtk and Qt. anything else that will happen? please fill me > in, I'd love to vote wayland=on by default if people think it's the > future, but without hurting people who still use and like Xorg. > Hi! Yes, libraries that are common for X and Wayland like mesa-libs, qt5 and gtk30 will get a bit bigger in order to enable Wayland. This is completely transparent to X users and does not affect X-related stuff in anyway. Using Wayland compositors like x11-wm/sway or x11-wm/weston is still completely optional and can they can co-exist with any X server and X11 window manager. Simply run "startx" if you wanna run X or "weston-launch" if you wanna run weston. Any X client should run fine in Weston (requires the pkg "xwayland"), however the opposite is not true. > Thanks in advance, > > antranigv > https://antranigv.am/ | PGP Key ID : 0xDAB81456 > /* do one thing and do it well */ > > On 12/20/2017 01:20 PM, Johannes Lundberg wrote: >> Hi >> >> I want to suggest that we enable wayland by default. In current state >> having some parts of wayland in ports is basically useless the >> end-users themselves re-build gtk30 and mesa-libs with wayland >> enabled. >> >> libwayland-egl.so from mesa-libs and the extra libraries and headers >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >> packages. (might be something more that I missed) >> >> Personally I see no reason not to make it default on, even with >> flavors coming up. For any Desktop user (as well as embedded devices >> like IVI-systems and whatnot), Wayland is the future. There's no >> escaping that. >> >> Wayland has been quite usable on FreeBSD for over a year now but >> access to it is limited due to the extra efforts required to use it. >> >> If we are to compare with the other guys, several Linux distros are >> already switching to wayland-based compositors as default window >> server. >> >> What do you think? >> >> >> /Johannes >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >> From owner-freebsd-ports@freebsd.org Wed Dec 20 14:12:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FBB7E8B43F for ; Wed, 20 Dec 2017 14:12:54 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7A6E6EE72 for ; Wed, 20 Dec 2017 14:12:53 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-it0-x243.google.com with SMTP id t1so6865763ite.5 for ; Wed, 20 Dec 2017 06:12:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FGm1KAqLW0rhITHfV/vdKbXl7szaV0jEavE1lT61zfo=; b=NDI16e2iVHQ+wdmC/dxAT7osx53Cu/Eg1ro2tlEWfjj397Kc10NZive144H4NFbHb8 2Z2JaZLkXso8MxZCGf5jVKDzRWivP8uBMvTlEqLJTXLGDWtH0e5rFciEcnXfaG7Dbpw2 KBC+WC1E4BAsNs0sCECgnZT+DFZtlgu4z755glbIaDtOtGR79cWwWghNONsrmDHkedgB J7Wo5f6UCs7a0RN6e/qDGr4C6rtxnV+EGi5OqLYhyoyOpGO9FNcUxIesGjiAbWJ0Myz1 p43papj3N8+bKuR6fZNl7YgU1sK23HiFBCJH9gXwxrDLdwUh4s4W7fp9//MbVt0f26sf WssA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FGm1KAqLW0rhITHfV/vdKbXl7szaV0jEavE1lT61zfo=; b=YYrsG0+LqZaZfMoxKnP1f0ymkskVfrxRCCKSOWKs3+evmj3LFC+MCMkl0QcRU8kfEU 7qWX76vCx1eW/P9JR+L6jOkWs7cF0BqsbRG5urOoea9NWxXEvMxs9DsJ66IZi4At/UqX RAPrm6+9kvTvx+l+P+hIsaaZtC6QPdZhVOSFbGVwFjJTs45J7CNGFzf06XkDnetHiaBp BMoq5Set3a7m2UyvdC0qrtm9f2ZqTfEOlnB0MRV1FSR1rJtNEMfKlhwk955POVodIC4b wnc9RxWwcX9Wj0+9ucvdjsXHqCtaDLNP00VJmgKmlLHNf/hWCWg/EXS4WmHlglClMyPo iNUg== X-Gm-Message-State: AKGB3mIxkLdhpVPxv2/pJqaCyEwIa3fovwX7fpGe26sDMREK4F14AfuW buk+ChplPJsP+16vt7BAZO8O7gwE/ehyDYHKMdw= X-Google-Smtp-Source: ACJfBounxeu3bNwcATmcUcsIn9eA8bEF/EMm6aUokQOZRFwUw/mX9i1RQcYroNdaRH2VVspZ7Rxo3bF+RP6z6lMsdDo= X-Received: by 10.36.39.8 with SMTP id g8mr8563710ita.42.1513779173168; Wed, 20 Dec 2017 06:12:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.180.34 with HTTP; Wed, 20 Dec 2017 06:12:52 -0800 (PST) In-Reply-To: <20171216200959.GA97697@wstan> References: <20171216094058.GA37778@wstan> <5A351515.1080805@quip.cz> <20171216135919.GA17551@wstan> <5A352BA5.9070403@quip.cz> <20171216170411.GA85559@wstan> <20171216185317.GA87289@wstan> <20171216200959.GA97697@wstan> From: Adam Vande More Date: Wed, 20 Dec 2017 08:12:52 -0600 Message-ID: Subject: Re: Setting system user home directory To: Dmytro Bilokha Cc: Kevin Oberman , Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD Ports ML Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 14:12:54 -0000 On Sat, Dec 16, 2017 at 2:10 PM, Dmytro Bilokha wrote: > Guys, thanks for your help. I've managed to adjust user's homedir > using pkg-install script. Now I'll try to move everything writable > from /usr/local to /var (as Miroslav suggested), test and submit the new > port version. I think you should do what makes sense for your application. The /var/db stuff is not a hard fast rule and it doesn't work well for many situations. Also it's mostly system related DB's that live there. It's not only some java related ports that live mostly under /usr but also things like postgres(at least used to). IMO, as long as you're not flagrantly violating hier(7), do what is best for your port. -- Adam From owner-freebsd-ports@freebsd.org Wed Dec 20 15:54:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF54EE914BA for ; Wed, 20 Dec 2017 15:54:46 +0000 (UTC) (envelope-from SRS0=4vMs=DQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 778217496F for ; Wed, 20 Dec 2017 15:54:45 +0000 (UTC) (envelope-from SRS0=4vMs=DQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7315528428; Wed, 20 Dec 2017 16:54:37 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 21FD828423; Wed, 20 Dec 2017 16:54:36 +0100 (CET) Subject: Re: Setting system user home directory To: Adam Vande More , Dmytro Bilokha Cc: Kevin Oberman , FreeBSD Ports ML References: <20171216094058.GA37778@wstan> <5A351515.1080805@quip.cz> <20171216135919.GA17551@wstan> <5A352BA5.9070403@quip.cz> <20171216170411.GA85559@wstan> <20171216185317.GA87289@wstan> <20171216200959.GA97697@wstan> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5A3A87BB.4020603@quip.cz> Date: Wed, 20 Dec 2017 16:54:35 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 20 Dec 2017 15:54:46 -0000 Adam Vande More wrote on 2017/12/20 15:12: > On Sat, Dec 16, 2017 at 2:10 PM, Dmytro Bilokha wrote: > >> Guys, thanks for your help. I've managed to adjust user's homedir >> using pkg-install script. Now I'll try to move everything writable >> from /usr/local to /var (as Miroslav suggested), test and submit the new >> port version. > > > I think you should do what makes sense for your application. The /var/db > stuff is not a hard fast rule and it doesn't work well for many > situations. Also it's mostly system related DB's that live there. It's > not only some java related ports that live mostly under /usr but also > things like postgres(at least used to). Databases (Postgres) are mess. MySQL, CouchDB, Elasticsearch and others are using /var/db prefix, PostgreSQL and some others are using /usr/local. It is very inconsistent... Miroslav Lachman From owner-freebsd-ports@freebsd.org Wed Dec 20 16:06:32 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48F0BE92042 for ; Wed, 20 Dec 2017 16:06:32 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1DAA0751E4 for ; Wed, 20 Dec 2017 16:06:31 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vBKG8PoK064149; Wed, 20 Dec 2017 08:08:31 -0800 (PST) (envelope-from portmaster@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: In-Reply-To: From: "Chris H" Reply-To: portmaster@BSDforge.com To: "Johannes Lundberg" Subject: Re: Vote: making wayland=on default Date: Wed, 20 Dec 2017 08:08:31 -0800 Message-Id: <0bc4b9b1d25db922415413bfa84375d7@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable 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: Wed, 20 Dec 2017 16:06:32 -0000 On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" = said > Hi >=20 > I want to suggest that we enable wayland by default=2E In current state > having some parts of wayland in ports is basically useless the > end-users themselves re-build gtk30 and mesa-libs with wayland > enabled=2E >=20 > libwayland-egl=2Eso from mesa-libs and the extra libraries and headers > from gtk30 adds like a few KB, a drop in the ocean compared to xorg > packages=2E (might be something more that I missed) >=20 > Personally I see no reason not to make it default on, even with > flavors coming up=2E For any Desktop user (as well as embedded devices > like IVI-systems and whatnot), Wayland is the future=2E There's no > escaping that=2E >=20 > Wayland has been quite usable on FreeBSD for over a year now but > access to it is limited due to the extra efforts required to use it=2E >=20 > If we are to compare with the other guys, several Linux distros are > already switching to wayland-based compositors as default window > server=2E >=20 > What do you think? IMHO it's (still) too early=2E Too much other X(org) related work still being completed=2E In fact, I just built a new dev box to track 12 (CURRENT), and this was the first time I was not required to pre generate a config file for Xorg=2E I was only required to inform /usr/local/etc/X11/xorg=2Econf=2Ed/nvidia-driver=2Econf that the driver was "nvidia", not "nv"=2E Everything work(s|ed) famously=2E A real treat=2E I'm also a bit concerned about the progress (or lack there of) on network transparency=2E I (personally) could conceive it as a KERNEL OPTION, but would not want to see it in the Default kernel=2E Well, those are *my* thoughts=2E Because you asked=2E :-) --Chris >=20 >=20 > /Johannes From owner-freebsd-ports@freebsd.org Wed Dec 20 16:24:41 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2D3AE92FB1 for ; Wed, 20 Dec 2017 16:24:41 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57AF375B3B for ; Wed, 20 Dec 2017 16:24:41 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id f140so10811089wmd.2 for ; Wed, 20 Dec 2017 08:24:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4f5eCxFjfa5MntZhto36VC9hll0E/krLAWoJ6FTLFJs=; b=BEBi3BzCVYOnkbS6hwp/T7Kkas8X80G9WrDs3Iu8msrjdDGiowrThHLkq7OIf8KL/p W0SaTCAQnB6u1DG4Bm8dKMCDjIGQ++gvRBKP9n73QpORFLt4JoYHabDiW8R+m3RHy3Rv jJQJb3BMdHAY4EdBkoljRHN+loGeeoIHedW0Sllq2xD0XnbXVeFPj+xee+C9exyy4Xgz HAhBMTyy2bvguIF7nqPwsc+JLhxkBYDQBnZTR7xCr8yV2lo7Zjs/Be3XHDSv0VWEL4Pd utQ3UX2jgSdAYx6wkklJ8JpxGqRs/E5RYx9hMiQ8REx4Jz5o6O7G/ibKp1/iG/UJHITq 2Z2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4f5eCxFjfa5MntZhto36VC9hll0E/krLAWoJ6FTLFJs=; b=DJeAFbLHZyHHWCO1kc7einPZCSUHDUzRrl0rTv6zMhLomcsVnfBouirOsVYA2BVKdB MHvV7C7iZGqTwAws6yLQ/Vqjg7NlHzOED7zzZLz4NDqbXUvzqJuM2L+p+PTMHYSL6RIm +Hh0hEPu/RzGfHM5wupcRBuk/QRAuWFqtTCiVXglCQLF7bUvLkaZjLicerrB5c1GbR0N 6HtCSbtR0QyF7mexOxq5qMBebs3FYRJBC5I722b1pIdVo3aBmDS9ufiT++d/qlqVwqxI xO5m0b7un1teASLLJzZVAxM/8kKJH2klTfF4LNr7TcHE0+qV92mqApoaXgUgfESzqn7P CYiw== X-Gm-Message-State: AKGB3mLMFiy6driUgpGY6mmHlwjzOA7wtjauVDF2tN7CNGnCWP++L8fY I+FvDzsbutQUo5gy3DcOssT1xBaFPSgY33Xb9Kk= X-Google-Smtp-Source: ACJfBovMwzipaHG7F6NE4GCsQIuqA/nXy7ereZgIjI+qnBvEDMG8zhuWMLJDdLqkqeaA89j11CuNRLONsskO/2iT/GM= X-Received: by 10.28.62.20 with SMTP id l20mr7648297wma.6.1513787079783; Wed, 20 Dec 2017 08:24:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.197.68 with HTTP; Wed, 20 Dec 2017 08:23:59 -0800 (PST) In-Reply-To: <0bc4b9b1d25db922415413bfa84375d7@udns.ultimatedns.net> References: <0bc4b9b1d25db922415413bfa84375d7@udns.ultimatedns.net> From: Johannes Lundberg Date: Wed, 20 Dec 2017 16:23:59 +0000 Message-ID: Subject: Re: Vote: making wayland=on default To: portmaster@bsdforge.com Cc: FreeBSD Content-Type: text/plain; charset="UTF-8" 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: Wed, 20 Dec 2017 16:24:41 -0000 On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote: > On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" > said > >> Hi >> >> I want to suggest that we enable wayland by default. In current state >> having some parts of wayland in ports is basically useless the >> end-users themselves re-build gtk30 and mesa-libs with wayland >> enabled. >> >> libwayland-egl.so from mesa-libs and the extra libraries and headers >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >> packages. (might be something more that I missed) >> >> Personally I see no reason not to make it default on, even with >> flavors coming up. For any Desktop user (as well as embedded devices >> like IVI-systems and whatnot), Wayland is the future. There's no >> escaping that. >> >> Wayland has been quite usable on FreeBSD for over a year now but >> access to it is limited due to the extra efforts required to use it. >> >> If we are to compare with the other guys, several Linux distros are >> already switching to wayland-based compositors as default window >> server. >> >> What do you think? > > IMHO it's (still) too early. Too much other X(org) related work > still being completed. In fact, I just built a new dev box to > track 12 (CURRENT), and this was the first time I was not required > to pre generate a config file for Xorg. I was only required to > inform /usr/local/etc/X11/xorg.conf.d/nvidia-driver.conf that > the driver was "nvidia", not "nv". Everything work(s|ed) famously. > A real treat. I'm also a bit concerned about the progress (or lack > there of) on network transparency. > I (personally) could conceive it as a KERNEL OPTION, but would not > want to see it in the Default kernel. > > Well, those are *my* thoughts. Because you asked. :-) > > --Chris > Thanks for your feedback! Just to clarify, we're not talking about changing any defaults that would impact or change users' choice of desktop. We only want to enable Wayland compositors as an alternative to X (leaving X as is). This does not break or modify anything existing. It does not force you to do anything differently. It simply adds a couple of libraries that you won't use unless you run Wayland stuff (if you install qt5/gtk30 and mesa-libs). The reference to Linux making it default might have been unclear. Since FreeBSD doesn't have a default desktop, it's hard to change. It is and will continue to be up to the end user what they choose to use, we only add more options :) >> >> >> /Johannes > > > From owner-freebsd-ports@freebsd.org Wed Dec 20 16:31:08 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1EEAE9353B for ; Wed, 20 Dec 2017 16:31:08 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8807575DD7 for ; Wed, 20 Dec 2017 16:31:08 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x233.google.com with SMTP id o130so11965616itg.0 for ; Wed, 20 Dec 2017 08:31:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SOENlLD1apXfMvMWclANYfjDj2Kd4VNFoNiUMtbfaMs=; b=dYMTTQpxPndwAT2TjAjnZJG7sQ5+uSZG4ccUtvEmDcEDynJQJVyPvn1GF9Ud7PkgUn 2HQxc0sq1VJSXyFniBVnjHFrSBBopuxuDVqkg84KKCSc+wLg0U6Lr4akqCFuTbxAN7dQ 8mDfaw42lnT6CMxGrv101v7w10HXNy6TwNhQlooFX1Z5l0KjOvSoDExfhs/zeEd6oO+k 7N8UTftmHZKzWOWFI5XtIyjqzBPckpyGImFBlleoJ+Y7kvfVpOabJSYErwR5IPThRnMs GIF0K5BIoaIR21v0BK+TPAvmUCQqcUjtSLawrzMgMchzkcdWJAURkFAEAwmIfELvJKbb 2IrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SOENlLD1apXfMvMWclANYfjDj2Kd4VNFoNiUMtbfaMs=; b=qRmysJD5mW298fi9OS1Ckhgtz5KHZqPXtZuYIA24uwZjuRwiMHLBrJdfwi8tqqeely CD/vX720MHoHfSFZt7ELbqia2SGNuXh61l7Y62jdXzCN8qa5WCACVJqZlqNfpsPcIveh dPue8TLZtmbg6klL0vLGKApD1wfN1AMTq4EVGrFFi4QhDyi34rsSWHCJPsQII2LKcBEO zGTOK4mag3Nsp81oCbp21TF3c0ZXqruAdj+HQ1ehS1JEjjBovCd17BuCKACcNJniPgnL 4MYYmIgfkIxS3wGYYYE23rRjhvnjHJehc+qqMa+yRDZ6QbvHz6cyNs457jLKE9gblxjF 1CWg== X-Gm-Message-State: AKGB3mKhsaoNo88IYaV6GVtfQBLrxJiRJoUtYtuRe7/KI1xbp9eLzaH/ uFD6UgnKJZgo8xz/qPh5MuD+IFUV5k6d38SWBxs= X-Google-Smtp-Source: ACJfBotsyiXEWgGrs/BqBctqC8k/xFeU8T/Ri3FNGrUZEC6UhEpbItv4mMB/mrwLCsQ3Gk8YP2Q27rhtX3SlL3ey14c= X-Received: by 10.36.221.147 with SMTP id t141mr8648652itf.140.1513787467618; Wed, 20 Dec 2017 08:31:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Wed, 20 Dec 2017 08:31:06 -0800 (PST) In-Reply-To: References: <0bc4b9b1d25db922415413bfa84375d7@udns.ultimatedns.net> From: blubee blubeeme Date: Thu, 21 Dec 2017 00:31:06 +0800 Message-ID: Subject: Re: Vote: making wayland=on default To: Johannes Lundberg Cc: Chris H , FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 16:31:08 -0000 On Thu, Dec 21, 2017 at 12:23 AM, Johannes Lundberg wrote: > On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote: > > On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" < > johalun0@gmail.com> > > said > > > >> Hi > >> > >> I want to suggest that we enable wayland by default. In current state > >> having some parts of wayland in ports is basically useless the > >> end-users themselves re-build gtk30 and mesa-libs with wayland > >> enabled. > >> > >> libwayland-egl.so from mesa-libs and the extra libraries and headers > >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg > >> packages. (might be something more that I missed) > >> > >> Personally I see no reason not to make it default on, even with > >> flavors coming up. For any Desktop user (as well as embedded devices > >> like IVI-systems and whatnot), Wayland is the future. There's no > >> escaping that. > >> > >> Wayland has been quite usable on FreeBSD for over a year now but > >> access to it is limited due to the extra efforts required to use it. > >> > >> If we are to compare with the other guys, several Linux distros are > >> already switching to wayland-based compositors as default window > >> server. > >> > >> What do you think? > > > > IMHO it's (still) too early. Too much other X(org) related work > > still being completed. In fact, I just built a new dev box to > > track 12 (CURRENT), and this was the first time I was not required > > to pre generate a config file for Xorg. I was only required to > > inform /usr/local/etc/X11/xorg.conf.d/nvidia-driver.conf that > > the driver was "nvidia", not "nv". Everything work(s|ed) famously. > > A real treat. I'm also a bit concerned about the progress (or lack > > there of) on network transparency. > > I (personally) could conceive it as a KERNEL OPTION, but would not > > want to see it in the Default kernel. > > > > Well, those are *my* thoughts. Because you asked. :-) > > > > --Chris > > > > Thanks for your feedback! > > Just to clarify, we're not talking about changing any defaults that > would impact or change users' choice of desktop. We only want to > enable Wayland compositors as an alternative to X (leaving X as is). > > This does not break or modify anything existing. It does not force you > to do anything differently. It simply adds a couple of libraries that > you won't use unless you run Wayland stuff (if you install qt5/gtk30 > and mesa-libs). > > The reference to Linux making it default might have been unclear. > Since FreeBSD doesn't have a default desktop, it's hard to change. It > is and will continue to be up to the end user what they choose to use, > we only add more options :) > > >> > >> > >> /Johannes > > > > > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > I'd +1 to this From owner-freebsd-ports@freebsd.org Wed Dec 20 16:55:29 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A506E94DA1 for ; Wed, 20 Dec 2017 16:55:29 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B51D176ECF for ; Wed, 20 Dec 2017 16:55:28 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa16.server.lan (via HTTP); Wed, 20 Dec 2017 17:55:21 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: freebsd-ports@freebsd.org Subject: re: Vote: making wayland=on default Content-Type: text/plain; charset=UTF-8 Date: Wed, 20 Dec 2017 17:55:21 +0100 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:dashr4hAsAmsK1sv1NdNxAAMJK0jKRIEz1AzGMJONJp ilYPgZZsk4NYIEIBzdcjMNPfPfbnq3I0jrGNMTwISPhbdyaUwl RLKPdofZXcYLt7OEUGhSIdNsSD2uK6ESKSs/h3WRcKSoT9F2d9 KbVlbF+qXRQzbUtpGtCCmwOD9uUcQ20MATSosRREeX3Dw3q52H OjCx7oap5qR+VIhUVwRyHSVny+EOZN90EJ9FW4yQewpNwCR3K8 lssUfhl3+U5a2+MLZMdwh1Y1HRkmbXOVc4zs6vRgkl4oZNIh1m vLiKos= X-UI-Out-Filterresults: notjunk:1;V01:K0:gZRRrID02bk=:uujh9xQStKnxUQwuYXetT2 8eZadazi5miWscHorqB/poYbKOUwoSEVsB1f6yKjaQ/37O69pHayOVnqBUexvROkrf7pbp6+L 2ugXrFC/7zBvTauW5Vlxzq3jxWuL1rietVkNbsNjkCNxKYUMuOS5RYllinMWWgplhFXX3/PIO lCgiCcap0EU0mHmeQuD9YLGosz7KHsk5EQfzWVZp2JJ8z0gbvMLGHpvsCy0/+bKZLVlL3GxPC BRPJZAN0UZ7F3F8MucYYSyjSF3v+cdWP6cxhhFgyhOcAC8dAPEIAHf7Ixmm+v2nkI0YGqTr7b LABqAWPy7chgj9PLQLaFf6mBAuyjW5afLmSrPYtSOmHj9kmmxX5Oj8ptNDZ3PXvGkavEyOICP woR+2wk2zS14h5gl7xeVbJVgzTDuCDv91OaqcXK8LkeC/j8OvsyRXq2y+X9W+bDlfYsmjguGC B8XBuyX8u76EvG+G2hmW38Kt9WKPbvCMoHoRoqbg08296pnjMLjebvpiuOI1/2vosZuWuBpDH u/Gn9stZrMjr55kSxSj1Jy3o+nmMB0nCgREfOUgQmhB 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: Wed, 20 Dec 2017 16:55:29 -0000 I would rather see smaller window managers work with Wayland first. If gtk2 and gtk3 want to enable it fine. But gtk2 and gtk3 shouldn't be mixed in with Wayland by default, which is what will happen if it is enabled before it gets a foothold with other window managers. From owner-freebsd-ports@freebsd.org Wed Dec 20 17:39:10 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78409E98670 for ; Wed, 20 Dec 2017 17:39:10 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 641F97903C for ; Wed, 20 Dec 2017 17:39:10 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id vBKHd3eK068379 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 20 Dec 2017 09:39:03 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: Vote: making wayland=on default To: Johannes Lundberg , freebsd-ports@freebsd.org References: From: Yuri Message-ID: <3267de19-6e00-a72a-e2a7-abb322ccf7ac@rawbw.com> Date: Wed, 20 Dec 2017 09:39:02 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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: Wed, 20 Dec 2017 17:39:10 -0000 On 12/20/17 01:20, Johannes Lundberg wrote: > For any Desktop user (as well as embedded devices > like IVI-systems and whatnot), Wayland is the future. There's no > escaping that. Over the history of its development, Wayland could never clearly answer the question "What are the benefits of Wayland for the end user?". Additionally, they always advocated the removal of features like networked connections, window manager features. It appears that this is the case of fixing of something (xorg) that wasn't/isn't broken in the first place. And if it is considered broken, then how, in which way? But you are right, it is a reality that Wayand devs had enough horsepower to eventually, after many years, make it and now impose it on everybody, and force it to be a future reality. There are a lot of things that need to be verified that they work: x11vnc, the ability to connect to a display remotely, every window manager should work with it, ex. xfce4, dwm. People should be asking the question "What's the benefit of the transition to X?". The answer should include the functional benefits to users, not just "We need to switch to something called X." What new features or improvements will users actually see? Just my 2c. Yuri From owner-freebsd-ports@freebsd.org Wed Dec 20 17:48:44 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16AB6E98FB1 for ; Wed, 20 Dec 2017 17:48:44 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0071679650 for ; Wed, 20 Dec 2017 17:48:43 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vBKHoctQ070066 for ; Wed, 20 Dec 2017 09:50:44 -0800 (PST) (envelope-from portmaster@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 In-Reply-To: From: "Chris H" Reply-To: portmaster@BSDforge.com To: Subject: Re: Vote: making wayland=on default Date: Wed, 20 Dec 2017 09:50:44 -0800 Message-Id: <9142f3e2938c84bd838b3764197226be@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable 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: Wed, 20 Dec 2017 17:48:44 -0000 On Wed, 20 Dec 2017 17:13:43 +0000 said On Wed, 20 Dec 2017 16:23:59 +0000 "Johannes Lundberg" said > On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote: > > On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" > > > said > > > >> Hi > >> > >> I want to suggest that we enable wayland by default=2E In current state > >> having some parts of wayland in ports is basically useless the > >> end-users themselves re-build gtk30 and mesa-libs with wayland > >> enabled=2E > >> > >> libwayland-egl=2Eso from mesa-libs and the extra libraries and headers > >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg > >> packages=2E (might be something more that I missed) > >> > >> Personally I see no reason not to make it default on, even with > >> flavors coming up=2E For any Desktop user (as well as embedded devices > >> like IVI-systems and whatnot), Wayland is the future=2E There's no > >> escaping that=2E > >> > >> Wayland has been quite usable on FreeBSD for over a year now but > >> access to it is limited due to the extra efforts required to use it=2E > >> > >> If we are to compare with the other guys, several Linux distros are > >> already switching to wayland-based compositors as default window > >> server=2E > >> > >> What do you think? > > > > IMHO it's (still) too early=2E Too much other X(org) related work > > still being completed=2E In fact, I just built a new dev box to > > track 12 (CURRENT), and this was the first time I was not required > > to pre generate a config file for Xorg=2E I was only required to > > inform /usr/local/etc/X11/xorg=2Econf=2Ed/nvidia-driver=2Econf that > > the driver was "nvidia", not "nv"=2E Everything work(s|ed) famously=2E > > A real treat=2E I'm also a bit concerned about the progress (or lack > > there of) on network transparency=2E > > I (personally) could conceive it as a KERNEL OPTION, but would not > > want to see it in the Default kernel=2E > > > > Well, those are *my* thoughts=2E Because you asked=2E :-) > > > > --Chris > > >=20 > Thanks for your feedback! >=20 > Just to clarify, we're not talking about changing any defaults that > would impact or change users' choice of desktop=2E We only want to > enable Wayland compositors as an alternative to X (leaving X as is)=2E >=20 > This does not break or modify anything existing=2E It does not force you > to do anything differently=2E It simply adds a couple of libraries that > you won't use unless you run Wayland stuff (if you install qt5/gtk30 > and mesa-libs)=2E >=20 > The reference to Linux making it default might have been unclear=2E > Since FreeBSD doesn't have a default desktop, it's hard to change=2E It > is and will continue to be up to the end user what they choose to use, > we only add more options :) Thanks for the informative reply, Johannes=2E So no kernel (libs/extensions)? Hmm, gtk3=2E Why is it not possible to make the Wayland stuff a sub package/option? I think this is the preferred track/policy anyway=2E I do this for all the ports I currently maintain=2E IOW any DE related stuff I install, that uses GNOME related material, will pull in gtk3, which, as I understand you say, will ultimately pull in Weston,mesa,=2E=2E=2E is that correct? While I understand, you indicate it's only a few Kb=2E I think it's cruft/(unnecessary)overhead=2E Which, in and of itself seems insignificant=2E But in the "big picture", and over many (100's) of builds/installations, is *not* insignificant=2E This also dismisses the security related work, maintaining extra un(used|needed) material=2E I suppose some will think that I'm just being nit-picky=2E But IMHO I'm not=2E This sort of thing, if overlooked, *does* affect the bottom line=2E Thanks again, Johannes! P=2ES=2E I have nothing against Wayland=2E I'm just not ready to run it on anything "production" related, just yet=2E :-) --Chris >=20 > >> > >> > >> /Johannes > > > > >> From owner-freebsd-ports@freebsd.org Wed Dec 20 19:15:24 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3494E9E02A for ; Wed, 20 Dec 2017 19:15:24 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E5C107D2D6 for ; Wed, 20 Dec 2017 19:15:23 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id i11so11701048wmf.4 for ; Wed, 20 Dec 2017 11:15:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xsG2BaS1FllvSA+rymjL63+w1U8TUpxZ/i/PIzrn1b4=; b=Nk1ih/jMK4XnD0mjHTTrdCU2yOrvmhYUk0WcKKkERqMPbSMEqKmln58rcVcFAkXTYr IrKwxLud1E0ZrH6kP/JblrSZKiSuFXHmcnP2cjTNAD6T8iK9b/tR/F/liw1/JfzH5P/8 e9uUS8j+BVond1JZoflgfskmUHqSu8evkwaO8F4cVvXGoupP0h23czfwp9pAXIaAZChW yszL4o7WxRR+aA0cQUMzMg0aHmMDp+4UbVMAcWSlJiXjexvqeDsIWsqRH2iI9s1/4lqn ht8BBGm+tAfaKpby035jGEbjOd75wWr4dgoWDegjY65YSpA8mMxlS0B9hmrvE8b2uVz6 08Ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xsG2BaS1FllvSA+rymjL63+w1U8TUpxZ/i/PIzrn1b4=; b=bbF+W63Es3JUBC5iTnyd65QSlWNH+5TjGscpzsx2mvdLBv8BoUecxsHQkUatB/Q2Xa 4tFc5HzorLC3cQ7c11UpWydzVAewLYIm0BJ5TJxOPWh4utMvl4qyyImUt4rq7hyTTYZI dAzLtCX7zYIjVZgwKPOQYMMrFN5SdNy3uRLbOQchmzqLK9hR1w0v5TXbv0u36AQ5POjE ioyoGFC++LlJ2M0w9YTo9YdvzQczsLvu+sTCQ0yZxN6KNRdMMPY1CYdtZ8++BVaE/gUu 4y+N37JzcvFoae2Mi90ZR99Y6aXzDIBjutDu6VCUa4U1NZVc2ZlL1Fw3CeIPqLN38WdH PeCw== X-Gm-Message-State: AKGB3mIQuLPcZye4owEPZln4o0JSG9HjT6PuP3zf6WpYIIj059I4VxDr 8UzxNPZklQOonjpkBp3On7DmpNCiRUIuK8Um68k= X-Google-Smtp-Source: ACJfBot/Xtm5cCeojjATv/rbBprV7ZztJdMN0LbNLOT0oEO0FAqT3l/pb1GwcBn7JhKJGn0V5SwxGCrDZ1E2w+EAlRg= X-Received: by 10.28.55.201 with SMTP id e192mr1334839wma.1.1513797321196; Wed, 20 Dec 2017 11:15:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.197.68 with HTTP; Wed, 20 Dec 2017 11:14:40 -0800 (PST) In-Reply-To: <3267de19-6e00-a72a-e2a7-abb322ccf7ac@rawbw.com> References: <3267de19-6e00-a72a-e2a7-abb322ccf7ac@rawbw.com> From: Johannes Lundberg Date: Wed, 20 Dec 2017 19:14:40 +0000 Message-ID: Subject: Re: Vote: making wayland=on default To: Yuri Cc: FreeBSD Content-Type: text/plain; charset="UTF-8" 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: Wed, 20 Dec 2017 19:15:25 -0000 Hi Yuri To be clear, we're not transitioning to anything, we're simply adding more options. Compare it to adding a new window manager for X, it doesn't mean you have to stop using the existing ones... On Wed, Dec 20, 2017 at 5:39 PM, Yuri wrote: > On 12/20/17 01:20, Johannes Lundberg wrote: >> >> For any Desktop user (as well as embedded devices >> like IVI-systems and whatnot), Wayland is the future. There's no >> escaping that. > > > Over the history of its development, Wayland could never clearly answer the > question "What are the benefits of Wayland for the end user?". > Additionally, they always advocated the removal of features like networked > connections, window manager features. > > It appears that this is the case of fixing of something (xorg) that > wasn't/isn't broken in the first place. And if it is considered broken, then > how, in which way? > > But you are right, it is a reality that Wayand devs had enough horsepower to > eventually, after many years, make it and now impose it on everybody, and > force it to be a future reality. > > There are a lot of things that need to be verified that they work: x11vnc, > the ability to connect to a display remotely, every window manager should > work with it, ex. xfce4, dwm. > > People should be asking the question "What's the benefit of the transition > to X?". The answer should include the functional benefits to users, not just > "We need to switch to something called X." What new features or improvements > will users actually see? > > > Just my 2c. > Yuri > From owner-freebsd-ports@freebsd.org Wed Dec 20 19:22:32 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CF7AE9E9F1 for ; Wed, 20 Dec 2017 19:22:32 +0000 (UTC) (envelope-from dmytro@posteo.net) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.posteo.de", Issuer "StartCom Class 3 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE9457DADB for ; Wed, 20 Dec 2017 19:22:31 +0000 (UTC) (envelope-from dmytro@posteo.net) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id EBC8420E39 for ; Wed, 20 Dec 2017 20:22:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1513797748; bh=JP+lA9usS7nS7G6ewH7kCu+tRJIKv0CP11mFJBxITnA=; h=Date:From:To:Cc:Subject:From; b=JGy/R62xCoHiQy18jo5/VJeKoaA2JRt6LLFFEtljNj7ILjv5cBYlm/iVWuMYaZUeo 8I5xk7SukQiYt2KHOUNqx1/lklXsUk7A1Q+cEKr0r3xJb2PmchBYagZyAEWveYkiNP WJrIrlmwg8dZClj3saLQeWK0VJHDQD7a4e5HGZoc/GCemp/U6qgYEde43kmurhnJSw JFJw9wXm3vj7OCFkj+OUw5wewqlPlqofM726X0Sy4dxrG0TR575AwbLMIASWxEck+E 1a3T3m4/lmkg4NHmJ7HxXeGGDOq1PHL/qo/Hw8Kg4nsgLJVYtYQVKqadekNkVMmS0K zYApHq7cVas3A== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3z24R60Tx7z9rxL; Wed, 20 Dec 2017 20:22:26 +0100 (CET) Date: Wed, 20 Dec 2017 21:22:23 +0200 From: Dmytro Bilokha To: Adam Vande More Cc: Kevin Oberman , Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD Ports ML Subject: Re: Setting system user home directory Message-ID: <20171220192222.GA4690@wstan> References: <20171216094058.GA37778@wstan> <5A351515.1080805@quip.cz> <20171216135919.GA17551@wstan> <5A352BA5.9070403@quip.cz> <20171216170411.GA85559@wstan> <20171216185317.GA87289@wstan> <20171216200959.GA97697@wstan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) 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: Wed, 20 Dec 2017 19:22:32 -0000 On Wed, Dec 20, 2017 at 08:12:52AM -0600, Adam Vande More wrote: >On Sat, Dec 16, 2017 at 2:10 PM, Dmytro Bilokha wrote: > >> Guys, thanks for your help. I've managed to adjust user's homedir >> using pkg-install script. Now I'll try to move everything writable >> from /usr/local to /var (as Miroslav suggested), test and submit the new >> port version. > > >I think you should do what makes sense for your application. The /var/db >stuff is not a hard fast rule and it doesn't work well for many >situations. Also it's mostly system related DB's that live there. It's >not only some java related ports that live mostly under /usr but also >things like postgres(at least used to). > >IMO, as long as you're not flagrantly violating hier(7), do what is best >for your port. > >-- >Adam Thanks for your response. For me both approaches are fine, application will work. As far as I understand, which layout is better depends on how the system is managed. For now having writable data in /var seems reasonable, so I'll try it. -- Dmytro Bilokha dmytro@posteo.net +38-050-607-41-43 From owner-freebsd-ports@freebsd.org Wed Dec 20 19:32:47 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04C3EE9F2E9 for ; Wed, 20 Dec 2017 19:32:47 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (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 BC3577E019 for ; Wed, 20 Dec 2017 19:32:46 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd15.aul.t-online.de (fwd15.aul.t-online.de [172.20.27.63]) by mailout01.t-online.de (Postfix) with SMTP id 7510042C1F30; Wed, 20 Dec 2017 20:32:43 +0100 (CET) Received: from Stefans-MBP-2.fritz.box (ZYIIMiZJQhNRYaOS7ELaGsymTg2q33ll+gzb8wKWFCBNOY7kWdX86JqZJIiVF9uZHq@[84.154.114.37]) by fwd15.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1eRk6Y-3FSFTE0; Wed, 20 Dec 2017 20:32:38 +0100 Subject: Re: Setting system user home directory To: Adam Vande More , Dmytro Bilokha Cc: Kevin Oberman , Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD Ports ML References: <20171216094058.GA37778@wstan> <5A351515.1080805@quip.cz> <20171216135919.GA17551@wstan> <5A352BA5.9070403@quip.cz> <20171216170411.GA85559@wstan> <20171216185317.GA87289@wstan> <20171216200959.GA97697@wstan> From: Stefan Esser Message-ID: <699d4702-2610-2d3c-fe32-0977a4f05bc2@freebsd.org> Date: Wed, 20 Dec 2017 20:32:37 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-ID: ZYIIMiZJQhNRYaOS7ELaGsymTg2q33ll+gzb8wKWFCBNOY7kWdX86JqZJIiVF9uZHq X-TOI-MSGID: c932f382-683b-4b11-b738-86380d47fe67 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: Wed, 20 Dec 2017 19:32:47 -0000 Am 20.12.17 um 15:12 schrieb Adam Vande More: > On Sat, Dec 16, 2017 at 2:10 PM, Dmytro Bilokha wrote: > >> Guys, thanks for your help. I've managed to adjust user's homedir >> using pkg-install script. Now I'll try to move everything writable >> from /usr/local to /var (as Miroslav suggested), test and submit the new >> port version. > > I think you should do what makes sense for your application. The /var/db > stuff is not a hard fast rule and it doesn't work well for many > situations. Also it's mostly system related DB's that live there. It's > not only some java related ports that live mostly under /usr but also > things like postgres(at least used to). > > IMO, as long as you're not flagrantly violating hier(7), do what is best > for your port. For a port that needs quite a large database (password hashes from accounts that have been leaked), I implemented an option to initialize the application by downloading the data files after the user had a chance to select a place for the data (by editing the config file). The default is in /var/db, but the user may prefer a home directory or some sub-directory of /usr/local/ ... Regards, STefan From owner-freebsd-ports@freebsd.org Wed Dec 20 19:40:11 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C20F0E9F9EA for ; Wed, 20 Dec 2017 19:40:11 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F74E7E5EB for ; Wed, 20 Dec 2017 19:40:11 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yw0-x229.google.com with SMTP id m129so2130102ywb.11 for ; Wed, 20 Dec 2017 11:40:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Ke9yEjJORGVWlZ94XmKRiVZc6PpoEIQccaL9daJLdhg=; b=GE6eAwLx2n2qp/GKrGgkTM8ZnxULMEIe4LXGKdtkPv3CsN4Q+3JxpGVr0Bja34+10J edsDfes2TTUL0bi4U93tCkgyX+ENwuI6qQ/8NE/ZfUX5X4kaTNku1qw6XTwbhSgNR01Z BI/sjxjqb+Zusc3T1Hrm7E0mflMzSs54LbcFjFEOX8F1fLl8qEbAvz4xri/iR4WTpk0N hpAjbaZYAEufWd99t/z98vcgU5eW49MYgLEwswB4db/JYD9PSOFToq2p+KWotN4+jnAH GangmKlAFTUqv231dgYDOs8n4vgKJ0UA3YjGCKw4V1BTIau05Bf1G2pbw2lbXqEpmNjy 7upA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Ke9yEjJORGVWlZ94XmKRiVZc6PpoEIQccaL9daJLdhg=; b=VPAhUGnbwL20i8qVYe2sbOAJSa6BKJxYkto6odzUd1kDj95Tx7w3WiFkq8yFubJMiq 11goiLxZX+gQYlHePHu5XzEIicS35roMmh0PzinutvjnmT2TYMtyY8FoHT33Pmda2wrn 2hz1NeLLmZFahF0s7Viq7xVsgXpWGE77G4keo7RFBt3mP6HMtgdJcDRqST2kWCUO+tE7 dKdSA3g8naoS/Rsj5qmew/1bEoiyCi5fOSZvfwjI938KoAFlOjzKOpinYapL7nI3MXTL OTif/3rXIWahowM1g6pt3Uw2sId9ec1Fr7LGha5B9jFLnca1gGcvYPmFSPpUQa8cCd1o 7MBg== X-Gm-Message-State: AKGB3mJO/hKC2X/xjb8kjGpnrmC5wVfFQ6HlTN6hGoeZlpTjbLNQlybH Up4bCCkbwrUTEwE2NbKROnrwq2fMWu2CG0BjA45Bwg== X-Google-Smtp-Source: ACJfBosIgQnAf6TMF0oNQ3GBjA4ZLP4VPzCu7xw4ublI6ck0XVpUo7aZld29fwcR6PQewJ6KrSB3wJBjBg3/MI9K7ik= X-Received: by 10.129.131.203 with SMTP id t194mr5997496ywf.115.1513798810371; Wed, 20 Dec 2017 11:40:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.174.3 with HTTP; Wed, 20 Dec 2017 11:40:09 -0800 (PST) In-Reply-To: References: <3267de19-6e00-a72a-e2a7-abb322ccf7ac@rawbw.com> From: Ultima Date: Wed, 20 Dec 2017 11:40:09 -0800 Message-ID: Subject: Re: Vote: making wayland=on default To: FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 20 Dec 2017 19:40:11 -0000 I support adding wayland support on by default as well. It still is WIP in several areas one I have not seen mentioned yet includes nvidia graphics cards. Needing to rebuild several ports just to test does seem a bit too much though. Best regards, Richard Gallamore On Wed, Dec 20, 2017 at 11:14 AM, Johannes Lundberg wrote: > Hi Yuri > > To be clear, we're not transitioning to anything, we're simply adding > more options. Compare it to adding a new window manager for X, it > doesn't mean you have to stop using the existing ones... > > > On Wed, Dec 20, 2017 at 5:39 PM, Yuri wrote: > > On 12/20/17 01:20, Johannes Lundberg wrote: > >> > >> For any Desktop user (as well as embedded devices > >> like IVI-systems and whatnot), Wayland is the future. There's no > >> escaping that. > > > > > > Over the history of its development, Wayland could never clearly answer > the > > question "What are the benefits of Wayland for the end user?". > > Additionally, they always advocated the removal of features like > networked > > connections, window manager features. > > > > It appears that this is the case of fixing of something (xorg) that > > wasn't/isn't broken in the first place. And if it is considered broken, > then > > how, in which way? > > > > But you are right, it is a reality that Wayand devs had enough > horsepower to > > eventually, after many years, make it and now impose it on everybody, and > > force it to be a future reality. > > > > There are a lot of things that need to be verified that they work: > x11vnc, > > the ability to connect to a display remotely, every window manager should > > work with it, ex. xfce4, dwm. > > > > People should be asking the question "What's the benefit of the > transition > > to X?". The answer should include the functional benefits to users, not > just > > "We need to switch to something called X." What new features or > improvements > > will users actually see? > > > > > > Just my 2c. > > Yuri > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Wed Dec 20 19:56:13 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83801EA08DC for ; Wed, 20 Dec 2017 19:56:13 +0000 (UTC) (envelope-from net@arrishq.net) Received: from mail1.arrishq.net (eatmyshorts.phobos.ws [178.63.103.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 495B97F13A for ; Wed, 20 Dec 2017 19:56:12 +0000 (UTC) (envelope-from net@arrishq.net) Received: from mail.arrishq.net (mail.arrishq.net [127.0.0.1]) (Authenticated sender: local) by mail1.arrishq.net (qmail) with ESMTPSA id 62AF430C ; Wed, 20 Dec 2017 20:50:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arrishq.net; s=default; t=1513799406; bh=mYE1tjbLY2AyR+MPuqxWsyGC3t+hyTcUA2gLs+pjirQ=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Q4fm9qhQN/5M3XJkqOc3QvBsXigmv2sHoFIWCGg1AsMr3qWC0Trmls9Fao/mkwaZc GZOeeyX1AguBka82vG5MA7Xem389Uur/twWWGwmGIJWiR2+Sk89tnqx8zGZMQETDgh ULeCRdAfUQj6Voyc2liSEP7FumML324tS+mzGrw0kk3jixu+voJSG06DbsOMlJ75W7 QppGSYxz7QUHR2PIkJk3KQQOBDyQfe2RomUnmMwyduHx5J2kdCqLgK97nbsUzqAVHA JoRadJnSEKnCufSIT1FYlMtf5VZmUuOigZzk9xjoXmegoabcA1Ik+OgBkX5odrfcqw U1lhzQsVHMA8g== Date: Wed, 20 Dec 2017 20:49:24 +0100 (CET) From: net@arrishq.net To: Johannes Lundberg cc: freebsd-ports@freebsd.org Subject: Re: Vote: making wayland=on default In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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: Wed, 20 Dec 2017 19:56:13 -0000 Hi, On Wed, 20 Dec 2017, Johannes Lundberg wrote: > Hi > > Personally I see no reason not to make it default on, even with > flavors coming up. For any Desktop user (as well as embedded devices > like IVI-systems and whatnot), Wayland is the future. There's no > escaping that. and why does everyone think a Unix should be run on a desktop only ? And the "future", well, lot of companies are going to say "Cloud first" ;) is the future so the next thing-of-the-day will replace the today-thing-of-the-day to add what's required then and we're busy replacing things with the newest shiny technology because someone has to re-invent the wheel another time. Personally I don't see much problems rebuilding some ports if I really want Wayland, but as long as some apps run on some RasPi's and embedded devices without a display using plain X11 is the way and Wayland adds just overhead. Sure, that's my usage way and maybe 99% of all others have different opions. --- Sent from my iP..., nah, sent from my coffee machine From owner-freebsd-ports@freebsd.org Wed Dec 20 20:06:31 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B9DDEA13CC for ; Wed, 20 Dec 2017 20:06:31 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout04.t-online.de (mailout04.t-online.de [194.25.134.18]) (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 11A737FAEB for ; Wed, 20 Dec 2017 20:06:30 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd15.aul.t-online.de (fwd15.aul.t-online.de [172.20.27.63]) by mailout04.t-online.de (Postfix) with SMTP id CCD4041BB295; Wed, 20 Dec 2017 21:06:28 +0100 (CET) Received: from Stefans-MBP-2.fritz.box (E4KsWZZV8hdnW3GO+eww7gVuXoagZzcGQig-rrbprmny-Gashb-LO5RB2rZejRwgqu@[84.154.114.37]) by fwd15.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1eRkdH-0VLIcy0; Wed, 20 Dec 2017 21:06:27 +0100 Subject: Re: some fix needed still To: Sergio de Almeida Lenzi , Ports FreeBSD References: <36151973-c15f-c331-e9bd-5f574c0da6a7@freebsd.org> <1513771702.23135.0.camel@gmail.com> From: Stefan Esser Message-ID: Date: Wed, 20 Dec 2017 21:06:26 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <1513771702.23135.0.camel@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-ID: E4KsWZZV8hdnW3GO+eww7gVuXoagZzcGQig-rrbprmny-Gashb-LO5RB2rZejRwgqu X-TOI-MSGID: 603a9d78-18e8-4db7-a7af-b717e12ed818 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: Wed, 20 Dec 2017 20:06:31 -0000 Am 20.12.17 um 13:08 schrieb Sergio de Almeida Lenzi: > Version portmaster-3.17.11_9 > when you are in the port directory, the portmaster build wrong path > /usr/ports/ports instead of /usr/ports > ========================================================= > > > > [root@VMS /usr/ports/x11-themes/kf5-oxygen-icons5]# portmaster > > ===>>> No /usr/ports/ports/Mk exists, and no information > ===>>> about ports/Mk can be found in /usr/ports/MOVED > > ===>>> No valid installed port, or port directory given > ===>>> Try portmaster --help Thank you for the report. Fixed in portmaster-3.17.11_11. Regards, STefan From owner-freebsd-ports@freebsd.org Wed Dec 20 20:47:11 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3FFBEA3FB7 for ; Wed, 20 Dec 2017 20:47:11 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 688CF27FE for ; Wed, 20 Dec 2017 20:47:11 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 3z26Js3JRqzDh4j for ; Wed, 20 Dec 2017 20:47:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1513802829; bh=tC/rn6NhMjFKSQeZw9v0jQAU GAnDpxm8ukbXm4tdMcQ=; b=oh0WcU6qUXuufEr3X+gOXUIJkHckIRWMCUVDGk16 qyHWRjEaDgW+rDU3lPxN6NPa3zjk/wsUIwP6ETj7w37RLfkgTihS80mUNU14gkQ8 DYkx5S/qUIbaxlYtLga2cLLY+YRBuhJm7Cxd2Zy96p7IUSvA4bIvYNGg0vMz/07Q EO4= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id GpCTKvIoU0ue for ; Wed, 20 Dec 2017 20:47:09 +0000 (UTC) Received: from garnet.daemonic.se (unknown [IPv6:2001:470:dca9:201:9eda:3eff:fe70:24c0]) by mail.daemonic.se (Postfix) with ESMTPSA id 3z26Jr6j2gzDh4h for ; Wed, 20 Dec 2017 20:47:08 +0000 (UTC) Subject: Re: Vote: making wayland=on default To: freebsd-ports@freebsd.org References: From: Niclas Zeising Message-ID: Date: Wed, 20 Dec 2017 21:47:08 +0100 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Wed, 20 Dec 2017 20:47:11 -0000 On 12/20/17 10:20, Johannes Lundberg wrote: > Hi > > I want to suggest that we enable wayland by default. In current state > having some parts of wayland in ports is basically useless the > end-users themselves re-build gtk30 and mesa-libs with wayland > enabled. > > libwayland-egl.so from mesa-libs and the extra libraries and headers > from gtk30 adds like a few KB, a drop in the ocean compared to xorg > packages. (might be something more that I missed) > > Personally I see no reason not to make it default on, even with > flavors coming up. For any Desktop user (as well as embedded devices > like IVI-systems and whatnot), Wayland is the future. There's no > escaping that. > > Wayland has been quite usable on FreeBSD for over a year now but > access to it is limited due to the extra efforts required to use it. > > If we are to compare with the other guys, several Linux distros are > already switching to wayland-based compositors as default window > server. > > What do you think? > With my x11@ hat on. I have no problem with this, as long as the old xorg stuff keeps on working, as you've stated they will do. I do not have time to fix this this week, but if you can help me prepare a patch we can perhaps get it in after that (beginning of next week, in the days between Christmas and new years). Do you know which ports are affected by this, and have a WAYLAND option? We should also check, probably just in case, if portmgr thinks an exp run is needed (I don't think so). Regards! -- Niclas From owner-freebsd-ports@freebsd.org Wed Dec 20 20:57:57 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9004EA49FD for ; Wed, 20 Dec 2017 20:57:57 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A10023028 for ; Wed, 20 Dec 2017 20:57:57 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.187] (cpe-75-82-192-14.socal.res.rr.com [75.82.192.14]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 345db980 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 20 Dec 2017 12:57:39 -0800 (PST) Subject: Re: Vote: making wayland=on default To: net@arrishq.net, Johannes Lundberg Cc: freebsd-ports@freebsd.org References: From: Pete Wright Message-ID: Date: Wed, 20 Dec 2017 12:57:55 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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: Wed, 20 Dec 2017 20:57:57 -0000 On 12/20/2017 11:49, net@arrishq.net wrote: > Hi, > > On Wed, 20 Dec 2017, Johannes Lundberg wrote: > >> Hi >> >> Personally I see no reason not to make it default on, even with >> flavors coming up. For any Desktop user (as well as embedded devices >> like IVI-systems and whatnot), Wayland is the future. There's no >> escaping that. > > and why does everyone think a Unix should be run on a desktop only ? I suspect you might be a little confused - no one is saying that Unix is going to be "desktop only" - this is in regards to where graphical interfaces is moving for Unix like operating systems in general. > And the "future", well, lot of companies are going to say "Cloud > first" ;) is the future so the next thing-of-the-day will replace the > today-thing-of-the-day to add what's required then and we're busy > replacing things with the newest shiny technology because someone has > to re-invent the wheel another time. > > Personally I don't see much problems rebuilding some ports if I really > want Wayland, but as long as some apps run on some RasPi's and > embedded devices without a display using plain X11 is the way and > Wayland adds just overhead. > how does adding support, by default, for Wayland in some graphical binaries add overhead to your system at run time? no one is saying that this will supplant Xorg, but rather this will make it easier for more people in the FreeBSD community to actively test and dogfood Wayland.  the alternative is for FreeBSD to continue to be an afterthought by freedesktop and Wayland community which doesn't seem like a good long-term strategy IMHO. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-ports@freebsd.org Wed Dec 20 22:21:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0578FE82EE7 for ; Wed, 20 Dec 2017 22:21:54 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp.rcn.com (smtp.rcn.com [69.168.97.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3CB565586 for ; Wed, 20 Dec 2017 22:21:53 +0000 (UTC) (envelope-from roberthuff@rcn.com) X_CMAE_Category: , , X-CNFS-Analysis: v=2.2 cv=ccOQlTLM c=1 sm=1 tr=0 a=9TgA2UwI6Wy+6BV4wQM/cQ==:117 a=9TgA2UwI6Wy+6BV4wQM/cQ==:17 a=KGjhK52YXX0A:10 a=kj9zAlcOel0A:10 a=XRQyMpdBKAEA:10 a=ocR9PWop10UA:10 a=48faUk6PgeAA:10 a=kcD68_fZcCixSmEIcWwA:9 a=CjuIK1q_8ugA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine X-Authed-Username: cm9iZXJ0aHVmZkByY24uY29t Authentication-Results: smtp02.rcn.cmh.synacor.com smtp.mail=roberthuff@rcn.com; spf=softfail; sender-id=softfail Authentication-Results: smtp02.rcn.cmh.synacor.com header.from=roberthuff@rcn.com; sender-id=softfail Authentication-Results: smtp02.rcn.cmh.synacor.com smtp.user=roberthuff; auth=pass (PLAIN) Received-SPF: softfail (smtp02.rcn.cmh.synacor.com: transitional domain rcn.com does not designate 209.6.230.48 as permitted sender) Received: from [209.6.230.48] ([209.6.230.48:37466] helo=jerusalem.litteratus.org.litteratus.org) by smtp.rcn.com (envelope-from ) (ecelerity 3.6.25.56547 r(Core:3.6.25.0)) with ESMTPSA (cipher=AES256-GCM-SHA384) id 15/F1-43295-F72EA3A5; Wed, 20 Dec 2017 17:21:52 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <23098.57983.262947.67141@jerusalem.litteratus.org> Date: Wed, 20 Dec 2017 17:21:51 -0500 To: Yuri Cc: Johannes Lundberg , freebsd-ports@freebsd.org From: roberthuff@rcn.com Subject: Re: Vote: making wayland=on default In-Reply-To: <3267de19-6e00-a72a-e2a7-abb322ccf7ac@rawbw.com> References: <3267de19-6e00-a72a-e2a7-abb322ccf7ac@rawbw.com> X-Mailer: VM 8.2.0b under 25.3.1 (amd64-portbld-freebsd12.0) 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: Wed, 20 Dec 2017 22:21:54 -0000 Yuri writes: > It appears that this is the case of fixing of something (xorg) > that wasn't/isn't broken in the first place. And if it is > considered broken, then how, in which way? You ask "Is it broken?". I ask "Is there a better way?" Think about gcc: it was developed in the mid '80s, and at the time was pretty dang impressive. But over time ... "provisional" hacks to handle less-common hardware or specific software anomalies became permanently entrenched (or so I am told) even as hardware changed, and both compiler technology and coding practices improved. I think of X the same way. To the list: I salute X for doing its job, but I have no brand loyalty. If something comes along that is some combination of a) more robust, b) faster, and c) as easy to install/manage I'll switch in a heartbeat. (Smaller footprint would be nice too.) Is that Wayland? Fact not (yet) in evidence. Is Wayland-on-FreeBSD in active development? If so: where - other than ports@ - do I go to check the /status quo/? Respectfully, Robert Huff From owner-freebsd-ports@freebsd.org Wed Dec 20 22:40:26 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82811E83BDD for ; Wed, 20 Dec 2017 22:40:26 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 435C765DFF for ; Wed, 20 Dec 2017 22:40:26 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=m/4OUnOKWRPNsKCrI/TXG4fT52EVa/gI8+j5Riur9zE=; b=Hwl7GAX2mCG13+m2oaB3Bb6vjb10GtTl54wIHxahzF8cOx8oeG5ttNd+Aes/AoqQ0+TVB0k9VWUL0uw76lN88sIc7m0qHoqnTOhZiMJVOGeHoHsQfP6Dq7gWb3Jez77Ci7qu9lZ4ZfIoE6eXIoiwuaCqyRrr2+9FW3+pt+p/hVk=; Received: from pam.xoc.tele2net.at ([213.90.36.6]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1eRn2E-000218-5o for freebsd-ports@freebsd.org; Wed, 20 Dec 2017 23:40:22 +0100 Received: from 188-23-12-173.adsl.highway.telekom.at ([188.23.12.173] helo=[10.0.0.93]) by pam.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1eRn2E-0002dF-3U for freebsd-ports@freebsd.org; Wed, 20 Dec 2017 23:40:22 +0100 To: freebsd-ports@freebsd.org References: Subject: Re: some fix needed still From: Walter Schwarzenfeld Message-ID: <7bac7614-1a51-8850-9f32-95ce562f4256@utanet.at> Date: Wed, 20 Dec 2017 23:40:16 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 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: Wed, 20 Dec 2017 22:40:26 -0000 a "little thing" pkg info portmaster portmaster-3.17.11_11 Name           : portmaster Version        : 3.17.11_11 -- portmaster --version ===>>> Version 3.17.10 From owner-freebsd-ports@freebsd.org Wed Dec 20 23:29:44 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74DBAE868FC for ; Wed, 20 Dec 2017 23:29:44 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id ADCB667E58 for ; Wed, 20 Dec 2017 23:29:43 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 2621 invoked by uid 89); 20 Dec 2017 23:29:40 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@46.244.226.155) by mail.grem.de with ESMTPA; 20 Dec 2017 23:29:40 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Vote: making wayland=on default From: Michael Gmelin X-Mailer: iPhone Mail (14G60) In-Reply-To: <9142f3e2938c84bd838b3764197226be@udns.ultimatedns.net> Date: Thu, 21 Dec 2017 00:29:40 +0100 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8EDCE5A5-391E-4529-9713-79901739CC6F@grem.de> References: <9142f3e2938c84bd838b3764197226be@udns.ultimatedns.net> To: portmaster@BSDforge.com 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: Wed, 20 Dec 2017 23:29:44 -0000 > On 20. Dec 2017, at 18:50, Chris H wrote: >=20 > On Wed, 20 Dec 2017 17:13:43 +0000 said >=20 > On Wed, 20 Dec 2017 16:23:59 +0000 "Johannes Lundberg" > said >=20 >> On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote:= >> > On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" >> >> > said >> > >> >> Hi >> >> >> >> I want to suggest that we enable wayland by default. In current state >> >> having some parts of wayland in ports is basically useless the >> >> end-users themselves re-build gtk30 and mesa-libs with wayland >> >> enabled. >> >> >> >> libwayland-egl.so from mesa-libs and the extra libraries and headers >> >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >> >> packages. (might be something more that I missed) >> >> >> >> Personally I see no reason not to make it default on, even with >> >> flavors coming up. For any Desktop user (as well as embedded devices >> >> like IVI-systems and whatnot), Wayland is the future. There's no >> >> escaping that. >> >> >> >> Wayland has been quite usable on FreeBSD for over a year now but >> >> access to it is limited due to the extra efforts required to use it. >> >> >> >> If we are to compare with the other guys, several Linux distros are >> >> already switching to wayland-based compositors as default window >> >> server. >> >> >> >> What do you think? >> > >> > IMHO it's (still) too early. Too much other X(org) related work >> > still being completed. In fact, I just built a new dev box to >> > track 12 (CURRENT), and this was the first time I was not required >> > to pre generate a config file for Xorg. I was only required to >> > inform /usr/local/etc/X11/xorg.conf.d/nvidia-driver.conf that >> > the driver was "nvidia", not "nv". Everything work(s|ed) famously. >> > A real treat. I'm also a bit concerned about the progress (or lack >> > there of) on network transparency. >> > I (personally) could conceive it as a KERNEL OPTION, but would not >> > want to see it in the Default kernel. >> > >> > Well, those are *my* thoughts. Because you asked. :-) >> > >> > --Chris >> > >> Thanks for your feedback! >> Just to clarify, we're not talking about changing any defaults that >> would impact or change users' choice of desktop. We only want to >> enable Wayland compositors as an alternative to X (leaving X as is). >> This does not break or modify anything existing. It does not force you >> to do anything differently. It simply adds a couple of libraries that >> you won't use unless you run Wayland stuff (if you install qt5/gtk30 >> and mesa-libs). >> The reference to Linux making it default might have been unclear. >> Since FreeBSD doesn't have a default desktop, it's hard to change. It >> is and will continue to be up to the end user what they choose to use, >> we only add more options :) > Thanks for the informative reply, Johannes. > So no kernel (libs/extensions)? > Hmm, gtk3. Why is it not possible to make the Wayland stuff a sub > package/option? I think this is the preferred track/policy anyway. > I do this for all the ports I currently maintain. IOW any DE related > stuff I install, that uses GNOME related material, will pull in gtk3, > which, as I understand you say, will ultimately pull in Weston,mesa,... > is that correct? While I understand, you indicate it's only a few Kb. > I think it's cruft/(unnecessary)overhead. Which, in and of itself > seems insignificant. But in the "big picture", and over many (100's) > of builds/installations, is *not* insignificant. This also dismisses > the security related work, maintaining extra un(used|needed) material. > I suppose some will think that I'm just being nit-picky. But IMHO > I'm not. This sort of thing, if overlooked, *does* affect the bottom > line. >=20 > Thanks again, Johannes! >=20 > P.S. I have nothing against Wayland. I'm just not ready to run it > on anything "production" related, just yet. :-) >=20 > --Chris >=20 The key is to have it in a state that easy to maintain and allows people to i= nstall it using pkg install without conflicting with X, so you can switch ba= ck and forth easily. I'm also not ready to switch to wayland yet (favorite w= indow manager not available, so many custom configurations I came up with ov= er the years etc.), but giving users an easy way to test it (or use it, as i= t's becoming more and more mainstream now) is a good thing.=20 Having a modern, working, out of the box desktop (read: no custom kernel bui= lds, no need to use ports, a laptop is the point of first contact for many p= otential users) is incredibly important for proliferation and compared to th= e total size of binaries required to run X, I think the usefulness of provid= ing wayland easily outweighs the extra overhead. Yours, Michael >> >> >> >> >> >> /Johannes >> > >> > >>>=20 >=20 >=20 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Dec 21 00:20:19 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D29B6E897C5 for ; Thu, 21 Dec 2017 00:20:19 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3327C698B3; Thu, 21 Dec 2017 00:20:18 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.182.48.68]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M9K5G-1eHJfG25Xi-00Ch5v; Thu, 21 Dec 2017 01:19:24 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id DDFA323D1D7; Thu, 21 Dec 2017 01:19:20 +0100 (CET) Subject: Re: Procmail got updated! To: Eugene Grosbein , Ted Hatfield , freebsd-ports@freebsd.org Cc: Sunpoet Po-Chuan Hsieh References: <5A39F7C9.1030800@grosbein.net> From: Matthias Andree Message-ID: <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> Date: Thu, 21 Dec 2017 01:19:20 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <5A39F7C9.1030800@grosbein.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE X-Provags-ID: V03:K0:1o+58Ymjk69MjxGGECU+75hhz70p939+NWQFRuSC5PMsRkev9R1 Z38nkzyJ1s3+pVsj5pmTq2odHwmxCkfjhKIe3ira9DsQ0i3qf5qx2cbokIdElgJAnsXO951 nJtMFQ0yu3rhhbBdmft0lLMf6mHsFcPnfm18hJiFGgIdQkJwp7nRiVXx8+j0BrxcyDrrLpX uU5HCpN11/BPFcvQ6/ckw== X-UI-Out-Filterresults: notjunk:1;V01:K0:tDexPcs5ui4=:2VsvkEI92Xi+KC/NiMYS7r 8TDirUCXnvKdfoJXpEi1hkL6izRptJmSQ80ooXsR7XKe4HvouZQv26IAHu/A83qgVWYcyH+cf TJnd10VNWDk43+e1ZTxlWvKkfJWtykdyl6PCw/XLwBho1FgI6Eyofo1T97jatokrjZ6m0cCmb Uw3cYQFeYymPwHzcWjFwP1jwJhZOo9H6RWb96jRrrbEGuypcIIqdtoCCoGyhaKNeYXpcPF+cl mwkq4mEwLf7QVnA2PO1Jv+HG62GyOqOqEvOtbqXqQ2hsJN0x6EM3oT1EnkQnKbOl5JvC0T+gg ILoB39H4BvvwFwWiVV6ArZBwlxVFxtTpNRvckvEqjazTCa6WnKOxlv+EIr5JR8GNUdbDxxnds pPZX/KmcptTLPYMtKW0AbpZTykbZB3NCu0fF9ZJTsCnmXs9MN532+YyAfT3DI9NczOZEViIhF Dffa0SLgcerT3pWnYJ0CWPDUj2wDavOuQLkgVwGMc6b9gs2dUAWJgAZexZ1jNeZ0YiI7PhbUL XgZFzZDmcs3QUW5f8DKGQEpQVvTqIAaJQO8gJJpKlaEJz6ahHOnDk4psIP3gZoyFpZxnZRPLa bouo+qiZGZ3yZHGnFr/lNVaEngZjU4bZ5JY3DUqBcZmpZwLaPYwgMz/A5/itclmUhVDx0n8pk TPWXtSj7puV95aYvw9PKTyUlxv8SWTqNSrd6mOGjLSU+Q50/GTXs4uWtgU736MVsQjI3OOMwK V1F597J0qjj5wCZ9dFp5PwWpm2smAAqjXAUvLq70UJfX/yL/wrfpaFVMeJ0N6lG4jzRy5AqLE H2Rf9R8jUk3Yu5r6y81pWetjcd9fgx74BDnWJ7PbhT1rEq8yMs= 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: Thu, 21 Dec 2017 00:20:19 -0000 Am 20.12.2017 um 06:40 schrieb Eugene Grosbein: > On 20.12.2017 01:03, Matthias Andree wrote: > >> Dear Ted, Eugene, > [skip] > > What happened with old good "Tools, not policy" thing? > > It's simpler than that, no policy involved. The tool had a hollow head, and broke after several years of banging it, and the former tool maker told the public it's out of warranty (never was in due to it being free) and not being fixed any more, and should be scrapped. From owner-freebsd-ports@freebsd.org Thu Dec 21 00:27:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16B1CE8A1B2 for ; Thu, 21 Dec 2017 00:27:46 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC8706A0D2 for ; Thu, 21 Dec 2017 00:27:45 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x22f.google.com with SMTP id g69so11290105vkg.0 for ; Wed, 20 Dec 2017 16:27:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ySpf4J5DTGbMF5blJ15Y59TEaBAMAwDPUBs1NICSGno=; b=oUR7eLXXHCkqa+Pjs5UfrMRiwieO3JXvL0HZqZUfruYWFpaNMWHCeo+3Uc006xItr3 EzclMrp/AAfOTleAvqKnObEKBe6zoyU7KjFtiFnuSm7sBTzhS00OtUuYugvwDGdnjl3u Kd13CFEsJrQeeHoVisnIzYWm7TFuh1u7vfShxXDpeyjROo7YcNWvKwx/7Gb3yGhxSaaJ GY0Z+rCkd36SXGMGQhhHhwzzXOzHHmdzYVYULbhuBt0qbal8SqsXxlanAroOfWII4vul 7n9J3RQ7oSHV1axLEMmm0ptzkjT8HEec0ndqyBVGMlH2FQeOR+mrWl0C4QihqK54N+mv IY5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ySpf4J5DTGbMF5blJ15Y59TEaBAMAwDPUBs1NICSGno=; b=mqHEiel3Ai2Nhs/VCC4SuzLUh2qfqeBoATgZhDyiUlISlfA6rmQNz7Md3JIFcahtXL jyMy5OB5dr+cdelBVfU3229+PKapGYhGTK4Ko5/uZjZqPzGE+csvcjfUO/RFP/JDdmfS 0DSCwU3irv3w4Psks+btkkSccfmB3DPSr6b11Lsodd4d5yoQxOVB31QIwP6nBAHXV4Gz nsKqDpm/AT14rn5NqrI9lP9y2SrEhrI5JgXmMYS9F65HSzKOFcnfFUNMGL3ZTH1amkZp AmsTuvaTYYqwRouh9hMItGo2ePZeyUZSnZ/r7T9sbpnN4o2s+bz2pTBhsgHsgVaLpV1n QMgw== X-Gm-Message-State: AKGB3mJNyf0dOdraYt7evokHDdfc81qvapdKaHX21/1Rzip/geLW0pvU /z7LmZh1PMbeUvvgkQzgFrEPsEKuAK7h7iBrN9/AMpjg X-Google-Smtp-Source: ACJfBoscHCYTMRTkYnaXfZuVJfmtvOAA1D4QQzahVa19wSmHsRKaZ6bPmbBDv09jzCd88GWM1x/i5bMN6wbKMxDRdfY= X-Received: by 10.31.34.84 with SMTP id i81mr8273899vki.181.1513816064558; Wed, 20 Dec 2017 16:27:44 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.147.156 with HTTP; Wed, 20 Dec 2017 16:27:43 -0800 (PST) In-Reply-To: <8EDCE5A5-391E-4529-9713-79901739CC6F@grem.de> References: <9142f3e2938c84bd838b3764197226be@udns.ultimatedns.net> <8EDCE5A5-391E-4529-9713-79901739CC6F@grem.de> From: Kevin Oberman Date: Wed, 20 Dec 2017 16:27:43 -0800 X-Google-Sender-Auth: htwwKna2t0Oez08boCOd4a49cKU Message-ID: Subject: Re: Vote: making wayland=on default To: Michael Gmelin Cc: portmaster@bsdforge.com, FreeBSD Ports ML Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Thu, 21 Dec 2017 00:27:46 -0000 On Wed, Dec 20, 2017 at 3:29 PM, Michael Gmelin wrote: > > > > On 20. Dec 2017, at 18:50, Chris H wrote: > > > > On Wed, 20 Dec 2017 17:13:43 +0000 > said > > > > On Wed, 20 Dec 2017 16:23:59 +0000 "Johannes Lundberg" < > johalun0@gmail.com> > > said > > > >> On Wed, Dec 20, 2017 at 4:08 PM, Chris H > wrote: > >> > On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" > >> > >> > said > >> > > >> >> Hi > >> >> > >> >> I want to suggest that we enable wayland by default. In current state > >> >> having some parts of wayland in ports is basically useless the > >> >> end-users themselves re-build gtk30 and mesa-libs with wayland > >> >> enabled. > >> >> > >> >> libwayland-egl.so from mesa-libs and the extra libraries and headers > >> >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg > >> >> packages. (might be something more that I missed) > >> >> > >> >> Personally I see no reason not to make it default on, even with > >> >> flavors coming up. For any Desktop user (as well as embedded devices > >> >> like IVI-systems and whatnot), Wayland is the future. There's no > >> >> escaping that. > >> >> > >> >> Wayland has been quite usable on FreeBSD for over a year now but > >> >> access to it is limited due to the extra efforts required to use it. > >> >> > >> >> If we are to compare with the other guys, several Linux distros are > >> >> already switching to wayland-based compositors as default window > >> >> server. > >> >> > >> >> What do you think? > >> > > >> > IMHO it's (still) too early. Too much other X(org) related work > >> > still being completed. In fact, I just built a new dev box to > >> > track 12 (CURRENT), and this was the first time I was not required > >> > to pre generate a config file for Xorg. I was only required to > >> > inform /usr/local/etc/X11/xorg.conf.d/nvidia-driver.conf that > >> > the driver was "nvidia", not "nv". Everything work(s|ed) famously. > >> > A real treat. I'm also a bit concerned about the progress (or lack > >> > there of) on network transparency. > >> > I (personally) could conceive it as a KERNEL OPTION, but would not > >> > want to see it in the Default kernel. > >> > > >> > Well, those are *my* thoughts. Because you asked. :-) > >> > > >> > --Chris > >> > > >> Thanks for your feedback! > >> Just to clarify, we're not talking about changing any defaults that > >> would impact or change users' choice of desktop. We only want to > >> enable Wayland compositors as an alternative to X (leaving X as is). > >> This does not break or modify anything existing. It does not force you > >> to do anything differently. It simply adds a couple of libraries that > >> you won't use unless you run Wayland stuff (if you install qt5/gtk30 > >> and mesa-libs). > >> The reference to Linux making it default might have been unclear. > >> Since FreeBSD doesn't have a default desktop, it's hard to change. It > >> is and will continue to be up to the end user what they choose to use, > >> we only add more options :) > > Thanks for the informative reply, Johannes. > > So no kernel (libs/extensions)? > > Hmm, gtk3. Why is it not possible to make the Wayland stuff a sub > > package/option? I think this is the preferred track/policy anyway. > > I do this for all the ports I currently maintain. IOW any DE related > > stuff I install, that uses GNOME related material, will pull in gtk3, > > which, as I understand you say, will ultimately pull in Weston,mesa,... > > is that correct? While I understand, you indicate it's only a few Kb. > > I think it's cruft/(unnecessary)overhead. Which, in and of itself > > seems insignificant. But in the "big picture", and over many (100's) > > of builds/installations, is *not* insignificant. This also dismisses > > the security related work, maintaining extra un(used|needed) material. > > I suppose some will think that I'm just being nit-picky. But IMHO > > I'm not. This sort of thing, if overlooked, *does* affect the bottom > > line. > > > > Thanks again, Johannes! > > > > P.S. I have nothing against Wayland. I'm just not ready to run it > > on anything "production" related, just yet. :-) > > > > --Chris > > > > The key is to have it in a state that easy to maintain and allows people > to install it using pkg install without conflicting with X, so you can > switch back and forth easily. I'm also not ready to switch to wayland yet > (favorite window manager not available, so many custom configurations I > came up with over the years etc.), but giving users an easy way to test it > (or use it, as it's becoming more and more mainstream now) is a good thing. > > Having a modern, working, out of the box desktop (read: no custom kernel > builds, no need to use ports, a laptop is the point of first contact for > many potential users) is incredibly important for proliferation and > compared to the total size of binaries required to run X, I think the > usefulness of providing wayland easily outweighs the extra overhead. > > Yours, > Michael There seems to be general confusion on what Wayland is and what it does. Anyone who worked with X11 back in the R4 and R5 days probably understands the issues with the client/server protocol. I remember all of the optimizations needed to get it to perform even passably on VMS, most of which went into R6. But the protocol is still painfully primitive and awkward in today's world. It really has no concept of compositors and that makes everything much more expensive on both the server and client sides. I really expected something like Wayland to show up 15 or 20 years ago. Putting Wayland into the system has a minimal cost in disk space. Unless you choose to use it, it has no impact on application performance or size. It mostly means that, if you want to use Wayland, you can o so without rebuilding lots of stuff from ports. The packages will have be built with ll of the required linkages. Does not matter what desktop you use, though many of them may not yet work well (or at all) with Wayland, many will and you wilol be able to try Wayland out easily. YES!!! Wayland support should be present when available. It's all upside. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-ports@freebsd.org Thu Dec 21 00:35:29 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77C52E8A896 for ; Thu, 21 Dec 2017 00:35:29 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0654B6A7A7; Thu, 21 Dec 2017 00:35:29 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x234.google.com with SMTP id j192so14587586vkc.1; Wed, 20 Dec 2017 16:35:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=/fOZCo1Fw1BqF1l+6umi2XadSHf+VM6vI7jVTPdlP24=; b=jF0kli/KxDp+KB/3ayAgHYGd0lAaOeJqyv9p4Yka+9GAe9Xxptm7gISVCtI0PCmRhu DWSuGs8VdzY+6Sp732GTv0aKUp4TumZHG4weXzLryu32/w8M0k4pibFHzAyFWzt39COY wGEmGehME/sYt+EGfT1j3aqfHZlVQ2BpI/fv99geqfQ8+rrgfB6cLdVr/VYFPYD2xqEU IqYcOUWg5+T4DB8qcdpES2hzLs08s83rt3brnHjIUXSbZKiNMhB7demah0WvMp5gzp7R EIQRKyj+txxCnwoEhJv5uxSQdvIniOhK41z4zomqPIbCMod11vDjl+Tir69dx2Q9fdt6 BKHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=/fOZCo1Fw1BqF1l+6umi2XadSHf+VM6vI7jVTPdlP24=; b=GowpcVgatPtj9yQzpQpuYAVg5gkuT3/dThnlshBZFOi1HrK1CNc1nUDf5ox3JThdBh f65d49q2JPUIfpjYhSSTwOqvit5wSh7ka8kah8nR+eV1C4scQCUwvng2A6WevqpHXebA 9foXuiiBfkl1jOSwvnAREJF0iKFyMCTCsKihDeQ5XX839kIJhTZnKSas/+pvVJJfWxkl +/sQ8cbIGX0iN1h3px/1SptuXPZNsORB2xvrZT0uNfTrJ82i4bal7k6kpndK5MB8CtB0 LtLXtZyL/8r3EiH+5be+izqNb7YuZ6MlLLcCmoDhiCwJ9YY4EaIM96KBVi9adLzKHaNA 0VoA== X-Gm-Message-State: AKGB3mL8UEcjmaswHC2KCCjBeA126J0yhaCPrrTHnGcP4r7kcjq9NVtr /0hr2KJkADLwqBCdsa3kzje3v/k8SMwn1KolSbs= X-Google-Smtp-Source: ACJfBotYQkCYpgZIa6xio9F4F6KpipFYEg3Z/bRn3iPlyBs8jLPY8+GYOiHysDmfKZ60/ETr7CT/n3SbwvEcMVSVyPI= X-Received: by 10.31.207.199 with SMTP id f190mr8935761vkg.166.1513816527775; Wed, 20 Dec 2017 16:35:27 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.147.156 with HTTP; Wed, 20 Dec 2017 16:35:27 -0800 (PST) In-Reply-To: <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> From: Kevin Oberman Date: Wed, 20 Dec 2017 16:35:27 -0800 X-Google-Sender-Auth: nMXwNM_DyGo0BS9e3paw2C7GuDU Message-ID: Subject: Re: Procmail got updated! To: Matthias Andree Cc: Eugene Grosbein , Ted Hatfield , FreeBSD Ports ML , Sunpoet Po-Chuan Hsieh Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Thu, 21 Dec 2017 00:35:29 -0000 On Wed, Dec 20, 2017 at 4:19 PM, Matthias Andree wrote: > Am 20.12.2017 um 06:40 schrieb Eugene Grosbein: > > On 20.12.2017 01:03, Matthias Andree wrote: > > > >> Dear Ted, Eugene, > > [skip] > > > > What happened with old good "Tools, not policy" thing? > > > > > > It's simpler than that, no policy involved. > > The tool had a hollow head, and broke after several years of banging it, > and the former tool maker told the public it's out of warranty (never > was in due to it being free) and not being fixed any more, and should be > scrapped. > It still works (painfully) and is used by many. They would be wise to stop, but it is not the job of the project to force them to do so, I do think that a pkg-message with "Here there be dragons! Proceed at your own risk. dropmail is a MUCH safer (and easier) path." would be appropriate. I don't think it is the job of the project to force people to replace it if they think they know what they are doing. Of course, bitrot or similar may take it before long. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-ports@freebsd.org Thu Dec 21 00:37:21 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8068E8AB15 for ; Thu, 21 Dec 2017 00:37:21 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 702056AA07 for ; Thu, 21 Dec 2017 00:37:21 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa12.server.lan (via HTTP); Thu, 21 Dec 2017 01:37:18 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: "blubee blubeeme" Cc: "FreeBSD Ports" Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Thu, 21 Dec 2017 01:37:18 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:s2qfAUHEd75qmG8JeQTbNS175g0hC68yE/PjtfX5ecg aJhHzcNo1SpZ1Lh8Xj5emCNKyxr+l07Lnh3iKJADq2/4vgPZ6S DH1Vr9FwGBWG5879MGbgRnRWvtRIckhlN9CjfSiB9axnWxuL9j t2Wgg8Q15ga+9efF9COJLAqvQm5NmmOlPkuGJ9T6Z3VQ1JEv2T W6SM4zDV82AUUPtIAnh2gmr0O8nMs0brFVjtlDw0Rv225L7LPE I99QytsgtUA47MOxr2DeimlhEdx7NMyTZRvQWqbu1RVNXQFigM XSaiP8= X-UI-Out-Filterresults: notjunk:1;V01:K0:1gqf03HQWmU=:70HXWhbdi1WhKNQQvtYbsy 9s+Yv2R0mEBm2z43rI/48YWkgQyNW3/d6pA8ULd2vyZZXOS7MWcbMzGz4rDBJzYis4OsbByLy Eze7afIeRMictTdp1SJKNgPX+AtCUsgEi4QQtMoVdAL+qSo0i7bSWRGCeDUama8t57FvMyZ89 1NqdKv/3g8AXh3V4ndEcjGm2MQ0+tHaO38Gvf5gaeYa5KuRkg+cRXj0UYfrKcA4GRcbiWk1/M iDuDpv5DPtTpd1VIOWReULrIno72ECSdUjrgZ8VC2+uY7SSf9LSBHqyYTifRZpct24nT681GC xOIkaGQKymMjqbMPiCEmE62QstggJ3Or0/tpMfML/Qn0JhCpsT2ALuLHulnfa5nCjVkp4tBlu v2DtLFoMuvlMFhMRXSpX1Yxm+IECJUZB7nyra0o4QLl/uKhWxhV95KiJmiMdbkXNZwtS/pOTq eyavWXt1JqIRCQ2CIOZKO7DMGDi4RFBD74KBnyrFHfOmaYp0Ln1k8zN22b6YtQ1aswOYwkIem o3oWKudIgY+cfhSqtUI3w6TAU7Hclw1uM0qlPf7XqBD 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: Thu, 21 Dec 2017 00:37:21 -0000 > Blubee blubeeme > I'll work on it but let me get the port in the tree first, then I can refine it. > Just as i've done with my previous ports. > Sid > a simple program that plays simple sounds like "Ding!" > The problem with libcanberra is around pulseaudio and gstreamer. It is also with how gtk, a Visual Graphical toolkit, is mixed in with an Audio application. I was inspecting libcanberra and libcanberra-gtk3. audio/libcanberra-gtk3 takes care of canberra plugins for pulseaudio and gstreamer. It also takes care of two gtk3 library files, one of which is a module. Ports that really need gtk3 are tangled mostly upstream, and require --enable-gtk3. Others ports require libcanberra-gtk3 for either gtk3, pulseaudio or gstreamer. Some ports have audio/libcanberra-gtk3 as a dependency, but don't need it. audio/libcanberra itself is not so bad. audio/libcanberra also works without gtk20 in the test Makefile, which shouldn't be needed at all. So, plain libcanberra without libcanberra-gtk3 is not complicated, because it doesn't involve gtk3, pulseaudio, and gstreamer; it has gtk2 as a dependency, which it doesn't need. Sooner or later, a drop in replacement for libcanberra needs to be made for all BSD's. It should use ogg files from audio/freedesktop-sound-theme. Perhaps it can include simple pipe to play ogg and other audio files as well. After investigating, libcanberra is suitable for the short term, and anything that fails without libcanberra-gtk3 is an issue with the upstream ports themselves. From owner-freebsd-ports@freebsd.org Thu Dec 21 01:12:23 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D04EE8CD59 for ; Thu, 21 Dec 2017 01:12:23 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3E00E6BBB0 for ; Thu, 21 Dec 2017 01:12:22 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vBL1EJCs074600 for ; Wed, 20 Dec 2017 17:14:25 -0800 (PST) (envelope-from portmaster@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 In-Reply-To: <8EDCE5A5-391E-4529-9713-79901739CC6F@grem.de> From: "Chris H" Reply-To: portmaster@BSDforge.com To: Subject: Re: Vote: making wayland=on default Date: Wed, 20 Dec 2017 17:14:25 -0800 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable 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: Thu, 21 Dec 2017 01:12:23 -0000 On Thu, 21 Dec 2017 00:29:40 +0100 "Michael Gmelin" said > > On 20=2E Dec 2017, at 18:50, Chris H wrote: > >=20 > > On Wed, 20 Dec 2017 17:13:43 +0000 sa= id > >=20 > > On Wed, 20 Dec 2017 16:23:59 +0000 "Johannes Lundberg" > > said > >=20 > >> On Wed, Dec 20, 2017 at 4:08 PM, Chris H wro= te: > >> > On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" > >> > >> > said > >> > > >> >> Hi > >> >> > >> >> I want to suggest that we enable wayland by default=2E In current sta= te > >> >> having some parts of wayland in ports is basically useless the > >> >> end-users themselves re-build gtk30 and mesa-libs with wayland > >> >> enabled=2E > >> >> > >> >> libwayland-egl=2Eso from mesa-libs and the extra libraries and header= s > >> >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg > >> >> packages=2E (might be something more that I missed) > >> >> > >> >> Personally I see no reason not to make it default on, even with > >> >> flavors coming up=2E For any Desktop user (as well as embedded device= s > >> >> like IVI-systems and whatnot), Wayland is the future=2E There's no > >> >> escaping that=2E > >> >> > >> >> Wayland has been quite usable on FreeBSD for over a year now but > >> >> access to it is limited due to the extra efforts required to use it= =2E > >> >> > >> >> If we are to compare with the other guys, several Linux distros are > >> >> already switching to wayland-based compositors as default window > >> >> server=2E > >> >> > >> >> What do you think? > >> > > >> > IMHO it's (still) too early=2E Too much other X(org) related work > >> > still being completed=2E In fact, I just built a new dev box to > >> > track 12 (CURRENT), and this was the first time I was not required > >> > to pre generate a config file for Xorg=2E I was only required to > >> > inform /usr/local/etc/X11/xorg=2Econf=2Ed/nvidia-driver=2Econf that > >> > the driver was "nvidia", not "nv"=2E Everything work(s|ed) famously=2E > >> > A real treat=2E I'm also a bit concerned about the progress (or lack > >> > there of) on network transparency=2E > >> > I (personally) could conceive it as a KERNEL OPTION, but would not > >> > want to see it in the Default kernel=2E > >> > > >> > Well, those are *my* thoughts=2E Because you asked=2E :-) > >> > > >> > --Chris > >> > > >> Thanks for your feedback! > >> Just to clarify, we're not talking about changing any defaults that > >> would impact or change users' choice of desktop=2E We only want to > >> enable Wayland compositors as an alternative to X (leaving X as is)=2E > >> This does not break or modify anything existing=2E It does not force you > >> to do anything differently=2E It simply adds a couple of libraries that > >> you won't use unless you run Wayland stuff (if you install qt5/gtk30 > >> and mesa-libs)=2E > >> The reference to Linux making it default might have been unclear=2E > >> Since FreeBSD doesn't have a default desktop, it's hard to change=2E It > >> is and will continue to be up to the end user what they choose to use, > >> we only add more options :) > > Thanks for the informative reply, Johannes=2E > > So no kernel (libs/extensions)? > > Hmm, gtk3=2E Why is it not possible to make the Wayland stuff a sub > > package/option? I think this is the preferred track/policy anyway=2E > > I do this for all the ports I currently maintain=2E IOW any DE related > > stuff I install, that uses GNOME related material, will pull in gtk3, > > which, as I understand you say, will ultimately pull in Weston,mesa,=2E=2E=2E > > is that correct? While I understand, you indicate it's only a few Kb=2E > > I think it's cruft/(unnecessary)overhead=2E Which, in and of itself > > seems insignificant=2E But in the "big picture", and over many (100's) > > of builds/installations, is *not* insignificant=2E This also dismisses > > the security related work, maintaining extra un(used|needed) material=2E > > I suppose some will think that I'm just being nit-picky=2E But IMHO > > I'm not=2E This sort of thing, if overlooked, *does* affect the bottom > > line=2E > >=20 > > Thanks again, Johannes! > >=20 > > P=2ES=2E I have nothing against Wayland=2E I'm just not ready to run it > > on anything "production" related, just yet=2E :-) > >=20 > > --Chris > >=20 >=20 > The key is to have it in a state that easy to maintain and allows people = to > install it using pkg install without conflicting with X, so you can switc= h > back and forth easily=2E I'm also not ready to switch to wayland yet (favor= ite > window manager not available, so many custom configurations I came up wit= h > over the years etc=2E), but giving users an easy way to test it (or use it,= as > it's becoming more and more mainstream now) is a good thing=2E=20 >=20 > Having a modern, working, out of the box desktop (read: no custom kernel > builds, no need to use ports, a laptop is the point of first contact for = many > potential users) is incredibly important for proliferation and compared t= o > the total size of binaries required to run X, I think the usefulness of > providing wayland easily outweighs the extra overhead=2E I wouldn't argue, nor did I argue those points=2E Who would? But muddying up the individual ports (gtk3 for example) doesn't make anything lighter, or better=2E Quite the contrary=2E IMHO Wayland should probably be added=2E Who doesn't like more options? But, if it's coming to FreeBSD, and the ports tree=2E It should isolate itself as it's own port(s), and include those dependencies it requires=2E This is supposed to be policy=2E IOW if I decide to include gtk3 as an option to one of the ports I'm installing as a run/ build depends, I don't want it installing Wayland, mesa, and a bunch of other things I don't need -- no matter how small they might be=2E Doesn't that just make sense for *any* port? That's really my only possible gripe=2E :-) --Chris >=20 > Yours, > Michael >=20 > >> >> > >> >> > >> >> /Johannes > >> > > >> > > >>>=20 > >=20 > > From owner-freebsd-ports@freebsd.org Thu Dec 21 01:30:10 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6E8FE8EC59 for ; Thu, 21 Dec 2017 01:30:10 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 939166CCEE for ; Thu, 21 Dec 2017 01:30:10 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa12.server.lan (via HTTP); Thu, 21 Dec 2017 02:30:09 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: freebsd-ports@freebsd.org Subject: Re: Vote: making wayland=on default Content-Type: text/plain; charset=UTF-8 Date: Thu, 21 Dec 2017 02:30:09 +0100 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:xWM+LVeAg8zZzDko0oDRrgB4cN5zw09MN2TNSbSUJuN nac77lvVy4RyYrGwQvG/t+/IeS0IhO+pnDNdyRqptZT+8lM/J7 X4+AqeuCS966Sp0z1NZ+USn8rJIovtFMvSNqtKmGkDmcjNDQcr tgADLyxkOK1sU+CKNXT2qhzOU1fmPc+tHvz5UfJKqcO2oqDWG9 GWRgNsW5lTTo76sRU07J0+y9P8qyW+vrgwr62xen2kBRFJK6y8 BkLJ4G8PXgsIK4WDcBOG2HVt05YAkvC7IUoxK5vxBLEtIavUHy yxZXEs= X-UI-Out-Filterresults: notjunk:1;V01:K0:QjnxLsb3tU0=:2Vj7MiLmF21lxwn2E8x5xK bGU7nfann4eddJQmnpcp3MwW2k8elOxOOxpnhPjcr0YZ2ktosQfxTwFrtHwhDT8GSG4YwdP2t H9oyjh2mQWPlndUkBrcDwhqkeh67XnqKu94sLEol/tPD+N+xLtFmYtX6SbZ8YShm6CsHW2ofq T4M8TuY8YUx9PSI3IjPTlw3gajQg3AojMH1W88RYkrQW3VtXJ9MjlaBY+o1dJ0NGdASaLtKjh GQI3tVFYl/654KTgW2G5fbRiuHsQvp5xZWjP/zlaxPR+q1K00YwGiahVBJLFAOOguFfmmzzsF z8vg55PluHQqPkvkl1pD1xKr6ph16phzcAxzU1kTH8qydLXh3VgY+lWPUdSQnk+lNMH7qMw9U lJypYCz2BetJUKnyxYGFmImBBYX0sikr9P1AE/+e3vyd+r9we9/EpOcRxTNLFWhGm7jXf8B98 XNteelkPHxiLxZu+NV62pXbh47Ckai4Bs4TSsTSwZ8iCPGhSFEneqxyz3sFRiUBrdWH4L5oxA Wv0lFSCAZJtJTe8DGWEcRJIvk8u4jcXY5YDfh/Gfq2b 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: Thu, 21 Dec 2017 01:30:10 -0000 Wayland should not be mixed in with other code like gtk3, gtk2, gnome related programs. This will immediately create bloat. Wayland does remove a lot of unneeded obsolete code that is in Xorg, that is put in there by principle, and not much else. If gtk creeps into Wayland, those benefits will be lost. The current eagerness about wanting Wayland is centered around gtk. This will quickly harm the project. Wayland should work on top of xlibs that are not obsolete. Wayland shouldn't be made the default until small window managers like antiwm, blackbox, bspwm, ctwm, cwm, i3, jwm, qtile, vtwm and others like this work on it. It should also work on fluxbox and enlightenment first. Wayland on FreeBSD shouldn't be centered around GNU, gtk or Gnome. I would say make a Wayland-gtk package offshoot, but this will also quickly ruin things. Wayland should stay clean, and allow modular components on top of it, that don't spread out bloat dependencies out. Wayland should keep the same habit as Xorg, with the exception of keeping obsolete hardware code. From owner-freebsd-ports@freebsd.org Thu Dec 21 02:16:27 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BC4AE937E8 for ; Thu, 21 Dec 2017 02:16:27 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 379116EFB4 for ; Thu, 21 Dec 2017 02:16:27 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id 36E25E937E7; Thu, 21 Dec 2017 02:16:27 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 368D2E937E6 for ; Thu, 21 Dec 2017 02:16:27 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 282E96EFB2 for ; Thu, 21 Dec 2017 02:16:26 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id vBL2GQ4g059462 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 20 Dec 2017 18:16:26 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me To: "ports@freebsd.org" From: Yuri Subject: Again, flavors or options? Message-ID: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> Date: Wed, 20 Dec 2017 18:16:25 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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: Thu, 21 Dec 2017 02:16:27 -0000 I have the port for the digital currency. It has 3 parts that install non-intersecting file sets: daemon, cli, qt-ui. The commonality: same repository, same build options, same license, mostly same port options. I am attracted to the idea to use flavors to let users choose which part do they want: FLAVORS=default daemon qt cli "default" will install all of them, others will install individual parts. Option list will be slightly different for each flavor. One alternative: only have port options. Then some options can't be conditional on which parts are built. Another alternative: 3 slave ports. I don't like this idea at all. Do you think flavors are a good fit for this task? Yuri From owner-freebsd-ports@freebsd.org Thu Dec 21 03:19:47 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B617DE989D5 for ; Thu, 21 Dec 2017 03:19:47 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 10A9A71762 for ; Thu, 21 Dec 2017 03:19:46 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 7262 invoked by uid 89); 21 Dec 2017 03:19:44 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@46.244.226.155) by mail.grem.de with ESMTPA; 21 Dec 2017 03:19:44 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Vote: making wayland=on default From: Michael Gmelin X-Mailer: iPhone Mail (14G60) In-Reply-To: Date: Thu, 21 Dec 2017 04:19:43 +0100 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <48EBD5AF-1FF6-442D-9365-0A93CD63E88A@grem.de> References: To: portmaster@BSDforge.com 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: Thu, 21 Dec 2017 03:19:47 -0000 > On 21. Dec 2017, at 02:14, Chris H wrote: >=20 > On Thu, 21 Dec 2017 00:29:40 +0100 "Michael Gmelin" said= >=20 >> > On 20. Dec 2017, at 18:50, Chris H wrote: >> > > On Wed, 20 Dec 2017 17:13:43 +0000 s= aid >> > > On Wed, 20 Dec 2017 16:23:59 +0000 "Johannes Lundberg" >> > said >> > >> On Wed, Dec 20, 2017 at 4:08 PM, Chris H w= rote: >> >> > On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" >> >> >> >> > said >> >> > >> >> >> Hi >> >> >> >> >> >> I want to suggest that we enable wayland by default. In current sta= te >> >> >> having some parts of wayland in ports is basically useless the >> >> >> end-users themselves re-build gtk30 and mesa-libs with wayland >> >> >> enabled. >> >> >> >> >> >> libwayland-egl.so from mesa-libs and the extra libraries and header= s >> >> >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg= >> >> >> packages. (might be something more that I missed) >> >> >> >> >> >> Personally I see no reason not to make it default on, even with >> >> >> flavors coming up. For any Desktop user (as well as embedded device= s >> >> >> like IVI-systems and whatnot), Wayland is the future. There's no >> >> >> escaping that. >> >> >> >> >> >> Wayland has been quite usable on FreeBSD for over a year now but >> >> >> access to it is limited due to the extra efforts required to use it= . >> >> >> >> >> >> If we are to compare with the other guys, several Linux distros are= >> >> >> already switching to wayland-based compositors as default window >> >> >> server. >> >> >> >> >> >> What do you think? >> >> > >> >> > IMHO it's (still) too early. Too much other X(org) related work >> >> > still being completed. In fact, I just built a new dev box to >> >> > track 12 (CURRENT), and this was the first time I was not required >> >> > to pre generate a config file for Xorg. I was only required to >> >> > inform /usr/local/etc/X11/xorg.conf.d/nvidia-driver.conf that >> >> > the driver was "nvidia", not "nv". Everything work(s|ed) famously. >> >> > A real treat. I'm also a bit concerned about the progress (or lack >> >> > there of) on network transparency. >> >> > I (personally) could conceive it as a KERNEL OPTION, but would not >> >> > want to see it in the Default kernel. >> >> > >> >> > Well, those are *my* thoughts. Because you asked. :-) >> >> > >> >> > --Chris >> >> > >> >> Thanks for your feedback! >> >> Just to clarify, we're not talking about changing any defaults that >> >> would impact or change users' choice of desktop. We only want to >> >> enable Wayland compositors as an alternative to X (leaving X as is). >> >> This does not break or modify anything existing. It does not force you= >> >> to do anything differently. It simply adds a couple of libraries that >> >> you won't use unless you run Wayland stuff (if you install qt5/gtk30 >> >> and mesa-libs). >> >> The reference to Linux making it default might have been unclear. >> >> Since FreeBSD doesn't have a default desktop, it's hard to change. It >> >> is and will continue to be up to the end user what they choose to use,= >> >> we only add more options :) >> > Thanks for the informative reply, Johannes. >> > So no kernel (libs/extensions)? >> > Hmm, gtk3. Why is it not possible to make the Wayland stuff a sub >> > package/option? I think this is the preferred track/policy anyway. >> > I do this for all the ports I currently maintain. IOW any DE related >> > stuff I install, that uses GNOME related material, will pull in gtk3, >> > which, as I understand you say, will ultimately pull in Weston,mesa,...= >> > is that correct? While I understand, you indicate it's only a few Kb. >> > I think it's cruft/(unnecessary)overhead. Which, in and of itself >> > seems insignificant. But in the "big picture", and over many (100's) >> > of builds/installations, is *not* insignificant. This also dismisses >> > the security related work, maintaining extra un(used|needed) material. >> > I suppose some will think that I'm just being nit-picky. But IMHO >> > I'm not. This sort of thing, if overlooked, *does* affect the bottom >> > line. >> > > Thanks again, Johannes! >> > > P.S. I have nothing against Wayland. I'm just not ready to run it >> > on anything "production" related, just yet. :-) >> > > --Chris >> > The key is to have it in a state that easy to maintain and allows peopl= e to >> install it using pkg install without conflicting with X, so you can switc= h >> back and forth easily. I'm also not ready to switch to wayland yet (favor= ite >> window manager not available, so many custom configurations I came up wit= h >> over the years etc.), but giving users an easy way to test it (or use it,= as >> it's becoming more and more mainstream now) is a good thing. Having a mod= ern, working, out of the box desktop (read: no custom kernel >> builds, no need to use ports, a laptop is the point of first contact for m= any >> potential users) is incredibly important for proliferation and compared t= o >> the total size of binaries required to run X, I think the usefulness of >> providing wayland easily outweighs the extra overhead. > I wouldn't argue, nor did I argue those points. Who would? But muddying up= > the individual ports (gtk3 for example) doesn't make anything lighter, or > better. Quite the contrary. IMHO Wayland should probably be added. Who > doesn't like more options? But, if it's coming to FreeBSD, and the ports > tree. It should isolate itself as it's own port(s), and include those > dependencies it requires. This is supposed to be policy. IOW if I decide > to include gtk3 as an option to one of the ports I'm installing as a run/ > build depends, I don't want it installing Wayland, mesa, and a bunch of > other things I don't need -- no matter how small they might be. It's supposed to be insignificant in size, a small price compared to maintai= ning multiple versions of these ports. Just for comparison, on my system, gt= k3 from pkg.freebsd.org requires about 450MiB including dependencies. > Doesn't that just make sense for *any* port? That's really my only possibl= e > gripe. :-) >=20 I understand the ambition to keep things lean and in general I agree with th= is approach of only installing what you need, but having multiple versions/f= lavors of certain libraries doesn't seem viable (multiple flavors? Multiple v= ersions of the same package? Building applications twice?). That's why I'm i= n favor of it. Anyway, I think the positions are clear and that's all Johannes asked about.= Yours, Michael > --Chris >> Yours, >> Michael >> >> >> >> >> >> >> >> >> /Johannes >> >> > >> >> > >> >>> > > >=20 >=20 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Dec 21 04:35:08 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 746E1E9E600 for ; Thu, 21 Dec 2017 04:35:08 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.io-tx.com", Issuer "AlphaSSL CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48FF674677; Thu, 21 Dec 2017 04:35:08 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (authenticated bits=0) by io-tx.com (8.15.2/8.15.2) with ESMTPSA id vBL4Z2AE033422 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Dec 2017 22:35:02 -0600 (CST) (envelope-from ted@io-tx.com) Date: Wed, 20 Dec 2017 22:35:02 -0600 (CST) From: Ted Hatfield To: Kevin Oberman cc: Matthias Andree , Sunpoet Po-Chuan Hsieh , FreeBSD Ports ML , Eugene Grosbein Subject: Re: Procmail got updated! In-Reply-To: Message-ID: References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.99.2 at io-tx.com X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=5.0 on io-tx.com tests=ALL_TRUSTED, AWL, T_RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 user=root X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on io-tx.com 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: Thu, 21 Dec 2017 04:35:08 -0000 On Wed, 20 Dec 2017, Kevin Oberman wrote: > On Wed, Dec 20, 2017 at 4:19 PM, Matthias Andree > wrote: > >> Am 20.12.2017 um 06:40 schrieb Eugene Grosbein: >>> On 20.12.2017 01:03, Matthias Andree wrote: >>> >>>> Dear Ted, Eugene, >>> [skip] >>> >>> What happened with old good "Tools, not policy" thing? >>> >>> >> >> It's simpler than that, no policy involved. >> >> The tool had a hollow head, and broke after several years of banging it, >> and the former tool maker told the public it's out of warranty (never >> was in due to it being free) and not being fixed any more, and should be >> scrapped. >> > > It still works (painfully) and is used by many. They would be wise to > stop, but it is not the job of the project to force them to do so, > > I do think that a pkg-message with "Here there be dragons! Proceed at your > own risk. dropmail is a MUCH safer (and easier) path." would be > appropriate. I don't think it is the job of the project to force people to > replace it if they think they know what they are doing. Of course, bitrot > or similar may take it before long. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 I still use sendmail/procmail for all of my systems. If it's up to a vote I would vote to keep procmail as a valid port. That being said I am not a port maintainer and I wouldn't presume to tell them what to maintain as I am not the one doing the actual work. However based upon my experience I am betting that there are a lot of systems still out there that are still using procmail. I think if you choose to drop support for procmail you should do as Kevin suggests and give a warning and a firm date when support will stop. This will give people a chance to update their systems appropriately. Ted Hatfield From owner-freebsd-ports@freebsd.org Thu Dec 21 05:07:47 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F6FAEA0BC0 for ; Thu, 21 Dec 2017 05:07:47 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 721957576D; Thu, 21 Dec 2017 05:07:45 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 629fa4f2 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 20 Dec 2017 22:07:44 -0700 (MST) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Procmail got updated! From: Adam Weinberger In-Reply-To: <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> Date: Wed, 20 Dec 2017 22:07:42 -0700 Cc: Eugene Grosbein , Ted Hatfield , freebsd-ports@freebsd.org, Sunpoet Po-Chuan Hsieh Content-Transfer-Encoding: 7bit Message-Id: References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> To: Matthias Andree X-Mailer: Apple Mail (2.3445.5.20) 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: Thu, 21 Dec 2017 05:07:47 -0000 > On 20 Dec, 2017, at 17:19, Matthias Andree wrote: > > Am 20.12.2017 um 06:40 schrieb Eugene Grosbein: >> On 20.12.2017 01:03, Matthias Andree wrote: >> >>> Dear Ted, Eugene, >> [skip] >> >> What happened with old good "Tools, not policy" thing? > > It's simpler than that, no policy involved. > > The tool had a hollow head, and broke after several years of banging it, > and the former tool maker told the public it's out of warranty (never > was in due to it being free) and not being fixed any more, and should be > scrapped. I'm a little unsettled by this discussion, because it is moving into territory with which we have very little precedent. And the precedent that it would establish is not wholly within our mandate. FreeBSD ports provides the best available versions of software to run on FreeBSD---we have traditionally been very conservative in deprecating software. The mere fact that there are better alternatives is not sufficient reason to take it away from people. When it ceases to work, or is intolerably dangerous, then it is incumbent upon us to act. You know far, far more about the intricacies of email than I do, Matthias, so please correct me if I am incorrect here, but I'm not aware of procmail being unsuitably dangerous for admins who make a conscious decision to use it. I'm not a fan of the message it would send: taking the port away from our users tells them that we don't trust their ability to decide what to do with their systems. I would far prefer that we educate our users about the alternatives, and provide a suitable warning for procmail, not censor it entirely. We can plaster the port with warnings and recommendations for people to switch, or set DEPRECATED without an EXPIRATION_DATE, but taking it away from people establishes a precedent that I wouldn't feel great about. Procmail was the standard for an incredibly long time, and there are undoubtedly many shops that rely upon it. # Adam -- Adam Weinberger adamw@adamw.org http://www.adamw.org From owner-freebsd-ports@freebsd.org Thu Dec 21 06:05:58 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AEDEEA46B5 for ; Thu, 21 Dec 2017 06:05:58 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 36012774AC for ; Thu, 21 Dec 2017 06:05:58 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3343DEA46B4; Thu, 21 Dec 2017 06:05:58 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32E79EA46B3 for ; Thu, 21 Dec 2017 06:05:58 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF69C774A8 for ; Thu, 21 Dec 2017 06:05:57 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id r143so26531609lfe.13 for ; Wed, 20 Dec 2017 22:05:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=A4EkN2mNN32QJnDmKWQbpOx8eyg48a4qtziUrx/SCBg=; b=jTRT0Qu1z+2WniHF6yGGWQrR4feJAuDVfchEdGwu5NijGoDdHtAuACluh1zSz5pnM9 I29t7m3FqIAwPiOrUqWwNpjAkzM6dcMe5PRG7cjftvWkYgMuaKszQJ+X9nY3ISu9xRGo 8HpJo2HMhnRki+1lsKJhTDeqDXH9ujgSBjAjGoj8oh2SiNY2x0LrHjutO0QapGu0VeMk gKBcgWgTKU5mGYR4oso8G/KcfzFeC2sI06VJ9V5qLHXKP4ZNKIJRnjD4p7ZKeRft595O PfchcwWGRarzz7o7MPiyLfkOSXrain1BBOAq8y3RDiDQgzljdLyt4m6KXY0KGE/td9Se Oy5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=A4EkN2mNN32QJnDmKWQbpOx8eyg48a4qtziUrx/SCBg=; b=s2r+WihO8KR0JQakCyo1O6M3HWLQ66DoFLeV2ukz1/eKD3fDKxoTLD8wtGvt3uoIGT Z5QG69JBy9hdVc0CL4OwJH4CRx7ixEs9TRFVeplf2U4+8F9+n2zt3kvs9+wg6onlsYru v2rpotJPCWS2BViIBlm3S/A6sKXJf+MQhBBkSv/x6Hbep+5TD6PgWHM5jSyr/J3uGiGf DigUEHHVi/CA+W6BJ3rQRunrLksyVOgGM78gdWMP+7ooXwXnYBFAaayujsVb99PGpxHi UdBrrYzNY7Mi/ZxW5Y+srpe0CJRSbltKxkJgbQK6o+VJKqphFXFdSiRO0mUqOosD2yk2 yyPA== X-Gm-Message-State: AKGB3mLvmUxnc3GzwYJxHMOVn7zv5yogWZxDq/UOY6FLEWmU/fQwroYR X0aaoqiuYQ9YHqSfxotlYFAIOOqAWbZlAykwuaBoAg== X-Google-Smtp-Source: ACJfBotTFDTdwGZzMo9BKDVqwhbrLeLiB3BmIY4tWwM6E6B2TSlbM8tuDIKoPRzaf+WmIrXtWQl8N8wFkAPKgPWELP4= X-Received: by 10.25.15.217 with SMTP id 86mr6082896lfp.67.1513836355388; Wed, 20 Dec 2017 22:05:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.163.145 with HTTP; Wed, 20 Dec 2017 22:05:54 -0800 (PST) Received: by 10.25.163.145 with HTTP; Wed, 20 Dec 2017 22:05:54 -0800 (PST) In-Reply-To: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> References: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> From: Freddie Cash Date: Wed, 20 Dec 2017 22:05:54 -0800 Message-ID: Subject: Re: Again, flavors or options? To: Yuri Cc: FreeBSD Ports Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Thu, 21 Dec 2017 06:05:58 -0000 On Dec 20, 2017 6:16 PM, "Yuri" wrote: I have the port for the digital currency. It has 3 parts that install non-intersecting file sets: daemon, cli, qt-ui. The commonality: same repository, same build options, same license, mostly same port options. I am attracted to the idea to use flavors to let users choose which part do they want: FLAVORS=default daemon qt cli "default" will install all of them, others will install individual parts. Option list will be slightly different for each flavor. One alternative: only have port options. Then some options can't be conditional on which parts are built. Another alternative: 3 slave ports. I don't like this idea at all. Do you think flavors are a good fit for this task? Sounds like a textbook example of sub-packages. Until then, slave ports would be the next-best thing as that provides separate packages that can be installed. Cheers, Freddie From owner-freebsd-ports@freebsd.org Thu Dec 21 07:04:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E450E80797 for ; Thu, 21 Dec 2017 07:04:46 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from viclamta28p.bpe.bigpond.com (viclamta28p.bpe.bigpond.com [203.38.21.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7657E79486 for ; Thu, 21 Dec 2017 07:04:43 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from smtp.telstra.com ([10.10.26.4]) by viclafep28p-svc.bpe.nexus.telstra.com.au with ESMTP id <20171221054352.QORL21415.viclafep28p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com> for ; Thu, 21 Dec 2017 16:43:52 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtuddrgeehgdelvdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfupfevtfgpvffgnffuvfftteenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffujgfkfhgfgggtsehttddttddtredvnecuhfhrohhmpeffrghvvgcujfhorhhsfhgrlhhluceouggrvhgvsehhohhrshhfrghllhdrohhrgheqnecukfhppeduuddtrddugedurdduleefrddvfeefnecurfgrrhgrmhephhgvlhhopegrnhgvuhhrihhnrdhhohhrshhfrghllhdrohhrghdpihhnvghtpeduuddtrddugedurdduleefrddvfeefpdhmrghilhhfrhhomhepoegurghvvgeshhhorhhsfhgrlhhlrdho X-RG-VS-CLASS: clean Received: from aneurin.horsfall.org (110.141.193.233) by smtp.telstra.com (9.0.019.22-1) id 5A170C1805520CCA for freebsd-ports@freebsd.org; Thu, 21 Dec 2017 16:43:52 +1100 Received: from aneurin.horsfall.org (localhost [127.0.0.1]) by aneurin.horsfall.org (8.15.2/8.15.2) with ESMTP id vBL5hqM7026366 for ; Thu, 21 Dec 2017 16:43:52 +1100 (EST) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by aneurin.horsfall.org (8.15.2/8.15.2/Submit) with ESMTP id vBL5hpGm026363 for ; Thu, 21 Dec 2017 16:43:51 +1100 (EST) (envelope-from dave@horsfall.org) X-Authentication-Warning: aneurin.horsfall.org: dave owned process doing -bs Date: Thu, 21 Dec 2017 16:43:51 +1100 (EST) From: Dave Horsfall To: FreeBSD Ports Subject: Re: Procmail got updated! In-Reply-To: Message-ID: References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) X-GPG-Public-Key: http://www.horsfall.org/gpgkey.pub X-GPG-Fingerprint: 05B4 FFBC 0218 B438 66E0 587B EF46 7357 EF5E F58B X-Home-Page: http://www.horsfall.org/ X-Witty-Saying: "chmod 666 the_mode_of_the_beast" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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: Thu, 21 Dec 2017 07:04:46 -0000 On Wed, 20 Dec 2017, Adam Weinberger wrote: > I'm a little unsettled by this discussion, because it is moving into > territory with which we have very little precedent. And the precedent > that it would establish is not wholly within our mandate. Am I the only one who remembers the kerfuffle over "jive" being de-ported (to coin a phrase)? No technical reason whatsoever, but apparently it upset someone's delicate sensibilities, so there's sort of a precedent. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." From owner-freebsd-ports@freebsd.org Thu Dec 21 07:26:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B77F0E81D22 for ; Thu, 21 Dec 2017 07:26:18 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 39CFD7A078; Thu, 21 Dec 2017 07:26:17 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.64.131]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MSIf1-1eXbS41wIl-00TXRm; Thu, 21 Dec 2017 08:25:07 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 4854023D202; Thu, 21 Dec 2017 08:25:00 +0100 (CET) Subject: Re: Procmail got updated! To: Adam Weinberger Cc: Eugene Grosbein , Ted Hatfield , freebsd-ports@freebsd.org, Sunpoet Po-Chuan Hsieh References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> From: Matthias Andree Message-ID: Date: Thu, 21 Dec 2017 08:24:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE X-Provags-ID: V03:K0:ZVXLCfCET1igDVwIIabvLeKftt+zP524+sCjE8YlSWwxvD29KpQ 6uf8SZ7udJIQvfFqPmh2B251S7rDEjhl4oGVL+/YWr7AVEcMOFrE9Na4ng8WtegvJHJ7jr9 ChRE9zs2dM3s4NzJOfJRNpPF2qYzty1Y0TE5Ubgk6Vq7XTeP/VNucbx69lx6hJk8cqOECtX 0EjKbr+E6aGvXsM3+pKzg== X-UI-Out-Filterresults: notjunk:1;V01:K0:9MG8y0cSJmE=:EtwFZHkUgXto2x8RVn5gg6 qbdIyay5gGcnzzUzt5QFF3QgwiPPHXeYRtuF4gAv0OV5tXyFb7NvIkYMNA6okld7gI8857LMQ d9aQGiMqg1wAmXdhy9U+3zLGovfWTE4n/kklWejYxnCeXoJ+HtCWeVX9RxsrhSycaP9hQKOnU fw8Htn4gTDeZJ1kxUj+5OVdn/qE1kcahLWfmkRBI1JWZYPApnIzeHiNXuQhA7e1gGRx8fqAzj LY5ghiYARAW412eUya+GbgYssCjafyx/XApNB0K6Ch1KDOdz0SwaohfviPU7PfQWlAGtB5l0v U76Da5soyJarxs9uZt2KGkGXB/BuSEupJTKOGC19djNvsX2xyHpoIKnurz+xT8s6yCR63IkK+ FY6duih1+qZpWOx44bwgFIDUBxnUMfeSVhKVdv9MMOLFNrjbM9X5OwDqT7GMzswhW6kjq1aad Q81bMjrzu2Yefm+Vh2nzWQCUg7SwAXodm/rwe1aYqYozktcxO5hzSP5TSCSw6l0Zqxj+WcKrQ m/rW2i7Of48Omr35x5oyzYT2FwapQ4aQcWMCIVVgCPO2yXzfB+2wQ+hPn64WnxB/zMf761Ke2 blrPXaK3JB8kESFRhuCb8k5hoSASu4aznOY/3elxbS7O5BM8zUntQAw/NHqQ0OGPNpgrUWTOO ufGrfHLltogwn+zpCYhUQlW/p7mJ0Iaowy3YnijwXVPjwE1/rXTJtF2Q7DOfdo9jQnsPOG9a1 48UrRwndNprmJ4Fh+VRiKeMqAbm1cKd98UpKb7/HBlM2lcxnsuH2eMAKDdr4oD9J1ZoQJccXA 0D37XqT7tQz65FpbZRk7w6TO9R1Dk1WqazqYN4Wdeep0uTW24Y= 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: Thu, 21 Dec 2017 07:26:18 -0000 Am 21.12.2017 um 06:07 schrieb Adam Weinberger: >> On 20 Dec, 2017, at 17:19, Matthias Andree >> wrote: >> >> Am 20.12.2017 um 06:40 schrieb Eugene Grosbein: >>> On 20.12.2017 01:03, Matthias Andree wrote: >>> >>>> Dear Ted, Eugene, >>> [skip] >>> >>> What happened with old good "Tools, not policy" thing? >> >> It's simpler than that, no policy involved. >> >> The tool had a hollow head, and broke after several years of banging i= t, >> and the former tool maker told the public it's out of warranty (never >> was in due to it being free) and not being fixed any more, and should = be >> scrapped. > > I'm a little unsettled by this discussion, because it is moving into > territory with which we have very little precedent. And the precedent > that it would establish is not wholly within our mandate. > > FreeBSD ports provides the best available versions of software to run > on FreeBSD---we have traditionally been very conservative in > deprecating software. The mere fact that there are better alternatives > is not sufficient reason to take it away from people. When it ceases > to work, or is intolerably dangerous, then it is incumbent upon us to > act. You know far, far more about the intricacies of email than I do, > Matthias, so please correct me if I am incorrect here, but I'm not > aware of procmail being unsuitably dangerous for admins who make a > conscious decision to use it. > is all i= t needs to mount the various mentioned cases, such as dangerous, bitrotten and whatever other arguments have been asked for. Given two CVEs and another crasher fixed in 3.22_5, that is reason enough to reconsider. We either need to take responsibility and have the port audited and someone paid to maintain it properly, or remove it, or at least we need to move it into the poison cabinet and lock it up (i. e. set DEPRECATED due to missing upstream maintenance and FORBIDDEN + NOPACKAGE due to it being dangerous), This is not to belittle ache@ (until 2011) or sunpoet@s and the contributors' efforts, but really about the upstream software that we are shipping. From owner-freebsd-ports@freebsd.org Thu Dec 21 07:26:31 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09446E81D3F for ; Thu, 21 Dec 2017 07:26:31 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id E89227A0EF for ; Thu, 21 Dec 2017 07:26:30 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: by mailman.ysv.freebsd.org (Postfix) id E7E97E81D3E; Thu, 21 Dec 2017 07:26:30 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6F35E81D3C for ; Thu, 21 Dec 2017 07:26:30 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by mx1.freebsd.org (Postfix) with ESMTP id 770287A0EA for ; Thu, 21 Dec 2017 07:26:29 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp121-45-66-21.bras1.adl6.internode.on.net (HELO leader.local) ([121.45.66.21]) by ipmail07.adl2.internode.on.net with ESMTP; 21 Dec 2017 17:56:24 +1030 Subject: Re: Again, flavors or options? To: Yuri Cc: FreeBSD Ports Mailing List References: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> From: Shane Ambler Message-ID: <58e6b5e1-f2c4-1e07-6cb3-82253bd7e13a@ShaneWare.Biz> Date: Thu, 21 Dec 2017 17:56:21 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit 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: Thu, 21 Dec 2017 07:26:31 -0000 On 21/12/2017 16:35, Freddie Cash wrote: > On Dec 20, 2017 6:16 PM, "Yuri" wrote: > > I have the port for the digital currency. It has 3 parts that install > non-intersecting file sets: daemon, cli, qt-ui. The commonality: same > repository, same build options, same license, mostly same port options. > > I am attracted to the idea to use flavors to let users choose which part do > they want: FLAVORS=default daemon qt cli As I said in my first answer, flavours changes the dependencies not the options of the port, eg a flavour using py27 another using py36 I don't think there is a way to have different options enabled for different flavours, each flavour will use the same options. Until we have the ability to break a single port into multiple packages that can be installed separately, you either have options for each item or a different port for each. So you could make the daemon and cli enabled as default, which will be available in the standard repos, then the qt-gui as an option the user needs to enable and build themselves. To simplify maintaining multiple related ports, you can use the same Makefile for each by setting up the others as slave ports, see 5.10 of the porters handbook. By setting a variable in the slave, you can use logic tests to control what varies for each port in the one Makefile. > "default" will install all of them, others will install individual parts. > Option list will be slightly different for each flavor. > > One alternative: only have port options. Then some options can't be > conditional on which parts are built. You have several options to logically control what options are enabled. You can find several possibilities in 5.13 of the porters handbook. from 5.13.3.7 - OPT1_IMPLIES= OPT2 # this means when you enable OPT1, OPT2 will automatically be turned on from 5.13.3.8 - OPT1_PREVENTS= OPT2 # this prevents enabling OPT1 and OPT2 at the same time You can use the standard logic available in any Makefile - .if ${PORT_OPTIONS:MOPT1} && ${PORT_OPTIONS:MOPT2} # make adjustments for both options being on .endif You also get custom build targets based on options (5.13.3.12) - post-patch-OPT1-on: ${REINPLACE_CMD} -e 's|opt2=True|opt2=False|' ${WRKSRC}/configure -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-ports@freebsd.org Thu Dec 21 08:18:00 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25387E850EA for ; Thu, 21 Dec 2017 08:18:00 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 058787BAC3 for ; Thu, 21 Dec 2017 08:18:00 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 03362E850E9; Thu, 21 Dec 2017 08:18:00 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02EA3E850E8 for ; Thu, 21 Dec 2017 08:18:00 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (prod2.absolight.net [79.143.243.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B58E37BAC2 for ; Thu, 21 Dec 2017 08:17:59 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 723CABDD2F; Thu, 21 Dec 2017 09:17:56 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id 65370BDD2D; Thu, 21 Dec 2017 09:17:55 +0100 (CET) Subject: Re: Again, flavors or options? To: Yuri , "ports@freebsd.org" References: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: <8801756c-bc4f-3832-3468-d826b4884aeb@FreeBSD.org> Date: Thu, 21 Dec 2017 09:17:58 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ym3Hx7ZSGvzns8ip8HosTDNK1AdlUuYqn" 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: Thu, 21 Dec 2017 08:18:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ym3Hx7ZSGvzns8ip8HosTDNK1AdlUuYqn Content-Type: multipart/mixed; boundary="VRWwN2ZEis3Lp5ROBDvCMh3qF0t99FMKA"; protected-headers="v1" From: Mathieu Arnold To: Yuri , "ports@freebsd.org" Message-ID: <8801756c-bc4f-3832-3468-d826b4884aeb@FreeBSD.org> Subject: Re: Again, flavors or options? References: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> In-Reply-To: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> --VRWwN2ZEis3Lp5ROBDvCMh3qF0t99FMKA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 21/12/2017 =C3=A0 03:16, Yuri a =C3=A9crit=C2=A0: > Do you think flavors are a good fit for this task? Flavors is for when a port needs to be built differently multiple times. =46rom what you are saying, this can be built once and splitted up later,= this is subpackages. For now, you should use options, with what most people need as the default options. You could do slave ports, but I don't see the point. --=20 Mathieu Arnold --VRWwN2ZEis3Lp5ROBDvCMh3qF0t99FMKA-- --ym3Hx7ZSGvzns8ip8HosTDNK1AdlUuYqn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJaO245XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IOUsQAJGJF2SpUUCEto1GX68F3VD5 40vCvahgYdIvFX/b4rYmJg8u9K4nX+fMGknK1RK5MNkULnNSBBgQkSNFCOaHaZaj JF3Zl6z4QV/CmuLLtE+IXXknZx/bHfZEu0xFLlZXt4pd2hBDoyDV792AGgoaNTz/ Wa8uIFDOC0A2MOVnoUcwCtAl55pukKtOkl8H52rAcrP0hqzqKuCpby4SVQdqenHB gwpaUiRijA7O4qhHQRGn3Lufr1DN+3ww7YNCjc+BB7zcjTv9tROBheuAvWvIfSU8 EicAIyQlvmZkVMmMGzd9Y4ES4Jvx+UOb2xau/NK5HEbhfgtNOSBd5B7Vv53vnoDz aU5n41GhTN2OGqsYZQTZ7wpXOGSMUuc6n8r62WFEV5LVgkieSc41rqFytKWYKonU uv9Npi48zRC5krmdfHbOXNrd0zmxopU7KLIQu9lrFBiezklUDwHM96ONcF4nSh7J BL3y45Kj0sOrFGgs16rRNOxXoB2WFIyeFAKz3QtxBGMOUv9un2lbziAGGJts/lJg KV9Z3hnIP9cHMI81tynYesgMsx4766yESYSiNG5Y5AlNcCPpqhR7zJKteFG6EMRr mh+2EQ31+lh2zkmnF1jKBt1pufTQ0MnthhV7E0SXTBfvfKsBrHcFdBi1bT3IU+4W VCydEZcZ9+XGyh226ZcG =ygk3 -----END PGP SIGNATURE----- --ym3Hx7ZSGvzns8ip8HosTDNK1AdlUuYqn-- From owner-freebsd-ports@freebsd.org Thu Dec 21 08:50:35 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE263E86E4B for ; Thu, 21 Dec 2017 08:50:35 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5100A7CF49 for ; Thu, 21 Dec 2017 08:50:35 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22d.google.com with SMTP id s66so24508429wrc.9 for ; Thu, 21 Dec 2017 00:50:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ve9Bu8X9dI8Z0LUhZqAUlrzv1//VwiQTDsNJV0Jxzj8=; b=CV8qOOY4O+K4kQ7/kFlodGbG6uITlMYym6oKX/hjPznvb84limxuOssZgiVmsU/G3D Xg8ATKmVlnHmuoUHsiRfIGV9ZdZYmsKZnZLa77B746ci/6q8EPNf1gyma3Bu71I6gMsu KgPZyPJUA0lDJqulpFy2aOmSFECILSGxXYv8MDz8vfBXSZRh3gXmcCWlgKm10oGxN1cN S083UzUrafb9B9tpT+2e5iOSR7uWT1rdHItrEZ0YLzScGbhD6X65VKswS1g2Gsr8lOpZ MrQpelCgbV4ZhWSC7487Wyz13tMue89UGXX7cGNzc4VnJeSGwZkQEFY/tK9xX/+iiz2q IVsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ve9Bu8X9dI8Z0LUhZqAUlrzv1//VwiQTDsNJV0Jxzj8=; b=LEcQWc3gpoRa4ZcNtEa8k6cRYxfRTHz1+kw75TCaCyorAFffbED0NS1tz+77GI1ONW lOavEVj6Se6UmZ8enGdGqXwlQ3/LO3b25V8917Xr/nZJhsoLUTP+q4PmeM/HDNH0pDLV sw4Ka3id++Xd+ziuDglI7744c0OUAZhvqb3Zrls4iJtJj1f4qtSLcWVt+fwhpqiYwje1 Usvpw+aAPcMLmVZ/Q9XQ49+jIMb/aEgVm4Z0w9g1LR2Y9143bJ7KcDZlJfqmCYG0nIPp JFG+CzabvSNxWXthI1SIyMZNIS10Zkq74MggY1D9tNY3r+qz3uil7HKxk0Kp5ymaiL7t JFFA== X-Gm-Message-State: AKGB3mIERho88n/9O2UDKOwPRE+BDDYHLxyBbswjIJZaf7vlLf24gCzD GkvEYXNCsoHAYx9bPDT4CPTfm370oTzJEfaP1NY= X-Google-Smtp-Source: ACJfBouQGN9TPwIx52/Zz4N3o1+nYvF09W68KcnBC/BewhtFsqinlUqws2paLINcUESI1r/jtNcPGZsZmFzYWY2JPNI= X-Received: by 10.223.200.133 with SMTP id k5mr800890wrh.215.1513846233238; Thu, 21 Dec 2017 00:50:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.197.68 with HTTP; Thu, 21 Dec 2017 00:49:52 -0800 (PST) In-Reply-To: References: <9142f3e2938c84bd838b3764197226be@udns.ultimatedns.net> <8EDCE5A5-391E-4529-9713-79901739CC6F@grem.de> From: Johannes Lundberg Date: Thu, 21 Dec 2017 08:49:52 +0000 Message-ID: Subject: Re: Vote: making wayland=on default To: Kevin Oberman Cc: Michael Gmelin , portmaster@bsdforge.com, FreeBSD Ports ML Content-Type: text/plain; charset="UTF-8" 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: Thu, 21 Dec 2017 08:50:35 -0000 Thanks for the explanation, Kevin. I should have included more background information about what Wayland is and what turning it on by default means in more detail. Again to clarify, enabling Wayland by default does not change anything, it simply adds more options. Similar to adding a X11 window manager, you have the option to use it but don't have to... On Thu, Dec 21, 2017 at 12:27 AM, Kevin Oberman wrote: > On Wed, Dec 20, 2017 at 3:29 PM, Michael Gmelin wrote: > >> >> >> > On 20. Dec 2017, at 18:50, Chris H wrote: >> > >> > On Wed, 20 Dec 2017 17:13:43 +0000 >> said >> > >> > On Wed, 20 Dec 2017 16:23:59 +0000 "Johannes Lundberg" < >> johalun0@gmail.com> >> > said >> > >> >> On Wed, Dec 20, 2017 at 4:08 PM, Chris H >> wrote: >> >> > On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" >> >> >> >> > said >> >> > >> >> >> Hi >> >> >> >> >> >> I want to suggest that we enable wayland by default. In current state >> >> >> having some parts of wayland in ports is basically useless the >> >> >> end-users themselves re-build gtk30 and mesa-libs with wayland >> >> >> enabled. >> >> >> >> >> >> libwayland-egl.so from mesa-libs and the extra libraries and headers >> >> >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >> >> >> packages. (might be something more that I missed) >> >> >> >> >> >> Personally I see no reason not to make it default on, even with >> >> >> flavors coming up. For any Desktop user (as well as embedded devices >> >> >> like IVI-systems and whatnot), Wayland is the future. There's no >> >> >> escaping that. >> >> >> >> >> >> Wayland has been quite usable on FreeBSD for over a year now but >> >> >> access to it is limited due to the extra efforts required to use it. >> >> >> >> >> >> If we are to compare with the other guys, several Linux distros are >> >> >> already switching to wayland-based compositors as default window >> >> >> server. >> >> >> >> >> >> What do you think? >> >> > >> >> > IMHO it's (still) too early. Too much other X(org) related work >> >> > still being completed. In fact, I just built a new dev box to >> >> > track 12 (CURRENT), and this was the first time I was not required >> >> > to pre generate a config file for Xorg. I was only required to >> >> > inform /usr/local/etc/X11/xorg.conf.d/nvidia-driver.conf that >> >> > the driver was "nvidia", not "nv". Everything work(s|ed) famously. >> >> > A real treat. I'm also a bit concerned about the progress (or lack >> >> > there of) on network transparency. >> >> > I (personally) could conceive it as a KERNEL OPTION, but would not >> >> > want to see it in the Default kernel. >> >> > >> >> > Well, those are *my* thoughts. Because you asked. :-) >> >> > >> >> > --Chris >> >> > >> >> Thanks for your feedback! >> >> Just to clarify, we're not talking about changing any defaults that >> >> would impact or change users' choice of desktop. We only want to >> >> enable Wayland compositors as an alternative to X (leaving X as is). >> >> This does not break or modify anything existing. It does not force you >> >> to do anything differently. It simply adds a couple of libraries that >> >> you won't use unless you run Wayland stuff (if you install qt5/gtk30 >> >> and mesa-libs). >> >> The reference to Linux making it default might have been unclear. >> >> Since FreeBSD doesn't have a default desktop, it's hard to change. It >> >> is and will continue to be up to the end user what they choose to use, >> >> we only add more options :) >> > Thanks for the informative reply, Johannes. >> > So no kernel (libs/extensions)? >> > Hmm, gtk3. Why is it not possible to make the Wayland stuff a sub >> > package/option? I think this is the preferred track/policy anyway. >> > I do this for all the ports I currently maintain. IOW any DE related >> > stuff I install, that uses GNOME related material, will pull in gtk3, >> > which, as I understand you say, will ultimately pull in Weston,mesa,... >> > is that correct? While I understand, you indicate it's only a few Kb. >> > I think it's cruft/(unnecessary)overhead. Which, in and of itself >> > seems insignificant. But in the "big picture", and over many (100's) >> > of builds/installations, is *not* insignificant. This also dismisses >> > the security related work, maintaining extra un(used|needed) material. >> > I suppose some will think that I'm just being nit-picky. But IMHO >> > I'm not. This sort of thing, if overlooked, *does* affect the bottom >> > line. >> > >> > Thanks again, Johannes! >> > >> > P.S. I have nothing against Wayland. I'm just not ready to run it >> > on anything "production" related, just yet. :-) >> > >> > --Chris >> > >> >> The key is to have it in a state that easy to maintain and allows people >> to install it using pkg install without conflicting with X, so you can >> switch back and forth easily. I'm also not ready to switch to wayland yet >> (favorite window manager not available, so many custom configurations I >> came up with over the years etc.), but giving users an easy way to test it >> (or use it, as it's becoming more and more mainstream now) is a good thing. >> >> Having a modern, working, out of the box desktop (read: no custom kernel >> builds, no need to use ports, a laptop is the point of first contact for >> many potential users) is incredibly important for proliferation and >> compared to the total size of binaries required to run X, I think the >> usefulness of providing wayland easily outweighs the extra overhead. >> >> Yours, >> Michael > > > There seems to be general confusion on what Wayland is and what it does. > Anyone who worked with X11 back in the R4 and R5 days probably understands > the issues with the client/server protocol. I remember all of the > optimizations needed to get it to perform even passably on VMS, most of > which went into R6. But the protocol is still painfully primitive and > awkward in today's world. It really has no concept of compositors and that > makes everything much more expensive on both the server and client sides. I > really expected something like Wayland to show up 15 or 20 years ago. > > Putting Wayland into the system has a minimal cost in disk space. Unless > you choose to use it, it has no impact on application performance or size. > It mostly means that, if you want to use Wayland, you can o so without > rebuilding lots of stuff from ports. The packages will have be built with > ll of the required linkages. Does not matter what desktop you use, though > many of them may not yet work well (or at all) with Wayland, many will and > you wilol be able to try Wayland out easily. > > YES!!! Wayland support should be present when available. It's all upside. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Dec 21 08:55:26 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B484CE87469 for ; Thu, 21 Dec 2017 08:55:26 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9F09E7D4DE for ; Thu, 21 Dec 2017 08:55:26 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9E576E87468; Thu, 21 Dec 2017 08:55:26 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E09FE87467 for ; Thu, 21 Dec 2017 08:55:26 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3F57D4DD; Thu, 21 Dec 2017 08:55:26 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id vBL8tPY8007876 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 21 Dec 2017 00:55:25 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: Again, flavors or options? To: Mathieu Arnold , "ports@freebsd.org" References: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> <8801756c-bc4f-3832-3468-d826b4884aeb@FreeBSD.org> From: Yuri Message-ID: <5abfbdc3-acc2-1c73-44e8-f47b48fdcb1e@rawbw.com> Date: Thu, 21 Dec 2017 00:55:24 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <8801756c-bc4f-3832-3468-d826b4884aeb@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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: Thu, 21 Dec 2017 08:55:26 -0000 On 12/21/17 00:17, Mathieu Arnold wrote: > Flavors is for when a port needs to be built differently multiple times. > From what you are saying, this can be built once and splitted up later, > this is subpackages. For now, you should use options, with what most > people need as the default options. You could do slave ports, but I > don't see the point. Is there an ETA for sub-packages? Yuri From owner-freebsd-ports@freebsd.org Thu Dec 21 08:57:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0457E8772C for ; Thu, 21 Dec 2017 08:57:49 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 883FC7D621 for ; Thu, 21 Dec 2017 08:57:49 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 84B7BE8772B; Thu, 21 Dec 2017 08:57:49 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 845CEE8772A for ; Thu, 21 Dec 2017 08:57:49 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (prod2.absolight.net [79.143.243.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C21D7D620; Thu, 21 Dec 2017 08:57:48 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 2587ABDD25; Thu, 21 Dec 2017 09:57:47 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id 674B7BDD1E; Thu, 21 Dec 2017 09:57:46 +0100 (CET) Subject: Re: Again, flavors or options? To: Yuri , Mathieu Arnold , "ports@freebsd.org" References: <85f87eb1-ab21-e802-866c-93d7edbfb92a@rawbw.com> <8801756c-bc4f-3832-3468-d826b4884aeb@FreeBSD.org> <5abfbdc3-acc2-1c73-44e8-f47b48fdcb1e@rawbw.com> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: Date: Thu, 21 Dec 2017 09:57:42 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <5abfbdc3-acc2-1c73-44e8-f47b48fdcb1e@rawbw.com> Content-Type: text/plain; charset=utf-8 Content-Language: fr Content-Transfer-Encoding: quoted-printable 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: Thu, 21 Dec 2017 08:57:49 -0000 Le 21/12/2017 =C3=A0 09:55, Yuri a =C3=A9crit=C2=A0: > On 12/21/17 00:17, Mathieu Arnold wrote: >> Flavors is for when a port needs to be built differently multiple time= s. >> =C2=A0From what you are saying, this can be built once and splitted up= later, >> this is subpackages. For now, you should use options, with what most >> people need as the default options. You could do slave ports, but I >> don't see the point. > > > Is there an ETA for sub-packages? When it is done. --=20 Mathieu Arnold From owner-freebsd-ports@freebsd.org Thu Dec 21 09:04:48 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15263E87F91 for ; Thu, 21 Dec 2017 09:04:48 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BFAD7DD95; Thu, 21 Dec 2017 09:04:47 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBL94Xft009994 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Dec 2017 10:04:33 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: rkoberman@gmail.com Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id vBL94QMW072107; Thu, 21 Dec 2017 16:04:26 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Procmail got updated! To: Kevin Oberman , Matthias Andree References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> Cc: Sunpoet Po-Chuan Hsieh , FreeBSD Ports ML , Ted Hatfield From: Eugene Grosbein Message-ID: <5A3B791A.6020304@grosbein.net> Date: Thu, 21 Dec 2017 16:04:26 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_Q_PLUS autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_Q_PLUS Date: is over 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** 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: Thu, 21 Dec 2017 09:04:48 -0000 On 21.12.2017 07:35, Kevin Oberman wrote: >>> What happened with old good "Tools, not policy" thing? >> >> It's simpler than that, no policy involved. >> >> The tool had a hollow head, and broke after several years of banging it, >> and the former tool maker told the public it's out of warranty (never >> was in due to it being free) and not being fixed any more, and should be >> scrapped. > > It still works (painfully) and is used by many. They would be wise to > stop, but it is not the job of the project to force them to do so, > > I do think that a pkg-message with "Here there be dragons! Proceed at your > own risk. dropmail is a MUCH safer (and easier) path." would be > appropriate. +1 > I don't think it is the job of the project to force people to > replace it if they think they know what they are doing. Of course, bitrot > or similar may take it before long. From owner-freebsd-ports@freebsd.org Thu Dec 21 09:06:41 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACCBEE88135 for ; Thu, 21 Dec 2017 09:06:41 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 403B27DEA0; Thu, 21 Dec 2017 09:06:40 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBL96Xwg010029 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Dec 2017 10:06:33 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: ted@io-tx.com Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id vBL96THa072707; Thu, 21 Dec 2017 16:06:29 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Procmail got updated! To: Ted Hatfield , Kevin Oberman References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> Cc: Matthias Andree , Sunpoet Po-Chuan Hsieh , FreeBSD Ports ML From: Eugene Grosbein Message-ID: <5A3B7995.1060500@grosbein.net> Date: Thu, 21 Dec 2017 16:06:29 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_Q_PLUS autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_Q_PLUS Date: is over 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** 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: Thu, 21 Dec 2017 09:06:41 -0000 On 21.12.2017 11:35, Ted Hatfield wrote: > I think if you choose to drop support for procmail you should do as > Kevin suggests and give a warning and a firm date when support will stop. There is nothing to stop. We have plenty software working but maintained by nobody and it is not a big deal. Let it work until it really break. No dates needed. From owner-freebsd-ports@freebsd.org Thu Dec 21 09:17:16 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2D92E88B08 for ; Thu, 21 Dec 2017 09:17:16 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E82F67E6C9; Thu, 21 Dec 2017 09:17:15 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBL9GwEa010128 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Dec 2017 10:16:59 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: matthias.andree@gmx.de Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id vBL9GlGx075704; Thu, 21 Dec 2017 16:16:47 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Procmail got updated! To: Matthias Andree , Adam Weinberger References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> Cc: Ted Hatfield , freebsd-ports@freebsd.org, Sunpoet Po-Chuan Hsieh From: Eugene Grosbein X-Enigmail-Draft-Status: N1110 Message-ID: <5A3B7BFF.2020202@grosbein.net> Date: Thu, 21 Dec 2017 16:16:47 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_Q_PLUS autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_Q_PLUS Date: is over 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** 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: Thu, 21 Dec 2017 09:17:16 -0000 On 21.12.2017 14:24, Matthias Andree wrote: >>>> What happened with old good "Tools, not policy" thing? >>> >>> It's simpler than that, no policy involved. >>> >>> The tool had a hollow head, and broke after several years of banging it, >>> and the former tool maker told the public it's out of warranty (never >>> was in due to it being free) and not being fixed any more, and should be >>> scrapped. >> >> I'm a little unsettled by this discussion, because it is moving into >> territory with which we have very little precedent. And the precedent >> that it would establish is not wholly within our mandate. >> >> FreeBSD ports provides the best available versions of software to run >> on FreeBSD---we have traditionally been very conservative in >> deprecating software. The mere fact that there are better alternatives >> is not sufficient reason to take it away from people. When it ceases >> to work, or is intolerably dangerous, then it is incumbent upon us to >> act. You know far, far more about the intricacies of email than I do, >> Matthias, so please correct me if I am incorrect here, but I'm not >> aware of procmail being unsuitably dangerous for admins who make a >> conscious decision to use it. >> > > is all it > needs to mount the various mentioned cases, such as dangerous, bitrotten > and whatever other arguments have been asked for. > > Given two CVEs and another crasher fixed in 3.22_5, that is reason > enough to reconsider. We either need to take responsibility and have the > port audited and someone paid to maintain it properly, or remove it, or > at least we need to move it into the poison cabinet and lock it up (i. > e. set DEPRECATED due to missing upstream maintenance and FORBIDDEN + > NOPACKAGE due to it being dangerous), > > This is not to belittle ache@ (until 2011) or sunpoet@s and the > contributors' efforts, but really about the upstream software that we > are shipping. We do not "ship" procmail. It is not part of FreeBSD. It is third-party software packaged for user's convenience without any guarantee. So, you demand we stop shipping any unmaintained software with our Ports & Packages? Absence of CVEs means nothing and almost any non-trivial software has bugs (axiom). From owner-freebsd-ports@freebsd.org Thu Dec 21 09:19:19 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09769E88DAE for ; Thu, 21 Dec 2017 09:19:19 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B576C7E950 for ; Thu, 21 Dec 2017 09:19:18 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3z2R0Z2YPkzb4K; Thu, 21 Dec 2017 10:19:10 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id hLoDPXt4teUe; Thu, 21 Dec 2017 10:19:04 +0100 (CET) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.madpilot.net (Postfix) with ESMTPSA; Thu, 21 Dec 2017 10:19:04 +0100 (CET) Subject: Re: Vote: making wayland=on default To: Niclas Zeising , freebsd-ports@freebsd.org References: From: Guido Falsi Message-ID: <34f699e2-b852-63fd-f6d6-a862a42569de@FreeBSD.org> Date: Thu, 21 Dec 2017 10:19:03 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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: Thu, 21 Dec 2017 09:19:19 -0000 On 12/20/2017 21:47, Niclas Zeising wrote: > On 12/20/17 10:20, Johannes Lundberg wrote: >> Hi >> >> I want to suggest that we enable wayland by default. In current state >> having some parts of wayland in ports is basically useless the >> end-users themselves re-build gtk30 and mesa-libs with wayland >> enabled. >> >> libwayland-egl.so from mesa-libs and the extra libraries and headers >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >> packages. (might be something more that I missed) >> >> Personally I see no reason not to make it default on, even with >> flavors coming up. For any Desktop user (as well as embedded devices >> like IVI-systems and whatnot), Wayland is the future. There's no >> escaping that. >> >> Wayland has been quite usable on FreeBSD for over a year now but >> access to it is limited due to the extra efforts required to use it. >> >> If we are to compare with the other guys, several Linux distros are >> already switching to wayland-based compositors as default window >> server. >> >> What do you think? >> > > > With my x11@ hat on. > > I have no problem with this, as long as the old xorg stuff keeps on > working, as you've stated they will do.  I do not have time to fix this > this week, but if you can help me prepare a patch we can perhaps get it > in after that (beginning of next week, in the days between Christmas and > new years).  Do you know which ports are affected by this, and have a > WAYLAND option?  We should also check, probably just in case, if portmgr > thinks an exp run is needed (I don't think so). > I recently added a WAYLAND option to the multimedia/libva port I maintain. I set it to off by default but that can be changes without problems. -- Guido Falsi From owner-freebsd-ports@freebsd.org Thu Dec 21 09:30:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88306E89ABD for ; Thu, 21 Dec 2017 09:30:25 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 491F77F120 for ; Thu, 21 Dec 2017 09:30:24 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 3z2RFT5XSgzDh4l; Thu, 21 Dec 2017 09:30:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1513848621; bh=kLcoEVrbiVU7Ilf1Yu+4WxVM 9uidkL8UEjmp19oBDZI=; b=AgfjqvE+Bzv6WOjIA2ojY5fHWOHYrjAt0a7mj5Fv 0W0ULFWXtV6N1uSgxfvB6RkvIodtx1LFhUKZdaNA46HJKvY/TJuZyq6JH3a6DNp2 W/4IXe5gBW4BRl+OZPuurbv5UtTo26mPxPYC0Z1148fFj2KvoKOUciDt9ux0/nsY y5s= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id w5y_Eu1QzLkt; Thu, 21 Dec 2017 09:30:21 +0000 (UTC) Received: from garnet.daemonic.se (unknown [94.246.95.140]) by mail.daemonic.se (Postfix) with ESMTPSA id 3z2RFS5lHfz62P2; Thu, 21 Dec 2017 09:30:20 +0000 (UTC) Subject: Re: Vote: making wayland=on default To: roberthuff@rcn.com, Yuri Cc: Johannes Lundberg , freebsd-ports@freebsd.org References: <3267de19-6e00-a72a-e2a7-abb322ccf7ac@rawbw.com> <23098.57983.262947.67141@jerusalem.litteratus.org> From: Niclas Zeising Message-ID: Date: Thu, 21 Dec 2017 10:30:20 +0100 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <23098.57983.262947.67141@jerusalem.litteratus.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Thu, 21 Dec 2017 09:30:25 -0000 On 12/20/17 23:21, roberthuff@rcn.com wrote: > > To the list: > I salute X for doing its job, but I have no brand loyalty. If > something comes along that is some combination of a) more robust, b) > faster, and c) as easy to install/manage I'll switch in a heartbeat. > (Smaller footprint would be nice too.) Is that Wayland? Fact not > (yet) in evidence. > Is Wayland-on-FreeBSD in active development? If so: where - > other than ports@ - do I go to check the /status quo/? > Wayland and xwayland is part of the x11@ umbrella. The mailing list used is freebsd-x11@freebsd.org Regards! -- Niclas From owner-freebsd-ports@freebsd.org Thu Dec 21 11:10:32 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F8F4E8EB27 for ; Thu, 21 Dec 2017 11:10:32 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0B2A12639 for ; Thu, 21 Dec 2017 11:10:32 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0A779E8EB25; Thu, 21 Dec 2017 11:10:32 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 086C1E8EB24 for ; Thu, 21 Dec 2017 11:10:32 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EEE772638 for ; Thu, 21 Dec 2017 11:10:31 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id vBLBAVZv069166 for ; Thu, 21 Dec 2017 11:10:31 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id vBLBAVRs069165; Thu, 21 Dec 2017 11:10:31 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201712211110.vBLBAVRs069165@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Thu, 21 Dec 2017 11:10:31 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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: Thu, 21 Dec 2017 11:10:32 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ audio/rosegarden | 17.04 | 17.12 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Thu Dec 21 12:44:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18A73E947A7 for ; Thu, 21 Dec 2017 12:44:14 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp205.alice.it (smtp205.alice.it [82.57.200.101]) by mx1.freebsd.org (Postfix) with ESMTP id A842464CB9 for ; Thu, 21 Dec 2017 12:44:13 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (87.1.57.7) by smtp205.alice.it (8.6.060.28) id 5A0F897307FFF4D5 for freebsd-ports@freebsd.org; Thu, 21 Dec 2017 13:44:05 +0100 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id vBLCi2aw071666 for ; Thu, 21 Dec 2017 13:44:02 +0100 (CET) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu From: Andrea Venturoli Subject: Re: Vote: making wayland=on default To: freebsd-ports@freebsd.org References: <3267de19-6e00-a72a-e2a7-abb322ccf7ac@rawbw.com> <23098.57983.262947.67141@jerusalem.litteratus.org> Message-ID: <813980de-b5f9-6834-e5ef-28bc76ee2f4c@netfence.it> Date: Thu, 21 Dec 2017 13:43:57 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <23098.57983.262947.67141@jerusalem.litteratus.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Thu, 21 Dec 2017 12:44:14 -0000 On 12/20/17 23:21, roberthuff@rcn.com wrote: First off, I'm not trying to bring up any flame... my questions are real and I'd really welcome good answers. > Yuri writes: > >> It appears that this is the case of fixing of something (xorg) >> that wasn't/isn't broken in the first place. And if it is >> considered broken, then how, in which way? I have the same questions Yuri has... I've always seen Wayland enthusiasts saying they can't stand X11 no more, but I've never seen them explain what's wrong with it. N.B. I'm not implying nothing is wrong, I just wish they explained their point. > You ask "Is it broken?". > I ask "Is there a better way?" > ... > I think of X the same way. Fine, I agree with this. So, in what ways is Wayland better? That said, I have nothing against having Wayland support by default. I'm still ssh-ing into remote boxes to run graphical applications and I don't want to see this go away... but I read this is not going to happen (yet?), so it's fine to me. bye av. From owner-freebsd-ports@freebsd.org Thu Dec 21 13:41:47 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B2C9E97D0C for ; Thu, 21 Dec 2017 13:41:47 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 500AC66FA0 for ; Thu, 21 Dec 2017 13:41:47 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x235.google.com with SMTP id b5so10713403itc.3 for ; Thu, 21 Dec 2017 05:41:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CwdvOfpZ678NshcYgzAfCkuENPtFdLkb+Mi6YAr5VXs=; b=E90Do6Za504ZwuFG9FSC5+mkeyKFaqY0Kcqsh088BtfKuQrFg4rTUrvUpNxpUL8cZR uM2oN7k3MKN/PwksYysE4U4n96o0rKqHHaxLTZZvgH1ifHYzZRDawiRKywCODsigYBsU V8ZCjLFQcEZIAMHWgZ4sYhEqqUaQc1PGKciTHndwfjdUe+Uy/lzovN3Vy6jwQnPCD2WB u6bB1ifAtuV0zVmXJv8SUq2GSN1xmQzm5hFC5DelcF5GJzZdVWFQxjEFLh6E7fEmjxXk jortun5bUz4FSbYp8GtMu7y94QNi1Tj1HqP8yBtfWG0c/aPcggL/w2XXQOI7WySnOQRg Zfxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CwdvOfpZ678NshcYgzAfCkuENPtFdLkb+Mi6YAr5VXs=; b=fvk4So+SpoO/AzeA6q6PTpZOHeb8OGOkxlwJPzqMV4Ri3MR9B+bRutYFArIBzhcm1F dJ34Zo7p1eD4u3+/tFL5orwveGtYZ+DRTnrZaCdETpiMA8hyJkM4iBJ9kYu1ypFBSb9X CcANa5/70Tsjr84Jd8WGu2VWTd8dlgPXSZ0dbYgvm/LrKgf2AJ8MEGKEuhrV9qjtzWys LPivZQ27MEdSKc9GE6xPVUzfdUnO0XAI7XxnkEnu7kwyFKB2RMI8FiEwVucIcysRuZJx selraAmOZxTr3ptfrDQkH+dMQhGNPM8JI9o7B7GmiI8srvzKLNgdVnovE2SNDkaMH/iu aHXA== X-Gm-Message-State: AKGB3mLIooRd25CLrwNMW11c6lTw7LOajGFiQ74QpWseWr3jk3UZLGKs WWtgIa0RWEo5/WOdEBXffx10XBfrdJ4Q4X5FsyU= X-Google-Smtp-Source: ACJfBosX2m4viJvkCFAW6t5B8+/80l0zRJCnQeFzhOvc93n6aUAj+tEbBGXSV0cjGOmLxihKSRYZ4kitXwlHfPpKAXU= X-Received: by 10.36.151.198 with SMTP id k189mr13437647ite.100.1513863706476; Thu, 21 Dec 2017 05:41:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Thu, 21 Dec 2017 05:41:45 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Thu, 21 Dec 2017 21:41:45 +0800 Message-ID: Subject: Re: Canberra To: Sid Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Thu, 21 Dec 2017 13:41:47 -0000 On Thu, Dec 21, 2017 at 8:37 AM, Sid wrote: > > Blubee blubeeme > > I'll work on it but let me get the port in the tree first, then I can > refine it. > > Just as i've done with my previous ports. > > > Sid > > a simple program that plays simple sounds like "Ding!" > > The problem with libcanberra is around pulseaudio and gstreamer. It is > also with how gtk, a Visual Graphical toolkit, is mixed in with an Audio > application. > > I was inspecting libcanberra and libcanberra-gtk3. > > audio/libcanberra-gtk3 takes care of canberra plugins for pulseaudio and > gstreamer. It also takes care of two gtk3 library files, one of which is a > module. Ports that really need gtk3 are tangled mostly upstream, and > require --enable-gtk3. Others ports require libcanberra-gtk3 for either > gtk3, pulseaudio or gstreamer. Some ports have audio/libcanberra-gtk3 as a > dependency, but don't need it. > > audio/libcanberra itself is not so bad. audio/libcanberra also works > without gtk20 in the test Makefile, which shouldn't be needed at all. So, > plain libcanberra without libcanberra-gtk3 is not complicated, because it > doesn't involve gtk3, pulseaudio, and gstreamer; it has gtk2 as a > dependency, which it doesn't need. > > > Sooner or later, a drop in replacement for libcanberra needs to be made > for all BSD's. It should use ogg files from audio/freedesktop-sound-theme. > Perhaps it can include simple pipe to play ogg and other audio files as > well. After investigating, libcanberra is suitable for the short term, and > anything that fails without libcanberra-gtk3 is an issue with the upstream > ports themselves. > I'll look at the libcanberra OSS backend and see if I get get the changes upstream then the libcanberra maintainer can update the port. From owner-freebsd-ports@freebsd.org Thu Dec 21 14:07:50 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9088E98FEA for ; Thu, 21 Dec 2017 14:07:50 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 69E6F67C88 for ; Thu, 21 Dec 2017 14:07:49 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from [134.76.11.221] (helo=email.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.80) (envelope-from ) id 1eS1Vi-0001aC-Kh; Thu, 21 Dec 2017 15:07:46 +0100 Received: from UM-EXCHT-A02.um.gwdg.de (134.76.9.211) by um-excht-a01.um.gwdg.de (134.76.9.210) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 21 Dec 2017 15:07:46 +0100 Received: from pc028.nfv.nw-fva.de (134.76.242.1) by email.gwdg.de (134.76.9.211) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 21 Dec 2017 15:07:45 +0100 Subject: Re: FLAVOR for Qt4 and Qt5 (was Re: Flavor or not for this port?) To: L.Bartoletti CC: References: <46cbd287-186f-9b92-f2a7-d6884c681040@gwdg.de> <37d007c1-0315-5b23-7357-5dc3fcb836fc@gwdg.de> <92d09009-64b3-695a-2282-5acb6ab169f0@tuxfamily.org> From: Rainer Hurling Message-ID: <0c490eef-a12b-7447-691e-41cd1b5bee24@gwdg.de> Date: Thu, 21 Dec 2017 15:07:40 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 8bit X-Spam-Level: - X-Virus-Scanned: (clean) by clamav 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: Thu, 21 Dec 2017 14:07:50 -0000 Hi Loïc, Am 19.12.2017 um 20:48 schrieb L.Bartoletti: > Hi, > > Here's my WIP > > https://gitlab.com/lbartoletti/freebsd_ports/tree/master/qwt6 Looks interesting to me. Do we agree, that the package should be named qwt6-qt[45], and not qwt-qt[45]? And shouldn't PORTNAME better be named qwt6 instead of qwt. If so, the port has to handle with DISTNAME in some way to fetch a file named qwt-. At least, the actual naming brings some problems, for example if one tries to fetch the distfile make distclean make FLAVOR=qt4 fetch make distclean make FLAVOR=qt5 fetch QWT is licensed under Qwt 1.0, which is a LGPL with three execptions[1]. There is no definition for this license in Mk/bsd.license.db.mk until now. I don't know, what is the right way to define this 'unknown' license in the port. Again, many thanks for your work on this port. Best wishes, Rainer [1] http://qwt.sourceforge.net/qwtlicense.html > > Regards > > > On 18.12.2017 22:57, L.Bartoletti wrote: >> Hi Rainer, >> >> I have made a try with subpackages with success, but I think it's >> better with flavor (like on OpenBSD). >> >> So, I have started to create flavors for this port. >> >> For now, I success for qt4 but not yet for qt5. >> >> Extract from my Makefile in progress: >> >> FLAVORS=    qt5 qt4 >> FLAVOR?= >> >> .if ${FLAVOR:Mqt5} >> PKGNAMESUFFIX=    -qt5 >> USE_QT5=    widgets gui core designer gui opengl svg xml buildtools >> printsupport concurrent >> PLIST=        ${PKGDIR}/pkg-plist.qt5 >> PLIST_SUB+=    QT_MKSPECDIR=lib/qt5/mkspecs >> DOCSDIR=    ${PREFIX}/share/doc/qwt6-qt5 >> .else >> PKGNAMESUFFIX=    -qt4 >> USE_QT4=     corelib gui opengl svg xml moc_build >> PLIST=        ${PKGDIR}/pkg-plist.qt4 >> PLIST_SUB+=    QT_MKSPECDIR=lib/qt4/mkspecs >> DOCSDIR=    ${PREFIX}/share/doc/qwt6-qt4 >> .endif >> >> Ther error for qt5: >> >> qwt-qt5-6.1.3 can't be installed: different Qt versions specified via >> USE_QT[4 5]. >> >> Regards. >> >> On 17.12.2017 10:12, Rainer Hurling wrote: >>> Am 02.11.2017 um 07:41 schrieb Rainer Hurling: >>>> Am 02.11.2017 um 07:13 schrieb L.Bartoletti: >>>>> Hi, >>>>> >>>>> I want to take x11-toolkits/qwt{5,6}-* >>>>> >>>>> Both are built for Qt4. I especially need qwt6 for Qt5. Since we have >>>>> flavors. Is it better to add a Qt5 flavor for Qwt6 or simply add a >>>>> x11-toolkits/qwt6-qt5 (like security/qtkeychain-qt{4,5} ?) >>>>> >>>>> Thanks. >>>>> >>>>> Regards. >>>>> >>>>> Loïc >>>> >>>> Hi Loïc, >>>> >>>> Thanks for your dedication. I am very interested in a qwt6-qt5 port, >>>> since it is needed for the upcoming version 3.0 of graphics/qgis :) >>>> >>>> Sorry for my inexperience. In case of adding the qwt6-qt5 as a flavor, >>>> should we expect any change or restriction in the way, it would be used >>>> as a dependency of e.g. QGIS? >>>> >>>> Thanks for any answer. >>>> >>>> Best wishes, >>>> Rainer >>> Hi Loïc, >>> >>> Again about x11-toolkits/qwt{5,6}-* >>> >>> Now, that we have our first real world experiences with FLAVORS, it >>> seems to be functional to use flavors in this context. Something like >>> >>> x11-toolkits/qwt6@qt4 >>> x11-toolkits/qwt6@qt5 >>> >>> A bit tricky could be, that USE_QT* are different in both cases: >>> >>> USE_QT4= corelib gui opengl svg xml moc_build >>> USE_QT5= core gui opengl svg xml printsupport qmake_build widgets >>> >>> What do you think? >>> >>> Best wishes, >>> Rainer From owner-freebsd-ports@freebsd.org Thu Dec 21 16:10:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0402EA0094 for ; Thu, 21 Dec 2017 16:10:59 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7970A6BFE8 for ; Thu, 21 Dec 2017 16:10:59 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 8E30EBDD2D; Thu, 21 Dec 2017 17:10:56 +0100 (CET) Received: from ogg.in.absolight.net (ogg.in.absolight.net [79.143.241.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id 55A5EBDD25; Thu, 21 Dec 2017 17:10:56 +0100 (CET) Subject: Re: FLAVOR for Qt4 and Qt5 (was Re: Flavor or not for this port?) To: "L.Bartoletti" , Rainer Hurling Cc: freebsd-ports@freebsd.org References: <46cbd287-186f-9b92-f2a7-d6884c681040@gwdg.de> <37d007c1-0315-5b23-7357-5dc3fcb836fc@gwdg.de> <92d09009-64b3-695a-2282-5acb6ab169f0@tuxfamily.org> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: <778b4f63-48c7-c717-6c9b-f3ca35c5232c@FreeBSD.org> Date: Thu, 21 Dec 2017 17:10:52 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Zf6fIIkm2ALx7Px8JLyB9nw7cdPA5I2cD" 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: Thu, 21 Dec 2017 16:10:59 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Zf6fIIkm2ALx7Px8JLyB9nw7cdPA5I2cD Content-Type: multipart/mixed; boundary="gEfuyNnCJ8Az8ua0jbcuH3xLeDUZ8lKlw"; protected-headers="v1" From: Mathieu Arnold To: "L.Bartoletti" , Rainer Hurling Cc: freebsd-ports@freebsd.org Message-ID: <778b4f63-48c7-c717-6c9b-f3ca35c5232c@FreeBSD.org> Subject: Re: FLAVOR for Qt4 and Qt5 (was Re: Flavor or not for this port?) References: <46cbd287-186f-9b92-f2a7-d6884c681040@gwdg.de> <37d007c1-0315-5b23-7357-5dc3fcb836fc@gwdg.de> <92d09009-64b3-695a-2282-5acb6ab169f0@tuxfamily.org> In-Reply-To: --gEfuyNnCJ8Az8ua0jbcuH3xLeDUZ8lKlw Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 19/12/2017 =C3=A0 20:48, L.Bartoletti a =C3=A9crit=C2=A0: > Hi, > > Here's my WIP > > https://gitlab.com/lbartoletti/freebsd_ports/tree/master/qwt6 As long as you are defining a default FLAVOR value, do it right: FLAVOR?=3D ${FLAVORS:[1]} There are a few stuffs that could be simplified, this works for both flavors:| | |PLIST=3D ${PKGDIR}/pkg-plist.${FLAVOR} PLIST_SUB+=3D QT_MKSPECDIR=3Dlib/${FLAVOR}/mkspecs DOCSDIR=3D ${PREFIX}/share/doc/qwt6-${FLAVOR} And this: ||@${REINPLACE_CMD} -e 's/__= QT_VERSION__/${FLAVOR:S/qt//}/g' ${WRKSRC}/qwtconfig.pri| || You are missing: qt4_CONFLICTS_INSTALL=3D qwt6-qt5 qt5_CONFLICTS_INSTALL=3D qwt6-qt4 --=20 Mathieu Arnold --gEfuyNnCJ8Az8ua0jbcuH3xLeDUZ8lKlw-- --Zf6fIIkm2ALx7Px8JLyB9nw7cdPA5I2cD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJaO90PXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85Iw1MP/Azq/r9SWy6nvPWCFzch/c8K HEJblKApVIlqyzOVEc7dSM1wc2BzGp2bWtFSut97HlhsDcB2Y7cT3o3tXoKuYNIe zjOOr4LIhL+AbPKFOI9WdqWu4OCNA8sBLFlm/unSd+KslhbEdFPhbBreU63cVThf AdkBGQ5qDh/X5fOVTl9GHpfc7JqBmAJvKZ+EzfQwYz1lC+RpxAHLsImkrekxnTR7 JWmsgrpT/Optug00lBotKqQjdA/Ajsgc8WTu0eV8h7Tk4lMkLF21k+n2ZLMrd2y+ E3tzuGmqgiXKztIdvG8QJeimBGIfCAJtCftYinR5BGi1hYHodXBeCGVJomI5gTT3 Jgmr0cHBDpuNNQj6LPlHz2Q2CJJJM1ywONjwV/BDms9dvznuUQ/RSOLbXpfIcezW 5DYN/D5DeU/eaA2/TPso8MvqPTWuqO36xbVXZDRJv9xGr6lvZgkYDFHC7W/ZSHFr bvIi7gRMwMT7wHKV1p2uPMOqpWb8ximWGejhGn0Gdri5f9NL1L0/SLjz403ScLo3 KRiS2GSa6Y6ROyUh8aE0N4gmLrmyQGKQBrMU5k3sQLvQYgD/V/0d3p+5N6d2IPyC LtcaAp3q4Xs1p0sUSPhcniB3HQFLx51LaNA3PESBi2hS/d9Omwpcp3VdGDmtJ5mV ovr+4wONj3X7R4J9qP7w =Sk8t -----END PGP SIGNATURE----- --Zf6fIIkm2ALx7Px8JLyB9nw7cdPA5I2cD-- From owner-freebsd-ports@freebsd.org Thu Dec 21 18:24:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F604E811F0 for ; Thu, 21 Dec 2017 18:24:18 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C20EE7223B for ; Thu, 21 Dec 2017 18:24:17 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa09.server.lan (via HTTP); Thu, 21 Dec 2017 19:24:09 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: freebsd-ports@freebsd.org, gurenchan@gmail.com Subject: Re: OSS Audio Content-Type: text/plain; charset=UTF-8 Date: Thu, 21 Dec 2017 19:24:09 +0100 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:vjAaFxVNgrfzPCMOcI6/15BAMCmGPRzw2Svt8dr6RP0 Sdez33VdY61iLeHNUllR7LVM1yvaxirBEJXjVieTvNEnEGxiiY kRpZRMmTbP/00dQzp16zmHu9SZgpKf/7q0BFeasXnUQ1UKBsVo QY/z5h0PSo7Ef6m9h1av8aRve7KBIb4ePmeRMmYO8bt+MYaXsX oIcW98Yt+5I3QsOMWROjGTXbfEcmUOOEgXKuYn7NxdAbUndw+n HRRUHctgibOFWu776E5KaiZO0BwBlU+zxdBAzN+4atg200LSTq iJUNyQ= X-UI-Out-Filterresults: notjunk:1;V01:K0:RnPXEfyhOuk=:uhiUyigbIpRRQQchH1nOeX gu69ZArLeHES3FGB73cFEMiKLfR/2hONKNScre7T6vzatdTiwWD0hUJgSsaqoIlw0jVOYzmcL ymbhkRUjpKdfIzCJli0ijrIlZI3WUMOvjdZGQLv0SNCH0HOGcD3IFQ//BDefBtfSFZcXnO0kh rkdJOlA51Z5YrnE7CtT0F4A0hKZvdMOrCGPxzueKZdvX74hqaOJ7Pf9X5L4if4jQ0OeqYK+6r oWtrgJ5f7LHXGHNtDVUw0kqNGUdK/Ujw/bcRsDoZnUtk6suzowuGCA7kPrhEqy9ox1OE6Uspv fIfqYRc+iLXOMZvEbwT3qrDA6ARg4gyYWEkcZRDD1L4YAq5+EuAqqlhBal/FWPJPSrq5CrJMB cKUtNcVR+wJCq0HfWqH/k0XZKp4SdTh4wj63hAmpIGS4fNk5qql/osLwvZROpKTkHZC2EKEZ5 gpQ7EJv9/DHQWR8yKt7V5L5Y2C7dokcBqwsOG5vULYvECW5UVUU/thdbnMwnea7I95Qxx9CAx v4p1f7yfDP2ltpIV6R6j4tWtBCTC3D3VkzxZX/Z7pwt 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: Thu, 21 Dec 2017 18:24:18 -0000 blubee blubeeme; Mon Dec 11 17:03:10 UTC 2017 > I'm taking a look at soundcard.h in /usr/include/sys/soundcard.h in FreeBSD > vs the soundcard.h in the offical OSS 4.01 > https://sourceforge.net/p/opensound/git/ci/master/tree/include/soundcard.h > It seems like there's been a lot of changes between FreeBSD 3.8ish version > and the 4.0 version. > I was grepping around to see if any other files included this soundcard.h > header and if updating to the latest would break any other programs. Can you find OSS version 4.1 or 4.2 in https://svn.freebsd.org/base/ for head/ or stable/? From owner-freebsd-ports@freebsd.org Thu Dec 21 18:46:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77F98E827B1 for ; Thu, 21 Dec 2017 18:46:40 +0000 (UTC) (envelope-from dmytro@posteo.net) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.posteo.de", Issuer "StartCom Class 3 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 36ED073283 for ; Thu, 21 Dec 2017 18:46:39 +0000 (UTC) (envelope-from dmytro@posteo.net) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id DB53320F1C for ; Thu, 21 Dec 2017 19:46:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1513881990; bh=rODtYE3tMiBWLxluHBbyOjUXDeINPKRwCPIUGcOgON4=; h=Date:From:To:Cc:Subject:From; b=SQgYsigYybNMAfphWpKYDioj8vczVfVABl3Y38enigojIfT15PyQMFBOJj1P8cCrd j37Px0u7EK9v7zcbwMdnbv1jU77rafnQ/avfIemB9utta/U2QcQMCcmmlWIrpJlDqp 7hoYq2tXADJBmcxriOi88vL1Up3zxo0E1jtVDuIzERPs0pyTNJCckDgTA32eY+t5/f NQS2tZpbkRt97+B/KrE8EOj6IZl9OZbWbKvA0xBkSk3B6VARSembNTVa0xd3lBFkh+ 1oBk0/IDVyqw6yh3SFD3YhS4D76KrrWKbB7wZ1ahOW4jTWlJmcH0/zSVa+P9RrJCYq iyYwFKW8pZrLA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3z2gb715Csz9rxk; Thu, 21 Dec 2017 19:46:27 +0100 (CET) Date: Thu, 21 Dec 2017 20:46:24 +0200 From: Dmytro Bilokha To: Stefan Esser Cc: Adam Vande More , Kevin Oberman , Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD Ports ML Subject: Re: Setting system user home directory Message-ID: <20171221184624.GA4279@wstan> References: <20171216094058.GA37778@wstan> <5A351515.1080805@quip.cz> <20171216135919.GA17551@wstan> <5A352BA5.9070403@quip.cz> <20171216170411.GA85559@wstan> <20171216185317.GA87289@wstan> <20171216200959.GA97697@wstan> <699d4702-2610-2d3c-fe32-0977a4f05bc2@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <699d4702-2610-2d3c-fe32-0977a4f05bc2@freebsd.org> User-Agent: Mutt/1.7.2 (2016-11-26) 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: Thu, 21 Dec 2017 18:46:40 -0000 On Wed, Dec 20, 2017 at 08:32:37PM +0100, Stefan Esser wrote: >Am 20.12.17 um 15:12 schrieb Adam Vande More: >> On Sat, Dec 16, 2017 at 2:10 PM, Dmytro Bilokha wrote: >> >>> Guys, thanks for your help. I've managed to adjust user's homedir >>> using pkg-install script. Now I'll try to move everything writable >>> from /usr/local to /var (as Miroslav suggested), test and submit the new >>> port version. >> >> I think you should do what makes sense for your application. The /var/db >> stuff is not a hard fast rule and it doesn't work well for many >> situations. Also it's mostly system related DB's that live there. It's >> not only some java related ports that live mostly under /usr but also >> things like postgres(at least used to). >> >> IMO, as long as you're not flagrantly violating hier(7), do what is best >> for your port. > >For a port that needs quite a large database (password hashes from accounts >that have been leaked), I implemented an option to initialize the application >by downloading the data files after the user had a chance to select a place >for the data (by editing the config file). The default is in /var/db, but the >user may prefer a home directory or some sub-directory of /usr/local/ ... > >Regards, STefan > Thanks, Stefan, it is also a nice approach. -- Dmytro Bilokha dmytro@posteo.net +38-050-607-41-43 From owner-freebsd-ports@freebsd.org Thu Dec 21 20:40:41 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E842E894DD for ; Thu, 21 Dec 2017 20:40:41 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C1A57777D7 for ; Thu, 21 Dec 2017 20:40:39 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x52716328.dyn.telefonica.de [82.113.99.40]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id vBLKMU12050707 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 21 Dec 2017 20:22:31 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x52716328.dyn.telefonica.de [82.113.99.40] claimed to be ultrabook.yoonka.com Subject: Re: Vote: making wayland=on default To: freebsd-ports@freebsd.org References: <48EBD5AF-1FF6-442D-9365-0A93CD63E88A@grem.de> From: Grzegorz Junka Message-ID: Date: Thu, 21 Dec 2017 20:22:25 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <48EBD5AF-1FF6-442D-9365-0A93CD63E88A@grem.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large 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: Thu, 21 Dec 2017 20:40:41 -0000 On 21/12/2017 03:19, Michael Gmelin wrote: > >> On 21. Dec 2017, at 02:14, Chris H wrote: >> >> On Thu, 21 Dec 2017 00:29:40 +0100 "Michael Gmelin" said >> >>>> On 20. Dec 2017, at 18:50, Chris H wrote: >>>>> On Wed, 20 Dec 2017 17:13:43 +0000 said >>>>> On Wed, 20 Dec 2017 16:23:59 +0000 "Johannes Lundberg" >>>> said >>>>>> On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote: >>>>>> On Wed, 20 Dec 2017 09:20:20 +0000 "Johannes Lundberg" >>>>> >>>>>> said >>>>>> >>>>>>> Hi >>>>>>> >>>>>>> I want to suggest that we enable wayland by default. In current state >>>>>>> having some parts of wayland in ports is basically useless the >>>>>>> end-users themselves re-build gtk30 and mesa-libs with wayland >>>>>>> enabled. >>>>>>> >>>>>>> libwayland-egl.so from mesa-libs and the extra libraries and headers >>>>>>> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >>>>>>> packages. (might be something more that I missed) >>>>>>> >>>>>>> Personally I see no reason not to make it default on, even with >>>>>>> flavors coming up. For any Desktop user (as well as embedded devices >>>>>>> like IVI-systems and whatnot), Wayland is the future. There's no >>>>>>> escaping that. >>>>>>> >>>>>>> Wayland has been quite usable on FreeBSD for over a year now but >>>>>>> access to it is limited due to the extra efforts required to use it. >>>>>>> >>>>>>> If we are to compare with the other guys, several Linux distros are >>>>>>> already switching to wayland-based compositors as default window >>>>>>> server. >>>>>>> >>>>>>> What do you think? >>>>>> IMHO it's (still) too early. Too much other X(org) related work >>>>>> still being completed. In fact, I just built a new dev box to >>>>>> track 12 (CURRENT), and this was the first time I was not required >>>>>> to pre generate a config file for Xorg. I was only required to >>>>>> inform /usr/local/etc/X11/xorg.conf.d/nvidia-driver.conf that >>>>>> the driver was "nvidia", not "nv". Everything work(s|ed) famously. >>>>>> A real treat. I'm also a bit concerned about the progress (or lack >>>>>> there of) on network transparency. >>>>>> I (personally) could conceive it as a KERNEL OPTION, but would not >>>>>> want to see it in the Default kernel. >>>>>> >>>>>> Well, those are *my* thoughts. Because you asked. :-) >>>>>> >>>>>> --Chris >>>>>> >>>>> Thanks for your feedback! >>>>> Just to clarify, we're not talking about changing any defaults that >>>>> would impact or change users' choice of desktop. We only want to >>>>> enable Wayland compositors as an alternative to X (leaving X as is). >>>>> This does not break or modify anything existing. It does not force you >>>>> to do anything differently. It simply adds a couple of libraries that >>>>> you won't use unless you run Wayland stuff (if you install qt5/gtk30 >>>>> and mesa-libs). >>>>> The reference to Linux making it default might have been unclear. >>>>> Since FreeBSD doesn't have a default desktop, it's hard to change. It >>>>> is and will continue to be up to the end user what they choose to use, >>>>> we only add more options :) >>>> Thanks for the informative reply, Johannes. >>>> So no kernel (libs/extensions)? >>>> Hmm, gtk3. Why is it not possible to make the Wayland stuff a sub >>>> package/option? I think this is the preferred track/policy anyway. >>>> I do this for all the ports I currently maintain. IOW any DE related >>>> stuff I install, that uses GNOME related material, will pull in gtk3, >>>> which, as I understand you say, will ultimately pull in Weston,mesa,... >>>> is that correct? While I understand, you indicate it's only a few Kb. >>>> I think it's cruft/(unnecessary)overhead. Which, in and of itself >>>> seems insignificant. But in the "big picture", and over many (100's) >>>> of builds/installations, is *not* insignificant. This also dismisses >>>> the security related work, maintaining extra un(used|needed) material. >>>> I suppose some will think that I'm just being nit-picky. But IMHO >>>> I'm not. This sort of thing, if overlooked, *does* affect the bottom >>>> line. >>>>> Thanks again, Johannes! >>>>> P.S. I have nothing against Wayland. I'm just not ready to run it >>>> on anything "production" related, just yet. :-) >>>>> --Chris >>>> The key is to have it in a state that easy to maintain and allows people to >>> install it using pkg install without conflicting with X, so you can switch >>> back and forth easily. I'm also not ready to switch to wayland yet (favorite >>> window manager not available, so many custom configurations I came up with >>> over the years etc.), but giving users an easy way to test it (or use it, as >>> it's becoming more and more mainstream now) is a good thing. Having a modern, working, out of the box desktop (read: no custom kernel >>> builds, no need to use ports, a laptop is the point of first contact for many >>> potential users) is incredibly important for proliferation and compared to >>> the total size of binaries required to run X, I think the usefulness of >>> providing wayland easily outweighs the extra overhead. >> I wouldn't argue, nor did I argue those points. Who would? But muddying up >> the individual ports (gtk3 for example) doesn't make anything lighter, or >> better. Quite the contrary. IMHO Wayland should probably be added. Who >> doesn't like more options? But, if it's coming to FreeBSD, and the ports >> tree. It should isolate itself as it's own port(s), and include those >> dependencies it requires. This is supposed to be policy. IOW if I decide >> to include gtk3 as an option to one of the ports I'm installing as a run/ >> build depends, I don't want it installing Wayland, mesa, and a bunch of >> other things I don't need -- no matter how small they might be. > It's supposed to be insignificant in size, a small price compared to maintaining multiple versions of these ports. Just for comparison, on my system, gtk3 from pkg.freebsd.org requires about 450MiB including dependencies. > >> Doesn't that just make sense for *any* port? That's really my only possible >> gripe. :-) >> > I understand the ambition to keep things lean and in general I agree with this approach of only installing what you need, but having multiple versions/flavors of certain libraries doesn't seem viable (multiple flavors? Multiple versions of the same package? Building applications twice?). That's why I'm in favor of it. > > Anyway, I think the positions are clear and that's all Johannes asked about. > > Yours, > Michael > Why Wayland can not be enabled by default the same way that byhyve was enabled by default, even before it was production ready, so that people could test how it works for them? Wayland isn't going anywhere, rather the opposite, and having it on by default will allow to catch issues earlier. If it doesn't break the existing stuff then isn't it a win-win situation? GrzegorzJ From owner-freebsd-ports@freebsd.org Fri Dec 22 02:56:24 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D162BE9FC01 for ; Fri, 22 Dec 2017 02:56:24 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33D6C63D0D for ; Fri, 22 Dec 2017 02:56:23 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.64.131]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MfBsk-1edgWi2Tf8-00Oqbp; Fri, 22 Dec 2017 03:50:14 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id F270D23D202; Fri, 22 Dec 2017 03:50:12 +0100 (CET) Subject: Re: Procmail got updated! To: Eugene Grosbein References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> From: Matthias Andree Cc: freebsd-ports@freebsd.org Message-ID: <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> Date: Fri, 22 Dec 2017 03:50:12 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <5A3B7BFF.2020202@grosbein.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE X-Provags-ID: V03:K0:x7dJbYoBqNzvX/4sslvsLTfzD1GxslVWRjyP5WAEaNd5ayS+Vgn IBcBSlCae95+lEDezpS7mE/4Z39Qhj8S++K5nWPmFGFXHghM8p7wUwlzfgbvlxpaPpvOExm H+FFoyNGDyIWL/C6SEQ17mXZ0AK6aBzzBIVNeLl3+p3tZCGMf2hoh3U5lrgUQ9iYtGH94n5 ddY5eO3fm9FYF7ZBZO6EA== X-UI-Out-Filterresults: notjunk:1;V01:K0:dduqE5buGag=:Uw6kNOXxH1QeWx6fRbKzZY 0dLq3za6FFp9CYztxlklozbp5qVNUbxO+11TIafro/NL3e0bcmzOdY4e4ymz/ojtNu1GPn6Z5 lSeCg1I4hBY3qKn8kpmEfhgDUZUTgYb+QlA2ubDnTJsSV+uXIphoiLed7n5LwK2vkyzAOWSmT D4EPOxACrg1kIxXf/ZJzMmG9D0YwWOTAIj8Ov8OrHzMKnNcMv5k39s5lKH9nO5UU9Sx8vcbyD veleQL1dtSZ0cG66NDVppTmPOCbTryEY4cNwt7mG7F19m1NSChAL9ANOuIu24f0bJriTVK0pC Y+YcCrIXI6KpeA5rcGoTgEgnY/4YXviMy0YQrvbarunVzH90NZQqF8+jGidX/ttrahH0qxGpI FD0LuHLAacmE/D8Bv7WCeBcdCpVq5pBlAdhwDJKWQlCPgeWm4Kz7XrZwtXRbYO1XU6otjWmRl KOqLrwNJojT/3UKE/srWZKyX6mM47X6venbCLlGkUFEs7m5FFv+6MeRDVRN5Brjv9LKM40k24 VMUX/lzpqah3NofgwDGe1xwYH3By5s2zRhEONzwimdoHf9zK/ro4o2bg+0RJbJD4RLvWDuAOH nO9KuueTcNzqTYzcLdRR44RNuKXOcxbu6xVe+C18huYsBVQzlbe0bYVR2cia1/JlugXMSPLCN 42efBDuwDNGBFQk41i6kAAvNnNneHy10kxcIwXtgbPNrtmYNk0FSOiecvl0IXW6/wqk7mHwC3 PSiO93uNpfRrzLKhO1Zqf1IlPTAxP+c16BycP3tlis5Jtr10pChkHiN/ElLDRfBjzSpTGJs3l Nu7li0yvWW/GltUTlzNnD1ZNb3lGN96zz8ZjtUFX0KFF3LdowY= 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: Fri, 22 Dec 2017 02:56:24 -0000 Am 21.12.2017 um 10:16 schrieb Eugene Grosbein: > So, you demand we stop shipping any unmaintained software with our Port= s & Packages? > Absence of CVEs means nothing and almost any non-trivial software has b= ugs (axiom). Eugene, these are attempts to distract from the argument, or to mount to fallacies. I do not intend to respond further to them or other of your messages in this thread. From owner-freebsd-ports@freebsd.org Fri Dec 22 04:45:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12FFFEA5AAD for ; Fri, 22 Dec 2017 04:45:18 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BEAAC673D6 for ; Fri, 22 Dec 2017 04:45:17 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa01.server.lan (via HTTP); Fri, 22 Dec 2017 05:45:08 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: "blubee blubeeme" Cc: "FreeBSD Ports" Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Fri, 22 Dec 2017 05:45:08 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:LC/wMlFBA+6m0BxncdyopEQYsDS94LpX6oiJlbjZuXx S0cQA5i9fTDWCAA+em60kdruS1z4m1SfAoXSgnyPKgEXc2Wu6V Ri6we54OCNoIV4IegvldGqcvoQq4mUhnPW/Kbu7tA+jgWXX58d dCRNxmJ1UA2CF4uA0dBUSNzysfFdFjy5zngn69KVSQuPm+a2jO 5oHdh+hAs36v8VbsJsuSdNbPWzLOjzoDKDMW2AimGa9QsJLs5U NZf9atNTlw8V/eqFymv+fyabgXtNRGxsqN+Cdp2rsv5jGalNW6 yy9Mt4= X-UI-Out-Filterresults: notjunk:1;V01:K0:30fCbJwaOSM=:mXCSf0yF824QZaSlNxL9id nkz1timlC/VQaTqhSfl/UqGhxotDi3xh2DTDyGBcfmY583GlxTweVNMi/JpYgi2Xuciij0skz AC8jrD60wYyRQ/qcjEWhjIL2E4FG+MNULcKL2BZsmj1RqneL8uZ54JKheGCPxqsqcDoEhOGhf cDhAn0FQiPfSD3VasN2fkLYQ8cCVBXSrlvmA8yZRw6j45mLKyWB0aT51hR6az/WPqgeq1ITEa srWn0xgpjlsBgnkgXX6TmHLpqLlbVHAZcC3+HlygJ5JbDe4ICaKlItBQ69LSB68Vca/utVEbF i5x41YeQdjnrDKmuHw6BRmza8Riu0VGliath/hA2vX/Mg6ImRqVQG1Dk+apISdrjZYzY3uyBs 4UTySzxv54+87oDoplpzV05ot67qmFQAILqZCQlHLH2VEYeENWTsZeQ9mmRK7kAD3zq4X7fC7 fdCKqjczXoPc2ma7s5kjKsJlNOIbvXDJF3ihap8+sC5h5bQr25Jxe1BXYitRgmyr9FOExOM7H hSn9NI2q31n4r54EnQXhpj1ehYWvFLtJWmyDsa6s+H/ 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: Fri, 22 Dec 2017 04:45:18 -0000 > Blubee blubeeme > I'll look at the libcanberra OSS backend and see if I get get the changes upstream then the libcanberra maintainer can update the port. >> Sid >> Sooner or later, a drop in replacement for libcanberra needs to be made for all BSD's. It should use ogg files from audio/freedesktop-sound-theme. Perhaps it can include simple pipe to play ogg and other audio files as well. After investigating, libcanberra is suitable for the short term, and anything that fails without libcanberra-gtk3 is an issue with the upstream ports themselves. I looked into it more. Canberra is meant only for sound (.oga, .wav), but graphical code is tied in heavily into it for XDG icons and graphics standards, so the problem is not just around gtk. The source code of libcanberra has many graphical files and lines, and its only binary /usr/local/bin/canberra-gtk-play (--file) requires the window display (which shouldn't be needed for sound, and no graphical interface), so it can't run from a root console (onto a non-root desktop). Icons and programs that need Canberra should just call it. Canberra has the ability to output a command, if for instance, the sound application fails. This should be output back to another program. libcanberra needs to fork, to have only audio components (to not rely on any graphical toolkit), but it is required for it to keep the same GPL license. I'll keep looking at it, and take notes on that. Then see if I can compile it, leaving out graphical components (I'm C code illiterate). Later on, it can be replaced completely by an OSS API of original code. While no FreeBSD ports currently use pulseaudio and gstreamer for libcanberra, that compatibility should stay in (as opposed to what I suggested previously). From owner-freebsd-ports@freebsd.org Fri Dec 22 06:10:15 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C163FE81724 for ; Fri, 22 Dec 2017 06:10:15 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 535896956D for ; Fri, 22 Dec 2017 06:10:14 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBM6A3XI018882 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 Dec 2017 07:10:04 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: matthias.andree@gmx.de Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id vBM69x4W045910 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 22 Dec 2017 13:09:59 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Procmail got updated! To: Matthias Andree References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> Cc: freebsd-ports@freebsd.org From: Eugene Grosbein Message-ID: <5A3CA1B5.2090907@grosbein.net> Date: Fri, 22 Dec 2017 13:09:57 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net 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: Fri, 22 Dec 2017 06:10:15 -0000 22.12.2017 9:50, Matthias Andree пишет: > Am 21.12.2017 um 10:16 schrieb Eugene Grosbein: > >> So, you demand we stop shipping any unmaintained software with our Ports & Packages? >> Absence of CVEs means nothing and almost any non-trivial software has bugs (axiom). > > Eugene, these are attempts to distract from the argument, or to mount to > fallacies. I do not intend to respond further to them or other of your > messages in this thread. That was real question, I like to know the answer. From owner-freebsd-ports@freebsd.org Fri Dec 22 08:09:08 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1B95E87BB9 for ; Fri, 22 Dec 2017 08:09:08 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 847156CA34 for ; Fri, 22 Dec 2017 08:09:08 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x22c.google.com with SMTP id t196so23726129iof.0 for ; Fri, 22 Dec 2017 00:09:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kecJcbD+h4AGNrknjqZtTG9hKWqPL2/BUv3YdQWaQSw=; b=FF0wmZHyrFlZweD8BO0giJHHvKZSZPDtPDxkofsdgX1JRUVr58VpJe+fTkRzdnDzAN 4m5G1LZtByr5/mwXpY5Uw4RCe3wVHzp60JeroostBpiKY5PNMGsIv9itm1oxl4V0KNY5 VmxMtiU7xQKNQ7PwUW0GgcrlhuyK2CMDVKFmFx+LZMl5WgQFKn20MbHtd7rV8coGk4uk IifLXlH9p3BvPW+FjfsxxihgYJFeIB5PS+Qgj+/WczLzqlWFOOrORSbpNpdbrfbfSq3w 6ByxNS4fJr/qkW2FH5+SpEcI4ai+EdDNNX+jLvZ1+e4rJI9A3Sk6tqzDYlyoO/UsgFoC APnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kecJcbD+h4AGNrknjqZtTG9hKWqPL2/BUv3YdQWaQSw=; b=iy+bXaIdE1eeLhzvpuA4ulFjCDrbTv6taSpOU89sqFWIOBeSLqHe5J9sm+NKiQpMdN bPMBrzEspkQYJt7P//MSn5pst5J+mgEQLFmT3W3VdVCBF2+6Wa/D/Ql87VctWXDcq8Ny 0NmnQmPjkafX2fVOKw/DYJjmHPQtD7gOdUveMD2Q6crylcFhBykvzcOGIjRKzJ5DUSCy fHyqv/y/B+ZKG/rbNF6aF55H8DS74APNQRDCmooJ9c6Gbm7OcguyPeL/2lIx+Bnx4Hun ThrjEmK0h2vbDnyOJ/y95+kc93EQqZSz5cRtHDbROx15IbCI4HxSrOhx4dprXjsyOxDd KaSw== X-Gm-Message-State: AKGB3mJPfu/ctcuhGejn2PgXcuQag/LRbefd0cic/X/BjDHlYceJciin B3qI94qnqsQpovY6SLwnhpC6/OosLxGOgu6mRNWQ6g== X-Google-Smtp-Source: ACJfBottiUnbpKXKK+vJdUpFJa0pkmi8dBwInHQ25WRPzUbhvd5GhVc7Ve0DK0IGzSug6241YvLhdXLCntOnRbB9tBM= X-Received: by 10.107.157.82 with SMTP id g79mr16708411ioe.296.1513930147707; Fri, 22 Dec 2017 00:09:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Fri, 22 Dec 2017 00:09:07 -0800 (PST) In-Reply-To: References: From: blubee blubeeme Date: Fri, 22 Dec 2017 16:09:07 +0800 Message-ID: Subject: Re: Canberra To: Sid Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 22 Dec 2017 08:09:08 -0000 On Fri, Dec 22, 2017 at 12:45 PM, Sid wrote: > > Blubee blubeeme > > I'll look at the libcanberra OSS backend and see if I get get the > changes upstream then the libcanberra maintainer can update the port. > > >> Sid > >> Sooner or later, a drop in replacement for libcanberra needs to be made > for all BSD's. It should use ogg files from audio/freedesktop-sound-theme. > Perhaps it can include simple pipe to play ogg and other audio files as > well. After investigating, libcanberra is suitable for the short term, and > anything that fails without libcanberra-gtk3 is an issue with the upstream > ports themselves. > > > I looked into it more. Canberra is meant only for sound (.oga, .wav), but > graphical code is tied in heavily into it for XDG icons and graphics > standards, so the problem is not just around gtk. > > The source code of libcanberra has many graphical files and lines, and its > only binary /usr/local/bin/canberra-gtk-play (--file) requires the window > display (which shouldn't be needed for sound, and no graphical interface), > so it can't run from a root console (onto a non-root desktop). > > Icons and programs that need Canberra should just call it. Canberra has > the ability to output a command, if for instance, the sound application > fails. This should be output back to another program. > > libcanberra needs to fork, to have only audio components (to not rely on > any graphical toolkit), but it is required for it to keep the same GPL > license. I'll keep looking at it, and take notes on that. Then see if I can > compile it, leaving out graphical components (I'm C code illiterate). Later > on, it can be replaced completely by an OSS API of original code. > > While no FreeBSD ports currently use pulseaudio and gstreamer for > libcanberra, that compatibility should stay in (as opposed to what I > suggested previously). > Who thought that was a good idea, now layer a few more audio layers and u have Linux[ism] to the max. Well, I think that it's not really worth it to go untangle that mess. It's okay if you're using a Gnome DE since it's all in there already but just to play a sound file you have to bring in all of this nonsense. If you want to keep going down the Gnome hole, go ahead let me know when you get to the OSS specific issues, if any. There's a lot more pressing issues that affect a larger surface area than a DE. Best From owner-freebsd-ports@freebsd.org Fri Dec 22 10:30:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E91F3E8EA0E for ; Fri, 22 Dec 2017 10:30:18 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 496B270E38 for ; Fri, 22 Dec 2017 10:30:17 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([78.48.162.120]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LxPgU-1f44vz40s6-0171FF; Fri, 22 Dec 2017 11:29:38 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 7037323D202; Fri, 22 Dec 2017 11:29:36 +0100 (CET) Subject: Re: Procmail got updated! To: freebsd-ports@freebsd.org, Eugene Grosbein References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> <5A3CA1B5.2090907@grosbein.net> From: Matthias Andree Message-ID: Date: Fri, 22 Dec 2017 11:29:36 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <5A3CA1B5.2090907@grosbein.net> Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:aag7xBYlarkLTCYq0DkpmxQz8/d6yK7mcyDBbnFqnIHAZoxA4ob waVAAHSVNWLUgtkwJk8dUK3rtIubyKRAJrSNQ6DuWK2hD48wzmi/AafL5usUsCq1lfr3iNJ GlxLa4o9HVQuS3ffhW3koybkUk+ngT9rR/Vg2BMaDsbQSCuIIXD4PnJeaOAQTFdQbyTzjxl pTET8mh3cHFDznZ/yq3Xg== X-UI-Out-Filterresults: notjunk:1;V01:K0:in4+eI9Ycdo=:AqXsVwAqXK1EiUSPL1SYnD UCq4RT0h4EUW1KwGhcVc+QdhT6OYgZZ/y74KQ6J+V8KI9sfjON0aL5zgyMLeibJrc5+1ENA3v JQOJDTK1W4we9qBajhF9QGI/0pjj/BP5PyI7KuW/4SWQ9/LuDudvmWsiuQ3nb3FbdC+lWHxDI 0VSxghomW50OxSyY8mTZKOXmPa27YncWHzxTNdkryUrZehePmpfLkFPyf9HdUYNJ5LRG4/14Q 42+T5sToH9X08Kk7vpEIj4voi7Ytk54LWo5NxsJhk83EcutbQ7BcGYwSy5DOCLzhtvk+mOjh5 5c7ahea/s8fUoJ5F9JueMQagvdV9KbuHn7zLa0qSM5oCTCyQeJdiWG8hZBeQw6e2+PBIZbErF J96RWJEQlMooUprdRUjD+2JgmLdhbm5O/MY0NPZXCP73B8hJwngREVpUJ5kxeyMlvfXkfLApr RSwH0cSZF1nlK16fO0rhcban7MeVufjmwCJfFpyhXKqfko8vUD6q5m9V+MmhLApJ2l/ZUqmbk ujFn31qPZDsEfFe6s2Vw20gvTqlIso/jeTkPM17qY2kngesw1rXDdmiXlHb9msjSwH611me1y 62gxN8jP1/zgo3e7ZKxkE1FUeuq6H+56aHVzUM9bY6o7SX1oMHonySaK/5+oblMdFKwWt5ijK wwYYRpUH7/hZA5VSB0urgeDx8egrXd4Kz5hPt/+L2ZCJZ5Kxnbu/kouOiCDnSFRsLZqLOHJlf LUe6pRI1CdFi8F0mtL+zBJccPCyKj5zMnGJWFZ4iWS/ZelY300jsghSb3sxrKT3dyeWGxsywz KzDoFu2GcR3qJC0SzMPdN23Fczvu3F7gLCWPe64h6oiU8Il1tE= 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: Fri, 22 Dec 2017 10:30:19 -0000 Am 22.12.2017 um 07:09 schrieb Eugene Grosbein: > 22.12.2017 9:50, Matthias Andree =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> Am 21.12.2017 um 10:16 schrieb Eugene Grosbein: >> >>> So, you demand we stop shipping any unmaintained software with our Po= rts & Packages? >>> Absence of CVEs means nothing and almost any non-trivial software has= bugs (axiom). >> Eugene, these are attempts to distract from the argument, or to mount = to >> fallacies. I do not intend to respond further to them or other of your >> messages in this thread. > That was real question, I like to know the answer. That generic question bears no relevance to the procmail case. From owner-freebsd-ports@freebsd.org Fri Dec 22 11:23:45 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9402E91500 for ; Fri, 22 Dec 2017 11:23:45 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B3B8072964 for ; Fri, 22 Dec 2017 11:23:45 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id B31FDE914FF; Fri, 22 Dec 2017 11:23:45 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2CC1E914FE for ; Fri, 22 Dec 2017 11:23:45 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A3E4B72963 for ; Fri, 22 Dec 2017 11:23:45 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id vBMBNjiP034817 for ; Fri, 22 Dec 2017 11:23:45 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id vBMBNjTb034816; Fri, 22 Dec 2017 11:23:45 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201712221123.vBMBNjTb034816@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Fri, 22 Dec 2017 11:23:45 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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: Fri, 22 Dec 2017 11:23:45 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/qconf | 2.3 | v2.4 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Fri Dec 22 12:52:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12E54E96BB6 for ; Fri, 22 Dec 2017 12:52:18 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9AFA75968 for ; Fri, 22 Dec 2017 12:52:17 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa05.server.lan (via HTTP); Fri, 22 Dec 2017 13:52:13 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: "blubee blubeeme" Cc: "FreeBSD Ports" Subject: Re: Canberra Content-Type: text/plain; charset=UTF-8 Date: Fri, 22 Dec 2017 13:52:13 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:Uz7chiMx1AgaIpeQLsWMnOiVDMvOk/NjQsfq5CU5g3G Hzg5xaC1CilrwTfHQ7hD12krbbb4I2h84gW2lm+L4bjSWIVtYw ovHc5ZDcmFLun/rNaCUrgZWuSmH2bUgLdET4ZFzeuyhtkZg9B9 hjV5aYoNW7JXnDhV1/CujQNX9NpM3m6Xr5q2Lt6Mr/0RhqDF8G hBa8gyDeYjNSoqLL4U5FYPljO7OtZg2kkpdXZh7Qg1aUpmgDJy mDKIJRn271QOjt60cJNrgNfxji8Y2u9jCL4F9r5nswU2gUxVpq wmmtLs= X-UI-Out-Filterresults: notjunk:1;V01:K0:gRnBuJ806hc=:vVktOFLwOtg/90iRJkw2MY XVZCgZUMKZKivBo6bM4dY2PwGCtYjeKSxY56b66sMcDuXp/kxwJHx6Qz5HbdkNRp5Wfj+E3b+ OQAHY50pRgASDrt9FRuWtiDikBWYmVwj8ScA0WIUlcd5ZYy1ztmjbw30FzpjS/w+7XjU5mhBH VpJrzi/ZmZb/14IXsWFRQDNWmdll6xmLKS6ExLqkqYKp3HYmgCxPfoRCix4m+RxwBxc71ayIw fIpEuK83xcP1lJArjhnrq+V1QsEMJqF8Nf3kZAGRspEEEK256/x4zYT8DcGUABwyjV2xA1s9S GoYk6zygTH8f8zrtkFZIaeF7Y77Mjb8xFd8ZBdh5Pv1/3xaB22btuGVlJxAmwXR54u3HgNAZs mUH/kRSSzfjkrdOcmwK6pIT4SBRUSNNlg3cbiZ4LYuR5JvK6T5dNTyn8xwu1As/z0oqgbmAk+ fJc3naGs8qgHNgw4VmRkJkVPeym33eBoqtGLR6aystcMoiLww5ueqnM0h7wO9vEqtampjyX/h uaK7Nu8zc4QZ0zUWvZ4RjpNETGtkxiZe7Popszj7pFa 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: Fri, 22 Dec 2017 12:52:18 -0000 > Blubee Blubeeme; > Who thought that was a good idea, now layer a few more audio layers and u have Linux[ism] to the max. > Well, I think that it's not really worth it to go untangle that mess. > It's okay if you're using a Gnome DE since it's all in there already but just to play a sound file you have to bring in all of this nonsense. > If you want to keep going down the Gnome hole, go ahead let me know when you get to the OSS specific issues, if any. > There's a lot more pressing issues that affect a larger surface area than a DE. > Best You're right, it's a rabbit hole. Whenever something starts to get untangled, it changes and becomes more tangled again. I made a personal Makefile for a light install of libcanberra that doesn't use gtk at all. It worked, but more ports now require gtk3 for graphics for some reason. libcanberra-gtk libraries and its package are now called specifically from the sourcecode. An elegant short term solution is to set make.conf to not install pulseaudio and gstreamer1 for audio/libcanberra-gtk3: audio_libcanberra-gtk3_UNSET=PULSEAUDIO GSTREAMER. This accomplishes the same outcome, without the extra Makefile, and tedious extra work. This made me wonder, that I can create a Makefile for distfile/sourcecode of gstreamer1 and audio/pulseaudio to extract the most used libraries, to avoid more compilation of those dependencies. The full port and the partial port may not necessarily conflict, because the extracted library should be similar enough to the one in the full install, but if it does, then CONFLICTS= only allows 1 of those ports. I can then file a bug report of this, if it works. Back to a drop in replacement: libcanberra uses audio/libvorbis which has its own API. libvorbis will do for .oga files. Wav files may need more work, or simply the .wav files will have to be filed as bugs to be converted into .oga files. An important thing to know about libcanberra is, where the program calls it, and where it calls OSS and libvorbis. Calls to gstreamer1 and pulseaudio, perhaps via their library files, should go to the OSS API. Other than that, API's are another language to me. Also, there has to be a way (perhaps like from make.conf) to make full substitutions of packages and libraries. As long as the program that calls it doesn't make drastic changes that affect it. >> Sid; >> Sooner or later, a drop in replacement for libcanberra needs to be made for all BSD's. It should use ogg files from audio/freedesktop-sound-theme. >> Canberra is meant only for sound (.oga, .wav), but graphical code is tied in heavily into it for XDG icons and graphics standards, so the problem is not just around gtk. From owner-freebsd-ports@freebsd.org Fri Dec 22 13:31:34 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6B64E9866A for ; Fri, 22 Dec 2017 13:31:34 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2BC87697A for ; Fri, 22 Dec 2017 13:31:34 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa03.server.lan (via HTTP); Fri, 22 Dec 2017 14:31:32 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: gurenchan@gmail.com, freebsd-ports@freebsd.org Subject: Re: OSS Audio Content-Type: text/plain; charset=UTF-8 Date: Fri, 22 Dec 2017 14:31:32 +0100 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:4+zAWePvvvYJIOGc0I08+spCXK9C+mfrEzTMGEOLFuJ r1SyLwxvSYovDYPgHvMLOJgrsWRyNC/PVRA9SSijATnfH70BgB /TDh+jkx+kle4xr3RZO66zHJhYHvtrvfz+7Hur3Gn8rqZt/3cU cnh41v0YR8uEcxkwITcXLvn9gEBmCMgjIRukBq39upnywsFhcw Yr+KhIgpxChFb1/fGdVJoR7/2rl/olTLX6Z9Gc/mdh+/ILmrIE ohRoOq3XXomX/az8d9pxXLn7rnNnAidjn5nWxTqAFLVa6RTzL0 yBAues= X-UI-Out-Filterresults: notjunk:1;V01:K0:KjoiyB5rgnM=:b7HaWU+zvZvHhYgC3BlQL8 zLrnEFOQEbkTsNPfVd+USesfr888sAC1/s1zb885fh9om6d8YSV39G8hegHxwgKXmQ6tvQpKI G0f5X6n6QUgkovTaDXqwYmVPd4fcbxphSypb+bc6Kp18ADqaFEdODjLFY96F+7MtocRENRogK TNxqKSJic2Xk2YX1oIEgfqiYYbhZ/5wmlzRUQzi3pB/zqaUrbofjE/Gv+5x5eYDPyyjshP+fI zauodEKA5g2IqkLFQD14sg7e1nuSCfkWwCgqOTiYvaUf2ELGHax7LTBZeGPE2hIwzVPbK6e/S dm0IT3pQsFrdETboKpAQELBBv92hWTGcc+JDsHD05SFjouzAShTN5b1vxvSrudjyGMyS3IoMN Y2rDmO/fchIUHhbja5hVcZFqYLYz3CsL4KZ40KDr4JCOOcq5/WUK35n8vwlrYIgRaK09+XBg1 +iRM9nh82ggAaNwhz3ExPXyN1I0ZYnTt9VfpLjhHTV8YznTb+4Jf1rT2m1gmra2AV4QK8FU0b TKAIW+RImfELsXouMryxTHtvwkKlTV3g90QjK0Lh6E/ 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: Fri, 22 Dec 2017 13:31:35 -0000 OSS soundcard.h for FreeBSD stable and current https://svn.freebsd.org/base/stable/11/sys/sys/ https://svn.freebsd.org/base/head/sys/sys/ blubee blubeeme; Mon Dec 11 17:03:10 UTC 2017 > I'm taking a look at soundcard.h in /usr/include/sys/soundcard.h in FreeBSD > vs the soundcard.h in the offical OSS 4.01 > https://sourceforge.net/p/opensound/git/ci/master/tree/include/soundcard.h > It seems like there's been a lot of changes between FreeBSD 3.8ish version > and the 4.0 version. > I was grepping around to see if any other files included this soundcard.h > header and if updating to the latest would break any other programs. From owner-freebsd-ports@freebsd.org Fri Dec 22 14:53:33 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83D6CE9E279; Fri, 22 Dec 2017 14:53:33 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A14179C09; Fri, 22 Dec 2017 14:53:33 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x235.google.com with SMTP id x67so18699757ioi.9; Fri, 22 Dec 2017 06:53:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=GOOCM5swvDbOP8iHv7f7DlPaiu5Ve300ePF/cpil5/g=; b=uwfRgtgelkbKie6piMYJGWnCRPX4wH/vA3cJJIONrF+0OMO38Bk2i/bszJmOgDjuZ0 Tm969A1AICdL3TUoZ0QhF4G7m+WRHur/0Ncp80QyD4z4ovYFwTCjudPg0iEU3Dcxgi/g IL47kgi+f5ENjFjH37fnnJHcsByCpEtjqsroaSlvMl8X98YYSjz+Z5zvsTYUmmbgTfx5 N/5znyv/H0aU2jHl8hlQrFLICaoICmWM9qTd2LLpqUGzURHu+Gn9MU+TKyh40HK/ubVU qcHIh9KOqqnFO/kfUJeU4WFsG4d4LfTDWNkHxe7lIl/8i+h3Wkc4WpM2XmQ/UJqs4r9f 1YXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=GOOCM5swvDbOP8iHv7f7DlPaiu5Ve300ePF/cpil5/g=; b=JTu/DA5Su8AW8Btu1LSFv6lBlkEYNsY2oRbHWCRI0ezuvuckJgXhWR4ZI1SLtIEjIn ylvYkpQTQaM8C9CVT1G+fCIvKRUNxFhY4LtDr4EbAoON4AxDnYrxoLI6GHIFFHgzj+74 VkVvR/FLqJWemiP67rTSK0KkrnpZ4veTqeC/SKvyMY/iRIB0izQOL4VwHlbEOT03eh0q 52GBzXCmCqdw3EN5lY2IdWuOx0nwKmFdQ0DPKFPW+6WxWXOo8q/eZEJ3u4Jfj/YGaJAo jhs/ktSXJzyQLIvcHpPZTyVuB3DopNlQgJszDGbkWeTOHyXg8qp09uZl+CxRuwNmnhZ4 NZkw== X-Gm-Message-State: AKGB3mJwH1yJOn4k36BwBSngPUaRK3+0iJ875nffvsQ0wudczroJHk9X cALlAektfV8XASoMFDM9fpXlPBYcxdDYBt2e2iooK0A7 X-Google-Smtp-Source: ACJfBotTdC6Vb5/+irNiNXf2QapNE2zOqBe0CMYeEyGUduX3QYjYGCu5wKxifiKhrJ5RPaEuJmnB5peuZTlCU3gikaU= X-Received: by 10.107.142.145 with SMTP id q139mr1101613iod.63.1513954412065; Fri, 22 Dec 2017 06:53:32 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.131.163 with HTTP; Fri, 22 Dec 2017 06:53:11 -0800 (PST) In-Reply-To: References: From: Ed Maste Date: Fri, 22 Dec 2017 09:53:11 -0500 X-Google-Sender-Auth: rbuvf9kX16IH2hqRay2xatMauSs Message-ID: Subject: Re: Ports and LLVM's lld linker To: FreeBSD Ports , freebsd-toolchain@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Fri, 22 Dec 2017 14:53:33 -0000 On 18 December 2017 at 22:10, Ed Maste wrote: > > With a couple of recent changes in src head (r326831 and r326897) lld > is now suitable for use as the base system /usr/bin/ld on amd64 and > i386. We're working through ports failures, starting with those > responsible for the largest number of skipped ports. > > The top four, on amd64: > > port # skipped > devel/libunwind 7994 > databases/postgresql*-client 230 These two are now addressed by setting LLD_UNSAFE=yes so that they'll still link with ld.bfd once ld.lld is installed as /usr/bin/ld. The issue with libunwind was already reported upstream (from someone trying to use ld.gold, which fails in the same way), and libunwind's developers will address it in a new version. The postgresql*-client issues need more investigation, but now will not prevent the migration to lld. > lang/fpc 76 This one's a little tricky, because it's a (Pascal) tool chain that doesn't support usual environment variables like LD to specify a linker explicitly. > lang/mono 22 I'll mark this one LLD_UNSAFE after a libtool dependency is sorted out (PR224514). After setting LLD_UNSAFE=yes for libunwind some previously-skipped ports attempt to build, and some of those now fail with lld. I'm working through that list and may have a dozen or so more that will become LLD_UNSAFE. From owner-freebsd-ports@freebsd.org Fri Dec 22 18:13:35 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D43B3E8110B for ; Fri, 22 Dec 2017 18:13:35 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BFD4E1B47 for ; Fri, 22 Dec 2017 18:13:35 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id BC308E81109; Fri, 22 Dec 2017 18:13:35 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BBD94E81108 for ; Fri, 22 Dec 2017 18:13:35 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 930871B46 for ; Fri, 22 Dec 2017 18:13:35 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id vBMIDOxF022304 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 22 Dec 2017 10:13:28 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me To: "ports@freebsd.org" From: Yuri Subject: [feature suggestion] Closed source binaries need to be labeled in ports, and explicitly allowed by users (suggesting the tag TRUST_CLOSED_SOURCE_BINARY) Message-ID: <8826f5e3-bd24-9bc6-e2d3-6cd47617560b@rawbw.com> Date: Fri, 22 Dec 2017 10:13:23 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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: Fri, 22 Dec 2017 18:13:35 -0000 We need to track closed source binaries better: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224526 Yuri From owner-freebsd-ports@freebsd.org Sat Dec 23 07:12:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDD35E9DBA7 for ; Sat, 23 Dec 2017 07:12:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DE1879979 for ; Sat, 23 Dec 2017 07:12:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x22c.google.com with SMTP id n9so12462988ual.13 for ; Fri, 22 Dec 2017 23:12:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=nTDO5YX+638aeiY2sJdzKM36CAhJ2xCXXhnOq3X191g=; b=tG/ziZJWOH7n32C/tD1SC3lhC4NbolV7Stm6xNdNtYyxXb9jwF3Y7JxOS9AigvYqXp IbBpiexE7y1UzM6E3SYmR1MR1eo2MGOjQUP5Wy4xyIPpdscawssmYWbFqeUtjU/uHLyP Q1GzEyrrJA0/Rst814j1DawZNE42uD5JXaSsvtP0+ks5V8Lsj91DCJ11rKXGt735gows GRWvagHbhEnR0lz7FvRUtJ5zdCOWd3KnVVLMpdaXwctDUXxOLKat/F4TLd7ZLl3tfkFs iNdIVlDSH3uzOa+zpWLeBTHEu2UG8H+F5XlaXkrpISCFWsjksVRQe52qeFN0FRb2yWRw QsgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=nTDO5YX+638aeiY2sJdzKM36CAhJ2xCXXhnOq3X191g=; b=l+J+/ElgscZt/XNac3PwctnJn3Kazh0vtzdD+WMRtX/PKPOcgQrq940vBxsX8+w2E1 zGW1e3muztxCaqNHhsUltqmCCa/6TbaGjfUNYiKnd7jhSePjWLQqqDgbo40v2geJaarD 7C/xTTvFsA2LwBvPyVq5QlK7MkEeyemuxMnvhZ+oQQ9UqA0oYmS9MqDVMpx+0ygnAmRg eWrmSxQFgRPayTn+JtGBE5SNt8r7vUuWDTjOJUonhf+sQyTYkYEjGF5XZgo+oNnnnH1A 6wfLueL/3Kgv8H/atIODIMF2fAP7z4JtXNvS7LOxGk6OiKd44W10/b4Vq7cmAXZR5G4u naxg== X-Gm-Message-State: AKGB3mKalbeiE7llCHPLjDMAHiYtKUBQUxQZV9RtLJ27rtqXV74Nh9Nk hfTOwbL/R5BSVWKYfg2h0pkDitr06rSVpO3AXIdSL3EJ X-Google-Smtp-Source: ACJfBos24CRYJt23Xkj0CFtA1t/rGRF0Dc1qVqVVozWXdUdO5Abbe8r0R/mwUsbGTFCMPM77wQU2lVQeSCvA93+zS4M= X-Received: by 10.159.51.75 with SMTP id a11mr18709190uac.147.1514013136281; Fri, 22 Dec 2017 23:12:16 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.147.156 with HTTP; Fri, 22 Dec 2017 23:12:15 -0800 (PST) In-Reply-To: References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> <5A3CA1B5.2090907@grosbein.net> From: Kevin Oberman Date: Fri, 22 Dec 2017 23:12:15 -0800 X-Google-Sender-Auth: moF8qMWRXK_N2aWkR9OZgOa71sM Message-ID: Subject: Re: Procmail got updated! To: Matthias Andree Cc: FreeBSD Ports ML , Eugene Grosbein Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Sat, 23 Dec 2017 07:12:18 -0000 On Fri, Dec 22, 2017 at 2:29 AM, Matthias Andree wrote: > Am 22.12.2017 um 07:09 schrieb Eugene Grosbein: > > 22.12.2017 9:50, Matthias Andree =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> Am 21.12.2017 um 10:16 schrieb Eugene Grosbein: > >> > >>> So, you demand we stop shipping any unmaintained software with our > Ports & Packages? > >>> Absence of CVEs means nothing and almost any non-trivial software has > bugs (axiom). > >> Eugene, these are attempts to distract from the argument, or to mount = to > >> fallacies. I do not intend to respond further to them or other of your > >> messages in this thread. > > That was real question, I like to know the answer. > > That generic question bears no relevance to the procmail case. OK. It looked like a reasonable question and a one-liner answer which seemed to say "I can't justify anything here" or "I don't want to bother". So maybe it could be clarified. First, I don't think Eugene meant "unmaintained by FreeBSD" but unmaintained upstream. Or maybe both. Can you clarify, Eugene? We have many ports that have no FreeBSD maintainer. We have fewer, but many that have no upstream maintainer. I know, as I use and have a critical need for a few. One that comes to mind is complex and almost certainly has at least one bug that could trigger a CVE if found. This is true with almost any complex code. So, why does Eugene's question have no relevance to the procmail case? Could you please explain? For the record, I have not used procmail for at least 7 years, perhaps longer. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-ports@freebsd.org Sat Dec 23 07:28:04 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF079E9E091 for ; Sat, 23 Dec 2017 07:28:04 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from disroot.org (bs-one.disroot.org [178.21.23.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9316579DD0 for ; Sat, 23 Dec 2017 07:28:04 +0000 (UTC) (envelope-from emilia@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id AD0D42A69C; Sat, 23 Dec 2017 08:27:55 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1514014075; bh=5c1psGo8KwmjTjdUktqheZCXS9RCguX3HKcDP0mTGH4=; h=Date:From:Subject:To:Cc:In-Reply-To:References; b=joKR7svMryMFZsqWPYvbvuv0eVvB/AyNh/qBpkiqJb+9y/a1Nx9EmBjSe+gC+4ukS u8p6He/dNo9UHD8JyE6WoBwYlyQ//Jt1p9XUtM9aoybwp3x3cy3OSAOntX/Hg0UYDV OWdDRmwkmNR/VaGFQjZVy0tzfe5ksodFjI4GVvv4= X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GqEwahLpmhEF; Sat, 23 Dec 2017 08:27:53 +0100 (CET) Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1514014073; bh=5c1psGo8KwmjTjdUktqheZCXS9RCguX3HKcDP0mTGH4=; h=Date:From:Subject:To:Cc:In-Reply-To:References; b=Z2uf9zQcQyhjeaiZGVWIm32HV+btqUH5Wly7Aci+8uhsjfuLYq5GzTzl0W2mHVn2P HAxdDL8dv4sLOWe1HQK+WXx4RGZey3PqC2xn0hNapEVc/lr+9VrdT00/yfUsWCkrRW TZOZWUyhr6ENIgDO1bQUrcgdLWxu4LnmJa8vT38c= Date: Sat, 23 Dec 2017 07:27:53 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: "emilia" Message-ID: <20a9d9c7d9047905218f8dd3ade305c7@disroot.org> Subject: Re: Procmail Vulnerabilities check To: "Kurt Jaeger" , "Chris H" Cc: freebsd-ports@freebsd.org In-Reply-To: <20171211183649.GB2827@home.opsec.eu> References: <20171211183649.GB2827@home.opsec.eu> <20171211111031.GA92072@gmail.com> <32da0142ef01d545aff61de3a3946d62@udns.ultimatedns.net> 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: Sat, 23 Dec 2017 07:28:04 -0000 December 11, 2017 7:39 PM, "Kurt Jaeger" wrote:=0A=0A> T= he argument is: The update process for base is more complex=0A> than for = packages, and we've come a long way to have a very=0A> nice pkg-system, i= n general. The mid-term plan is thus to package base, too.=0A=0AThe non-p= ackaged base is one of the primary reasons I switched from debian to Free= BSD :)=0A=0A=0Aregards,=0Aemilia From owner-freebsd-ports@freebsd.org Sat Dec 23 07:35:21 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD423E9E509 for ; Sat, 23 Dec 2017 07:35:21 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EC7C7A1CE for ; Sat, 23 Dec 2017 07:35:20 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBN7ZCKv029334 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 23 Dec 2017 08:35:13 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: rkoberman@gmail.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id vBN7Z8dX068353 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 23 Dec 2017 14:35:08 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Procmail got updated! To: Kevin Oberman , Matthias Andree References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> <5A3CA1B5.2090907@grosbein.net> Cc: FreeBSD Ports ML From: Eugene Grosbein Message-ID: <5A3E0727.4070800@grosbein.net> Date: Sat, 23 Dec 2017 14:35:03 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net 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: Sat, 23 Dec 2017 07:35:21 -0000 23.12.2017 14:12, Kevin Oberman wrote: > >>> So, you demand we stop shipping any unmaintained software with our Ports & Packages? > >>> Absence of CVEs means nothing and almost any non-trivial software has bugs (axiom). > >> Eugene, these are attempts to distract from the argument, or to mount to > >> fallacies. I do not intend to respond further to them or other of your > >> messages in this thread. > > That was real question, I like to know the answer. > That generic question bears no relevance to the procmail case. > OK. It looked like a reasonable question and a one-liner answer which seemed to say "I can't justify anything here" or "I don't want to bother". So maybe it could be clarified. > > First, I don't think Eugene meant "unmaintained by FreeBSD" but unmaintained upstream. Or maybe both. Can you clarify, Eugene? Unmaintained upstream, unmaintained in the Ports Collection. This was not about any part of FreeBSD base. From owner-freebsd-ports@freebsd.org Sat Dec 23 10:43:02 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2970EEA249E for ; Sat, 23 Dec 2017 10:43:02 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 803FC7F081 for ; Sat, 23 Dec 2017 10:43:01 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([92.227.100.135]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LjvV7-1f07CQ2OPh-00buJl; Sat, 23 Dec 2017 11:42:15 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id C7F2D23CEED; Sat, 23 Dec 2017 11:42:13 +0100 (CET) Subject: Re: Procmail got updated! To: Kevin Oberman Cc: FreeBSD Ports ML , Eugene Grosbein References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> <5A3CA1B5.2090907@grosbein.net> From: Matthias Andree Message-ID: <1f5623f9-0ed1-3fb7-d81a-efd2f08ae3c8@gmx.de> Date: Sat, 23 Dec 2017 11:42:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE X-Provags-ID: V03:K0:cpjhknmACuxO1IISTD8j9L3batLdemqNUKrt0PJdL7Em2+xEoUG Ip+MMm2zBGNCQQGbKdkctIj++406c6BXRP3EhAldAYnpex8EejUJn8uyeLvGBBoOXTXFYmm h1qdGaZYvY1hMdlMc9+ldFFynMm92N5rT+KpMaAyDGv7SHAp4RvW5zNdWgTJSBRhQWfSXp4 hrjvSdlQhYzofDhpa6DLw== X-UI-Out-Filterresults: notjunk:1;V01:K0:1Pu6Q51QCCA=:tdXZz0ZosvTvQsVHXD/83w S4dgtrSy6Pf3LiiehxX1Xhsv1Vw/bGOLIgLSUjSUv4TzZNGGQvCLZSDalVso+hCOqlrcGJyuo q/kjLjq00aap3V9UAF7LhnSQczKa5uHcgE+i6QAzbG4bJiMCnWNWz4Mw77wRj4vj7zkyALeFZ 7jTwYy4YIvrozEX6kkgYoKnyYaaoxCTg4PeyMlMU+9x/hcNPXj6ExxSZbqXeNHwPRhOAQ1sKa 0zUztbO9HUbP33XrJd8spfvS7Cs9Bf4FlRj5KrXO9G/7X0yWCY9qc1eeOrmfDo1B7aPgPWOfu gRrwt+nCSUsFeqwzPvwHEWtv4rHyf+NSK2Q6VExLzEBq8bQXJjm8Bq6egp2WIf1HLzk4D4CQn CJGOe9aZXiN0d2Cwb/6Kx9+0wXw/36XuIW1eJvTwSdXTnGl6/RF9kYJfb0dVxuRvNXAPUqK7k cuM97jq/1MZUo00Hlto+/2rIgy4hF1eS1gs1ArZLp6nHB3+XfM33aKMB5S78CaNQkgD7AQcLG lucUmebCxI/4i3Dba7wu+rxmRBhJTa/19eRah7E5g9zHoakMkgn/Ve5SmZDZ6itXhvWJRtmav FD+PVWrapuNlK/erkCp0gOh+ADuPw6fCqdHTyyKg32a/0NAz53jV6h0XoT7SdxUKMitbx6JBA bSZMMJID7/GFbbLQyz1doapViMj4yNwLWBUOTtQJsVaavjJ4ezKYRcL9ZkAp6MOM3jqS29EzC HzbBfizv2GVevSd+1uII3VoD5EWeMv4kmtwOo3vEV2qBPaKyEKNmrXPt+ZLFYQ6Us4mc4DxDw Po+F9YL1YvBI6jTwpsF9L+wEYkkk/YK2CADO6Tdq0WGvecl6W4= 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: Sat, 23 Dec 2017 10:43:02 -0000 Am 23.12.2017 um 08:12 schrieb Kevin Oberman: > > So, why does Eugene's question have no relevance to the procmail > case?=C2=A0 Could you please explain? Because I am not willing to discuss generics when we have a specific case of port at hand. The attempted generalization distracts from that, and I insinuate that distraction is the purpose. Everyone is free to start a new thread about general port maintenance and removal principles. From owner-freebsd-ports@freebsd.org Sat Dec 23 11:44:35 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6763DEA34BC for ; Sat, 23 Dec 2017 11:44:35 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 52D8B80844 for ; Sat, 23 Dec 2017 11:44:35 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4F13AEA34BB; Sat, 23 Dec 2017 11:44:35 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CAD9EA34BA for ; Sat, 23 Dec 2017 11:44:35 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2D79B80842 for ; Sat, 23 Dec 2017 11:44:35 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id vBNBiZOa077676 for ; Sat, 23 Dec 2017 11:44:35 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id vBNBiZup077674; Sat, 23 Dec 2017 11:44:35 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201712231144.vBNBiZup077674@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Sat, 23 Dec 2017 11:44:35 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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: Sat, 23 Dec 2017 11:44:35 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ textproc/sigil | 0.9.8 | 0.9.9 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Sat Dec 23 16:42:38 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27C59E86A28 for ; Sat, 23 Dec 2017 16:42:38 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.io-tx.com", Issuer "AlphaSSL CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE17D6A0C6 for ; Sat, 23 Dec 2017 16:42:37 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (authenticated bits=0) by io-tx.com (8.15.2/8.15.2) with ESMTPSA id vBNGgQRI061117 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 23 Dec 2017 10:42:27 -0600 (CST) (envelope-from ted@io-tx.com) Date: Sat, 23 Dec 2017 10:42:26 -0600 (CST) From: Ted Hatfield To: Matthias Andree cc: Kevin Oberman , Eugene Grosbein , FreeBSD Ports ML Subject: Re: Procmail got updated! In-Reply-To: <1f5623f9-0ed1-3fb7-d81a-efd2f08ae3c8@gmx.de> Message-ID: References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> <5A3CA1B5.2090907@grosbein.net> <1f5623f9-0ed1-3fb7-d81a-efd2f08ae3c8@gmx.de> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 X-Virus-Scanned: clamav-milter 0.99.2 at io-tx.com X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=5.0 on io-tx.com tests=ALL_TRUSTED, AWL, T_RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 user=root X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on io-tx.com Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Sat, 23 Dec 2017 16:42:38 -0000 On Sat, 23 Dec 2017, Matthias Andree wrote: > Am 23.12.2017 um 08:12 schrieb Kevin Oberman: >> >> So, why does Eugene's question have no relevance to the procmail >> case?  Could you please explain? > > Because I am not willing to discuss generics when we have a specific > case of port at hand. > The attempted generalization distracts from that, and I insinuate that > distraction is the purpose. > Everyone is free to start a new thread about general port maintenance > and removal principles. > I think the best reason to keep procmail available in ports is that there are still quite a number of people still using it. In fact opensource.com has an article dated 11/01/2017 titled: SpamAssassin, MIMEDefang, and Procmail: Best Trio of 2017 https://opensource.com/article/17/11/spamassassin-mimedefang-and-procmail Not necessarily an argument for code safety but a good argument that it's still being used by quite a number of people. I think that as long as someone is willing to patch the software when vulnerabilities come up we should keep the port available. Ted Hatfield From owner-freebsd-ports@freebsd.org Sat Dec 23 16:50:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46028E87594 for ; Sat, 23 Dec 2017 16:50:25 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 055F86ADAD for ; Sat, 23 Dec 2017 16:50:23 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.204.135.157] (helo=[10.157.219.157]) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1eSn02-0002Nv-Qu for freebsd-ports@freebsd.org; Sat, 23 Dec 2017 17:50:14 +0100 From: Matthias Apitz To: Subject: Re: Procmail got updated! Date: Sat, 23 Dec 2017 17:50:13 +0100 User-Agent: Dekko/0.6.20; Qt/5.4.1; ubuntumirclient; Linux; MIME-Version: 1.0 Message-ID: <64a0ce8f-8f1f-45bf-8024-95b7324e2d14@unixarea.de> In-Reply-To: References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> <5A3CA1B5.2090907@grosbein.net> <1f5623f9-0ed1-3fb7-d81a-efd2f08ae3c8@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.135.157 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: Sat, 23 Dec 2017 16:50:25 -0000 On Saturday, 23 December 2017 17:42:26 CET, Ted Hatfield =20 wrote: >=20 > ... > > I think that as long as someone is willing to patch the software when=20 > vulnerabilities come up we should keep the port available. > > Ted Hatfield +1 matthias --=20 Sent from my Ubuntu phone http://www.unixarea.de/ From owner-freebsd-ports@freebsd.org Sat Dec 23 22:11:53 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64779EA51C2 for ; Sat, 23 Dec 2017 22:11:53 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4CDE97841E for ; Sat, 23 Dec 2017 22:11:53 +0000 (UTC) (envelope-from yasu@utahime.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4C098EA51C1; Sat, 23 Dec 2017 22:11:53 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BBC1EA51C0 for ; Sat, 23 Dec 2017 22:11:53 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 20EC37841B for ; Sat, 23 Dec 2017 22:11:52 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 025B78E7C; Sun, 24 Dec 2017 07:11:50 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 3935632F47; Sun, 24 Dec 2017 07:11:36 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id F2A2032F46; Sun, 24 Dec 2017 07:11:35 +0900 (JST) Date: Sun, 24 Dec 2017 07:11:29 +0900 (JST) Message-Id: <20171224.071129.191311078132793435.yasu@utahime.org> To: ports@FreeBSD.org Subject: Re: Are these Emacs ports still useful? From: Yasuhiro KIMURA In-Reply-To: <86d135nne8.fsf@phe.ftfl.ca> References: <86d135nne8.fsf@phe.ftfl.ca> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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: Sat, 23 Dec 2017 22:11:53 -0000 From: Joseph Mingrone Subject: Are these Emacs ports still useful? Date: Sat, 23 Dec 2017 17:29:51 -0400 > A quick scan suggests that these port may have passed their usefulness. > Could you speak up if they are still useful or if you feel they should > be removed? (snip) > - japanese/lookup (source tarball from 2007) At least I still use it. And there is beta version of Lookup 2.0 in following URL. But it isn't fully compatible with 1.4.1. So I cannot dicide whether to update to 2.0. http://lookup2.github.io/ Regards. --- Yasuhiro KIMURA From owner-freebsd-ports@freebsd.org Sat Dec 23 22:35:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08580EA6AFA for ; Sat, 23 Dec 2017 22:35:59 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D6B3479052 for ; Sat, 23 Dec 2017 22:35:58 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mailman.ysv.freebsd.org (Postfix) id D5FEBEA6AF9; Sat, 23 Dec 2017 22:35:58 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5A52EA6AF8 for ; Sat, 23 Dec 2017 22:35:58 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9218979050 for ; Sat, 23 Dec 2017 22:35:58 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mail-qt0-x232.google.com with SMTP id w10so39989065qtb.10 for ; Sat, 23 Dec 2017 14:35:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ftfl.ca; s=google; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=13LCtyPZpwcFGTp9p/tQs9GElBTsYioTOf6lZDKByis=; b=A/GxLFWd5CqLPmOE7MjOTFssrlpa+kc3FNB+NHw8RTyuc4NeX9fvViVf1HKfb+Q2hZ yP+0QkY62G+6pD3bN2Uzu5mbSII+DryPZlQG29CUNzH784P/w4ZcKOYX7nbiGiyWS53q GoOQzDcTVk8Ig/yfWPVpowbSJeiqWFgYbEt1c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=13LCtyPZpwcFGTp9p/tQs9GElBTsYioTOf6lZDKByis=; b=NvPDmFBsIZBSFIQwMhp9VDyc5ibB1k7ZgPvZ6XmEga/WfmuRnroJaT2twYw4FkMepe Y9PNlrgiytgbDtvTJaNbtAFMYNZ/LjwwjX9uyLRLr6Gq6o2apCjYqlnLp0wl0OXqndL5 8Zz1cm6DXeneTtmBJ3xOZz38e9oKvIh7pTQI8XmcKEo09oq351MxzmgFxYUDhI7avDCr hL4W4KHYpgfxDvJ130qap8agWhsyxS2qo79/vd/SPkwkZhyfKxo3cqoAaKbV6fqmpGtS eVG2mpmXhu5y3uDBpm08d6hJpD1nahfcXLklNjgEwxgXGNbZfYKjc8VU4NJC/Z4adBC0 u09A== X-Gm-Message-State: AKGB3mIpVp9G2pVu7Yf7+lDz+vgbRPbl1bhgfz8vdo2NO7zs7ax8uACS JxwmuWI3q4/EGmjaJOmXQWLxeJL1Cso= X-Google-Smtp-Source: ACJfBot0l9Me93xYFc0QCr+k++iubNd/kWGZsAv16GiaGBlt71ov0LacbeH5RXXYgsRqS1WjzwWsaw== X-Received: by 10.237.62.4 with SMTP id l4mr26033800qtf.331.1514068557585; Sat, 23 Dec 2017 14:35:57 -0800 (PST) Received: from phe.ftfl.ca.ftfl.ca (hlfxns017vw-142-134-23-107.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.134.23.107]) by smtp.gmail.com with ESMTPSA id z17sm15188482qti.59.2017.12.23.14.35.56 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 23 Dec 2017 14:35:56 -0800 (PST) From: Joseph Mingrone To: Yasuhiro KIMURA Cc: ports@FreeBSD.org Subject: Re: Are these Emacs ports still useful? References: <86d135nne8.fsf@phe.ftfl.ca> <20171224.071129.191311078132793435.yasu@utahime.org> Date: Sat, 23 Dec 2017 18:35:55 -0400 In-Reply-To: <20171224.071129.191311078132793435.yasu@utahime.org> (Yasuhiro KIMURA's message of "Sun, 24 Dec 2017 07:11:29 +0900 (JST)") Message-ID: <86o9mpm5ro.fsf@phe.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" 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: Sat, 23 Dec 2017 22:35:59 -0000 --=-=-= Content-Type: text/plain Yasuhiro KIMURA writes: > From: Joseph Mingrone > Subject: Are these Emacs ports still useful? > Date: Sat, 23 Dec 2017 17:29:51 -0400 >> A quick scan suggests that these port may have passed their usefulness. >> Could you speak up if they are still useful or if you feel they should >> be removed? > (snip) >> - japanese/lookup (source tarball from 2007) > At least I still use it. And there is beta version of Lookup 2.0 in > following URL. But it isn't fully compatible with 1.4.1. So I cannot > dicide whether to update to 2.0. > http://lookup2.github.io/ Thanks for your feedback. japanese/lookup should not be removed then. Joseph --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEVbCTpybDiFVxIrrVNqQMg7DW754FAlo+2ktfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUACgkQNqQMg7DW 7567zw/+PVAuXXzf9pSNp0rhoKgbVlOon71zD5LHL3oeMo7OwuANpSkEbxV880ST TsStTMYNEoSUvasTaKOi/d+8PrPqCuBhcMWiKep4C6YcowOElbO4drUu7nnMZ2v4 m46d1QNii1+kjpdg8lysHhkHdEzML/Hn2Es8g9qtxmMbS3CmZqImHtCKGq35nMxz KWOZkRrof3y3Ry5xLu9HaqqoAiJXXaL6bZHajjVNPi/qJwtRGW4NfoCaLs3Z8cEJ xOZ4t/NkvIhHjp8TbEifIHg28OwAfHd8btaYRbi2wQKbRPcuI0KjckCT015LYZ6c vckhdMjJwvEBn5twsKXqF3LA3ov9HZ43c5OTKU6bzl8VN3pQx7uiSknoePP1p3U1 xzecjB6Qog5+MbCELfu+eUNyMRdMXX+vyV5RAJBE1ooPDf1+QyTYWmD+JifSx1AS t5kaEq/wNTREV2LUBOrGancmU5MqB0HgcF+niCRnob7FpKpfIskP8ZJzTcQ6bu/z bzoh1WXHCeDphsJD6MQGIrqqoJS7v5LTziLpkhmQhOeAeZn+NrirBIG7zSgG1LAp 44gr/Aw/TTg9Os4IKANJJQv8NM7rFAfFteurHy9hVgT0PDq5LfVe/4E1bom2hD6Q 6OLfNW3TyKQE6bgfneW4gBUqyGWBH5B+UbZQ9Au+m6ipMnfrBQM= =vkjH -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Sat Dec 23 23:13:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1B0DEA9617 for ; Sat, 23 Dec 2017 23:13:17 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D31BA7AFCB for ; Sat, 23 Dec 2017 23:13:17 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mailman.ysv.freebsd.org (Postfix) id D258CEA9616; Sat, 23 Dec 2017 23:13:17 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1ECFEA9615 for ; Sat, 23 Dec 2017 23:13:17 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com [209.85.220.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 992957AFCA for ; Sat, 23 Dec 2017 23:13:16 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mail-qk0-f182.google.com with SMTP id u184so38614133qkd.6 for ; Sat, 23 Dec 2017 15:13:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:user-agent :mime-version; bh=5QB11BKUUR2AL5O6Sp71SuvS+bgvH9sN1zI7IC4t75g=; b=gpMSpHUqnlGh/f/PZzIJdakfwsKErs6qcMHrZAiZsvWon9VVkdpLoVwOJwbahak0a9 7qpvhr7tOPAVi1VPBU1MF3c1t88mp6k7pcUdNPO17PgpJl4Ho2608UPjgPcIsbrws5x4 UoOCWIgJVrVBCt9RHB2ABW+adH13Gxvw5hSRTXd9nRX/b6CxM6bB0UFrvK8ZCd4pwxBI H7iZve+TuExBE6xZpzo1suPoQyS41AMNPCyH4Kr/pgGo8TF2t+TTnExRgOsEMfRGF5oK h5zVHwEPdQmypEk/0C+D7TMj05apgKkWpbyEdaP13rEI2Z98OOuvZpYad4so2IeMdF+z EoAg== X-Gm-Message-State: AKGB3mLhOS8QT3QrlXrvZE5RRAVkLvG0K66KK378RodO+xJ54Lwh2979 vIZ+3xW35BuCPOMYzVTPyBsv31B7cXA= X-Google-Smtp-Source: ACJfBou4V2h9IL18TvfNHuj43S19yEycNB8okt0p+6aeyBxOs/UfDkONCAddTLCOZeHLxKtKs1dN6g== X-Received: by 10.55.101.198 with SMTP id z189mr23583016qkb.46.1514070790043; Sat, 23 Dec 2017 15:13:10 -0800 (PST) Received: from phe.ftfl.ca.ftfl.ca (hlfxns017vw-142-134-23-107.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.134.23.107]) by smtp.gmail.com with ESMTPSA id g200sm16206825qke.55.2017.12.23.15.13.09 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 23 Dec 2017 15:13:09 -0800 (PST) From: Joseph Mingrone To: ports@FreeBSD.org Subject: Are these Emacs ports still useful? Date: Sat, 23 Dec 2017 19:13:08 -0400 Message-ID: <868tdtm41n.fsf@phe.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" 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: Sat, 23 Dec 2017 23:13:18 -0000 --=-=-= Content-Type: text/plain [resending (with updates) because original message did not make it to the list] Hello all, A quick scan suggests that these port may have passed their usefulness. Could you speak up if they are still useful or if you feel they should be removed? Regards, Joseph - sysutils/puppet-mode.el (pulling from source over 5 years old) - japanese/egg-canna/Makefile (does not build with emacs versions >= 23) - deskutils/etask (non-mirrored tarball dead since 2007) - editors/apel (2010 source) - editors/flim (2007 source) - editors/semi (2003 source) - editors/tree-widget (part of emacs since 2007) - graphics/xface.el (distilator reports 500 for all sources) - japanese/lookup (source tarball from 2007) (update: feedback received; still useful) - japanese/migemo-emacs23 - japanese/yc.el (source from 2010, does not build w/ emacs-devel) - mail/xcite (no real updates since 2010, still useful?) (update: feedback received; still useful) - textproc/dictem (last release over five years ago) - textproc/doc-mode.el (last release from 2006) - textproc/emacs-wiki (last release from 2006) - textproc/htmlize.el (500 from MASTER_SITES; fetchable from distcache) - textproc/ibus-el (no updates for over 5 years) - textproc/muse (last release from 2010) - textproc/xml-lite.el (merged with sgml-mode.el in 2007) - textproc/xml-parse.el (described as deprecated on Emacs wiki; release from 2001) These ports have not been updated in some time. Should they be updated or removed? - editors/psgml (use psgml-1.3.4.tar from http://elpa.gnu.org/packages/psgml.html ?) - editors/slime (five new releases since last 2015 port update) - japanese/ddskk (using nearly 5-year-old release) - mail/waderlust (only fetchable by distcache; source from 2005?; combine with mail/wanderlust-devel) - mail/x-face-e21 (not fetchable) (update: www.jpl.org is back up) - math/proofgeneral (version over 5 years old w/ releases since; does not building with Emacs 27 without X) - misc/elscreen (release from 2007) - print/hyperlatex (release from 2006) - print/yatex (version almost 5 years old, newer release available) - security/starttls (superceded by https://github.com/emacs-mirror/emacs/blob/master/lisp/net/starttls.el ?) - textproc/dictionary (port version from 2011 or earlier, 2013 version available) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEVbCTpybDiFVxIrrVNqQMg7DW754FAlo+4wRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUACgkQNqQMg7DW 755CCBAAjxPZrHOHJIg+OgLCvsArVUlEBMREzW8htGQVR1N4mr7F527EFi6RuWvx 70ldXzm+AtwN/w947BTVfx6mTmF80r9SSAk7YBiZHVJDqQbYLXU89brHzT5AARx9 k19cVfeH4e5mbYpOgn3KJDtJAaq1LhI/NSfeT5l6OlZIsu52n0GxXCntQbhkMtx4 lVrI++AwbX1neatpHaXHrKTQZJ0bIuMFoYCzihZ679H/UbxniaNZ3O133bhfmUIN NC/dVUO3cCBdEoDod6rE9KS7YxWBStFwlWL8H8+tJsLs3JctpxCCUlOwiIKdqRoZ 0QrqueMDKe4TAVu+sU39Al9yc1RMgNIXPfBGE11tQwbOaHF9H6NsvTt49AisU6aF B1y3svsFBcgb6PVx+/9nJE6c4lCxiV0tJgYVtfKnyNt8d3dbbtmQXNrEvBGN6JuZ sqrIurGKOl1fiSS3rbYerTgB4QOfXHUKzPa5J5YCChEWpnxyijksOdRgzQILf8fC MPiNxoUwiGIA1p8O6j7UT1IZ06ebkeHYe9ZY6JOW5pRAwVnVav80YsxyORLkE1E8 rJaDpwsDbf0NsRgjjQDnqbwJdZcBYb3mJuGs476LqXoHYZWLk8Jl51YUnO5Lkxzc oLWrWXlhLcJj5tafqCBCmO+qKLiddroexHMOkeegMUP472jqmWM= =+QtS -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Sat Dec 23 23:14:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6427EA9731 for ; Sat, 23 Dec 2017 23:14:14 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B33DC7B0BD for ; Sat, 23 Dec 2017 23:14:14 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mailman.ysv.freebsd.org (Postfix) id B29D0EA9730; Sat, 23 Dec 2017 23:14:14 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2473EA972F for ; Sat, 23 Dec 2017 23:14:14 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com [209.85.220.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 771BB7B0BC for ; Sat, 23 Dec 2017 23:14:14 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mail-qk0-f174.google.com with SMTP id q14so25855995qke.7 for ; Sat, 23 Dec 2017 15:14:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=vA8TjG5wi1bSX0bG4FMppPVPkJSM8r63d2pL8WFRqD0=; b=ceYaz+W18Cl/LJ9RCGkObcjXIPnVFoV71FsPdZh5bgEC9RzJC0YbTV4XZ9F8JywH1M MuCuCL59ihwTOplm6x9DTibMfD24iVXtp+h3A/F+dMaDP7lO5jM07U2WurVO10vhkR+5 GX/rrr7W/8/0TqBkFkC6TOdOEumzTm4IEJtGqAszVTeTxhqGQYJPmhZFtWAUVUUh0vDN yJdd9DgBqSIXtHYOiky9ASGhxwDLya0bvNaHnpD6WlddrCs1n2lxGYFT3vqICrELNAT5 SEWg1qff49qX/hngyC4IjuWKvCyMhcAIYpgWC4QpYmyyn/CzRP+NBy06f+mmQBpRaPA3 2Uig== X-Gm-Message-State: AKGB3mJxbVOg/Y0qfZD80trFWHqo5TidDnEfSX1ylXzSLbgFgz4/7dff nlk3iThfTgbqKhOP5g/ZRdU5xU3gGQk= X-Google-Smtp-Source: ACJfBouksX1B7Gt7qmcd63UQMsUUnvHyfMKf1Zuq6HeC0o/UkgzU8Mhd8+Us4GL+DNoixM+xWkHXLg== X-Received: by 10.55.176.66 with SMTP id z63mr19487779qke.149.1514070853018; Sat, 23 Dec 2017 15:14:13 -0800 (PST) Received: from phe.ftfl.ca.ftfl.ca (hlfxns017vw-142-134-23-107.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.134.23.107]) by smtp.gmail.com with ESMTPSA id l80sm1492908qki.96.2017.12.23.15.14.12 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 23 Dec 2017 15:14:12 -0800 (PST) From: Joseph Mingrone To: ports@FreeBSD.org Subject: Re: Are these Emacs ports still useful? References: <86d135nne8.fsf@phe.ftfl.ca> <20171224.065553.149647974919185417.yasu@utahime.org> <861sjlnkmu.fsf@phe.ftfl.ca> Date: Sat, 23 Dec 2017 19:14:11 -0400 In-Reply-To: <861sjlnkmu.fsf@phe.ftfl.ca> (Joseph Mingrone's message of "Sat, 23 Dec 2017 18:29:29 -0400") Message-ID: <864lohm3zw.fsf@phe.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" 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: Sat, 23 Dec 2017 23:14:14 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable [resending because original message did not make it to the list] Joseph Mingrone writes: > Yasuhiro KIMURA writes: >> From: Joseph Mingrone >> Subject: Are these Emacs ports still useful? >> Date: Sat, 23 Dec 2017 17:29:51 -0400 >>> A quick scan suggests that these port may have passed their usefulness. >>> Could you speak up if they are still useful or if you feel they should >>> be removed? >> (snip)=20 >>> - editors/apel (2010 source) >>> - editors/flim (2007 source) >>> - editors/semi (2003 source) >> They are required by www/emacs-w3m. >> Regards. > They are dependencies for www/emacs-w3m, but are they really required? > Upsreams [1,2] say apel and friends are only required with quite old > versions of Emacs that were released around 2001. > Regards, > Joseph > [1] The original emacs-w3m source, http://emacs-w3m.namazu.org/, says > with Emacs 21.1 (released in 2001) "No additional packages are > required." Other sources, such as [2] have made fixes to the last > release from this source. > [2] The melpa source, > https://github.com/emacsorphanage/w3m/ has no other elisp dependencies. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEVbCTpybDiFVxIrrVNqQMg7DW754FAlo+40NfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUACgkQNqQMg7DW 755yBw/9Ho7AM/XQCoo6d7M9htkgNsoOVk6u0XvmDtD+gkb4jzaTXdlRZfsaTXO/ Rmsirs+E8IEMiK6E/7hM9aHoEAERrav3oCs5LT3YgdTNswadU7N9aQLtLG1eaSkC 3FMJ5gOMiSP8cSOuGcw11tjvmpM5gCpAujs/vosOAFeX9IUhX5pfXwhL0sJKyknU fBr+cp64AuGyQuCk8iuwW9ICnLbQ65cguksxO8u7Fz0BDBUnio3G8pLRD3hsCYHQ QCE09ZM583UqWMZiP/OtYc16S4cj5xbSFRbzK6eof7rLOPu1EwF3z3QevmlKJVGl kLmadfVgi5Ccl+k40KIYDihR80hGR85TLo9fLkxW4DUBcNo707MqtNuKc9fP7K2o 6UwrEuAJ3E0gpGno+fgWC7lGzaVpZKEN7RhVRYcxfwGUvI3SqZQN9Zy8tVmzwZl7 E4H+24oZ6p5vH8CPtUq9hNI1c8DFMN7x2/YNpV+jKypJQV0T21A1hycIL66qNgrv H15ZMls4ZC+2OOzRz4NSbV8QooDXOVvBveydaH4hCG82PxPOulo1BHNczM4CZo3O swAFoplksrgZs6eBg6hu3i69mJCJ1bkPcuWP8Y18um3UvC++GaWX96SYIV5CN97Z B+E/TdCR2Wy6/3bBJda1OMcB7vje8zfJuI8HP3Feo4r37QjBMOU= =VI2u -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Sat Dec 23 23:15:31 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DC9FEA9839 for ; Sat, 23 Dec 2017 23:15:31 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3D5B37B1A3 for ; Sat, 23 Dec 2017 23:15:31 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 3CBB4EA9838; Sat, 23 Dec 2017 23:15:31 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C4A1EA9837 for ; Sat, 23 Dec 2017 23:15:31 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com [209.85.220.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 017227B1A2 for ; Sat, 23 Dec 2017 23:15:30 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mail-qk0-f178.google.com with SMTP id a8so1204043qkb.8 for ; Sat, 23 Dec 2017 15:15:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=nQz+AkmEbcBOyTyFbUgbDUwIf15evL+DwsQ5sJN9ioI=; b=HQKa4ZCM0sakrMVskujXX7CXOw3xMm+9tAPFmKhXFtJnBhRCIfvPdhzNay1Q7Y/ZQT L1VoSypYr3/+f96icwc+4630SfcJwVuumxXlctQGALRqZz4pmH2WAW7WKZGkDLnURtpq WETCB8bmnL6UbeTORNTFBEwgsMUc7KuH0NzJti8W4m4lSpi9Cq3HIqUi0e28Q2BIV/MY /RqJdkCFCoP1B18AzWIBaJgzC8/FHI9u1+Wriezcd/G42fQ5SpxG2JsAkt02qP3mIjOG xT+b7QvC8i6pctgcoG3kpq7TDg8VEQo3znTQhyUSkqTbfmzP2rBRicy4DUQOTeF8t155 t9Zg== X-Gm-Message-State: AKGB3mJW0qs7HDEb5JL+pGtDJdq0xkzZeb4NkgZIdTnqZfBbnmrHoHoh hL5VdBodYZWvrMV8Y2+ulSnch+o3aB8= X-Google-Smtp-Source: ACJfBovhuEHHhKl6zX8SGZxDwuc8s5C0d2Sjw3fL3GdD4CQQ5OFdOlfZoxmy6TJxECB0/oucB+ezcw== X-Received: by 10.55.146.65 with SMTP id u62mr24918990qkd.358.1514070929672; Sat, 23 Dec 2017 15:15:29 -0800 (PST) Received: from phe.ftfl.ca.ftfl.ca (hlfxns017vw-142-134-23-107.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.134.23.107]) by smtp.gmail.com with ESMTPSA id u43sm16377598qtj.54.2017.12.23.15.15.28 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 23 Dec 2017 15:15:29 -0800 (PST) From: Joseph Mingrone To: ports@FreeBSD.org Subject: Re: Are these Emacs ports still useful? References: <86d135nne8.fsf@phe.ftfl.ca> <86fu81m538.fsf@phe.ftfl.ca> Date: Sat, 23 Dec 2017 19:15:28 -0400 In-Reply-To: <86fu81m538.fsf@phe.ftfl.ca> (Joseph Mingrone's message of "Sat, 23 Dec 2017 18:50:35 -0400") Message-ID: <86zi69kpdb.fsf@phe.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" 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: Sat, 23 Dec 2017 23:15:31 -0000 --=-=-= Content-Type: text/plain [resending because original did not make it to the list] Joseph Mingrone writes: > Hajimu UMEMOTO writes: >> Hi, >>>>>>> On Sat, 23 Dec 2017 17:29:51 -0400 >>>>>>> Joseph Mingrone said: >> jrm> - mail/xcite (no real updates since 2010, still useful?) >> I'm using it. It is very useful at least for me. >> I don't think no update means no usefulness. :-( > Agreed. No updates does not imply it should be removed, but > superficially it can sometimes suggest stale > code. I will unflag mail/xcite for removal. > Thanks, > Joseph --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEVbCTpybDiFVxIrrVNqQMg7DW754FAlo+45BfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUACgkQNqQMg7DW 757/TxAApCWCZljxOIk+30iVs6I/c9uYUf58lneVzlLDmp52zR8hMH4CBel+Vmjc r3DJ69Xpc7hSE6rJLuNHwn1MGcFsXarVxelWe1v2PHQoTFicOmV4Wcr3SMqjid6l 2cjrmKIAZHBVxWCc3oOxHdQhqeRSGMuj5j394Ow7jzr0dXqroXqcivnzUYDxw0xb bEmukxNj2uud3CxGnbmOX8M748JgXNbFJLDoZ5CXLo0as9Zz5CN/wp1lyzGAeSHE 7Sug8FB036mHhJC0tGBvZ+/dcQiWvA2SUS9CqQd7JmK14Uqgv8xl+9TvyxaL2lK3 aI6eWJ/Z9IrPSz8RmumK4Z5708Ex89cB4TLxmtk8eVRqJI5VFczESSMD3xU548XF WOFJH3jvsc46ckputv1Txq+X1QvRMr58ql+FNzCP/5XFSgN1kHlG+6p9sC98gILL 5Olc4jYDsWDLw+8Pg2U6ylKFrahgzMKkGypV2NeiyIdZhalJeehu43OWV1H62PS3 llld0lvHF/qTExraY7tDtQ+BpPEK4X3fjwsoqBr9ZaBe11RzRRhfUI6MAzAFnZPn YlIntWjlzyy0IjvnaHNYA6zxcSshBuY0zJITNpg/tP8WzDaipRefziNYMD2tuw0v wue/W1+WkEIajyGPLkaViD8JGRxjQ4/5qEZ4uGw65u4IO+d4kKc= =c6Br -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Sat Dec 23 21:56:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57C56EA410C for ; Sat, 23 Dec 2017 21:56:28 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3DD2D77716 for ; Sat, 23 Dec 2017 21:56:28 +0000 (UTC) (envelope-from yasu@utahime.org) Received: by mailman.ysv.freebsd.org (Postfix) id 37DF2EA410B; Sat, 23 Dec 2017 21:56:28 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3789BEA410A for ; Sat, 23 Dec 2017 21:56:28 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 0510C77712; Sat, 23 Dec 2017 21:56:27 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 503798E77; Sun, 24 Dec 2017 06:56:19 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id F395A32F1A; Sun, 24 Dec 2017 06:56:18 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id B306D32F19; Sun, 24 Dec 2017 06:56:18 +0900 (JST) Date: Sun, 24 Dec 2017 06:55:53 +0900 (JST) Message-Id: <20171224.065553.149647974919185417.yasu@utahime.org> To: jrm@FreeBSD.org Cc: ports@FreeBSD.org, ume@FreeBSD.org, dryice@dryice.name, dryice@FreeBSD.org, nobutaka@FreeBSD.org, joe@thrallingpenguin.com, kuriyama@FreeBSD.org, tz@FreeBSD.org, hrs@FreeBSD.org Subject: Re: Are these Emacs ports still useful? From: Yasuhiro KIMURA In-Reply-To: <86d135nne8.fsf@phe.ftfl.ca> References: <86d135nne8.fsf@phe.ftfl.ca> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Mailman-Approved-At: Sat, 23 Dec 2017 23:26:07 +0000 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: Sat, 23 Dec 2017 21:56:28 -0000 From: Joseph Mingrone Subject: Are these Emacs ports still useful? Date: Sat, 23 Dec 2017 17:29:51 -0400 > A quick scan suggests that these port may have passed their usefulness. > Could you speak up if they are still useful or if you feel they should > be removed? (snip) > - editors/apel (2010 source) > - editors/flim (2007 source) > - editors/semi (2003 source) They are required by www/emacs-w3m. Regards. --- Yasuhiro KIMURA From owner-freebsd-ports@freebsd.org Sat Dec 23 22:50:01 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90EF3EA79B2 for ; Sat, 23 Dec 2017 22:50:01 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6B01F799FB for ; Sat, 23 Dec 2017 22:50:01 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5E55BEA79B1; Sat, 23 Dec 2017 22:50:01 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C383EA79B0 for ; Sat, 23 Dec 2017 22:50:01 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from mail.mahoroba.org (ent.mahoroba.org [IPv6:2001:2f0:104:8010::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "asuka.mahoroba.org", Issuer "ca.mahoroba.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 02281799FA; Sat, 23 Dec 2017 22:50:00 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from vsuiko.mahoroba.org (vsuiko.mahoroba.org [IPv6:2001:2f0:104:8010:a00:27ff:feb0:c2e]) (user=ume mech=DIGEST-MD5 bits=0) by mail.mahoroba.org (8.15.2/8.15.2) with ESMTPSA/inet6 id vBNMnsrK035107 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Dec 2017 07:49:55 +0900 (JST) (envelope-from ume@mahoroba.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mahoroba.org; s=20081103; t=1514069395; bh=Vlnkyr55EgiF6I2TfPRlm2zLXQ7YQxMi9u7naN+p3W4=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=C8zMsZdIPqWszRzExtmjeClAHD1piXaBDy3pdbYHnODYsiKWPKLHftsIRPkuTtJUl /o/Dp+200b+gz8s14CAslVEb2Ht+FFoibsl1eFaQar1VHOZjtf5a1Ne5c0JcN8X9IY BTm6iuLZkNcsh2zQdQfrbg0qE8B4gyaYHEhnYAa8= Date: Sun, 24 Dec 2017 07:49:53 +0900 Message-ID: From: Hajimu UMEMOTO To: Joseph Mingrone Cc: ports@FreeBSD.org, ume@FreeBSD.org, dryice@dryice.name, dryice@FreeBSD.org, nobutaka@FreeBSD.org, joe@thrallingpenguin.com, yasu@utahime.org, kuriyama@FreeBSD.org, tz@FreeBSD.org, hrs@FreeBSD.org Subject: Re: Are these Emacs ports still useful? In-Reply-To: <86d135nne8.fsf@phe.ftfl.ca> References: <86d135nne8.fsf@phe.ftfl.ca> User-Agent: xcite1.60> Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO) X-Operating-System: FreeBSD 11.1-STABLE X-PGP-Key: http://www.mahoroba.org/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.mahoroba.org [IPv6:2001:2f0:104:8010:0:0:0:1]); Sun, 24 Dec 2017 07:49:55 +0900 (JST) X-Virus-Scanned: clamav-milter 0.99.2 at asuka.mahoroba.org X-Virus-Status: Clean X-Spam-Status: No, score=-3.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on asuka.mahoroba.org X-Mailman-Approved-At: Sat, 23 Dec 2017 23:26:37 +0000 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: Sat, 23 Dec 2017 22:50:01 -0000 Hi, I resend this message because it was rejected by ports list. >>>>> On Sat, 23 Dec 2017 17:29:51 -0400 >>>>> Joseph Mingrone said: jrm> - mail/x-face-e21 (not fetchable) It seems fetchable. -- Hajimu UMEMOTO ume@mahoroba.org ume@FreeBSD.org http://www.mahoroba.org/~ume/ From owner-freebsd-ports@freebsd.org Sat Dec 23 22:51:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87F95EA7DEE for ; Sat, 23 Dec 2017 22:51:25 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 63D6F79CBE for ; Sat, 23 Dec 2017 22:51:25 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: by mailman.ysv.freebsd.org (Postfix) id 63315EA7DEC; Sat, 23 Dec 2017 22:51:25 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62D2DEA7DEB for ; Sat, 23 Dec 2017 22:51:25 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from mail.mahoroba.org (ent.mahoroba.org [IPv6:2001:2f0:104:8010::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "asuka.mahoroba.org", Issuer "ca.mahoroba.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 078CC79CBC; Sat, 23 Dec 2017 22:51:24 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from vsuiko.mahoroba.org (vsuiko.mahoroba.org [IPv6:2001:2f0:104:8010:a00:27ff:feb0:c2e]) (user=ume mech=DIGEST-MD5 bits=0) by mail.mahoroba.org (8.15.2/8.15.2) with ESMTPSA/inet6 id vBNMpIuM075097 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Dec 2017 07:51:18 +0900 (JST) (envelope-from ume@mahoroba.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mahoroba.org; s=20081103; t=1514069478; bh=rljBYrZqck/zGOXF8aOLNn3NsmMhnb64IJ+1+tkP9TI=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=PnFZn4+IB0/37cft3ShpT7Kvv9O4ZqGeDtPXBdvxYbKCIbF/KU2Xv/A68LW9Cc0Ta YddYXZmEG1++/RLo7GlKmHbyMg2lRlgZ8sjhxRUzyV1TsdzBBM4F2gy9tLB05g8iKG ZfkDMWnE2z3izHHdZW66J29T5Dj20TjmixXIJOwA= Date: Sun, 24 Dec 2017 07:51:17 +0900 Message-ID: From: Hajimu UMEMOTO To: Joseph Mingrone Cc: ports@FreeBSD.org, ume@FreeBSD.org, dryice@dryice.name, dryice@FreeBSD.org, nobutaka@FreeBSD.org, joe@thrallingpenguin.com, yasu@utahime.org, kuriyama@FreeBSD.org, tz@FreeBSD.org, hrs@FreeBSD.org Subject: Re: Are these Emacs ports still useful? In-Reply-To: <86d135nne8.fsf@phe.ftfl.ca> References: <86d135nne8.fsf@phe.ftfl.ca> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO) X-Operating-System: FreeBSD 11.1-STABLE X-PGP-Key: http://www.mahoroba.org/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.mahoroba.org [IPv6:2001:2f0:104:8010:0:0:0:1]); Sun, 24 Dec 2017 07:51:18 +0900 (JST) X-Virus-Scanned: clamav-milter 0.99.2 at asuka.mahoroba.org X-Virus-Status: Clean X-Spam-Status: No, score=-3.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on asuka.mahoroba.org X-Mailman-Approved-At: Sat, 23 Dec 2017 23:27:30 +0000 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: Sat, 23 Dec 2017 22:51:25 -0000 Hi, I resend this message because it was rejected by ports list. >>>>> On Sat, 23 Dec 2017 17:29:51 -0400 >>>>> Joseph Mingrone said: jrm> - mail/xcite (no real updates since 2010, still useful?) I'm using it. It is very useful at least for me. I don't think no update means no usefulness. :-( -- Hajimu UMEMOTO ume@mahoroba.org ume@FreeBSD.org http://www.mahoroba.org/~ume/