FreeBSD ports you maintain which are out of date
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/po...@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. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: OSS Audio
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 FreeBSD 8. 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, If they wouldn't use the OSS API on FreeBSD, they wouldn't be able to play and sound. If they use it to the full extend what is possible and makes sense, I don't know. Anyone is free to work with the developers of those servers to improve the FreeBSD parts in those programs. 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 Isn't this what the port audio/alsa-lib is about? server. Canberra's (computer sounds output) API especially needs to Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgp89bkidfS8o.pgp Description: Digitale PGP-Signatur
Re: OSS Audio
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 alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgp67Ffe5iiy9.pgp Description: Digitale PGP-Signatur
Re: OSS Audio
On Tue, Dec 19, 2017 at 12:11 AM, Alexander Leidinger < alexan...@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 alexan...@leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.orgnetch...@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? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Procmail got updated!
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." ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Portmaster error
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 < > amvandem...@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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Procmail got updated!
On Mon, 18 Dec 2017 19:09:30 +0100 "Matthias Andree" said 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." FWIW procmail.org has shown that banner since 2015-11 (november, 2015). A safe bet, that they won't be changing that anytime soon. :-) --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Can we have multiple flavors for a port?
Le 16/12/2017 à 15:24, Stefan Esser a écrit : > The answer I received was very clear: There can only be 1 flavor per port > 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. -- Mathieu Arnold signature.asc Description: OpenPGP digital signature
Re: A small problem after switching from portmaster to synth
I don't think this is related to portmaster or synth. The mismatched checksums 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 script expects? Or are these two different things that I'm not understanding? Thanks, Kyle -- Kyle Dippery Engineering Computing Services 219 RMB 859-257-1346 From: owner-freebsd-po...@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 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 ___ freebsd-ports@freebsd.org mailing list https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-ports&data=02%7C01%7Ckyle.dippery%40uky.edu%7Cbce06d4c49fd44b9348508d54650e860%7C2b30530b69b64457b818481cb53d42ae%7C0%7C0%7C636492235661238859&sdata=I2XySEihgN%2FJaJpx4hLq8YW45conTbwkHKkMTdRkhqw%3D&reserved=0 To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Option vs. flavor?
Le 17/12/2017 à 15:32, Adam Weinberger a écrit : >> 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 do not really see any reason to set NO_PACKAGE. There already are big packages in our repositories: -rw-r--r-- 2 root wheel 1,0G 10 déc. 05:49 ufoai-data-2.5.txz -rw-r--r-- 2 root wheel 1,1G 14 déc. 10:06 texlive-docs-20150523.txz -rw-r--r-- 2 root wheel 1,3G 10 déc. 15:30 flightgear-data-2017.3.1.txz -rw-r--r-- 2 root wheel 1,5G 14 déc. 20:24 diaspora-1.1.1_1.txz -rw-r--r-- 2 root wheel 1,7G 10 déc. 05:20 urbanterror-data-4.2.023.txz -- Mathieu Arnold signature.asc Description: OpenPGP digital signature
Re: Can we have multiple flavors for a port?
Le 16/12/2017 à 14:51, Matthew Seaman a écrit : > 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= 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 > > -- Mathieu Arnold signature.asc Description: OpenPGP digital signature
FLAVOR for Qt4 and Qt5 (was Re: Flavor or not for this port?)
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-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Canberra
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. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: A small problem after switching from portmaster to synth
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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg flavors breaks "make run-depends-list"
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 Mathieu, 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 À: ja...@thompson.dyslexicfish.net; po...@freebsd.org Objet: Re: pkg flavors breaks "make run-depends-list" Le 01/12/2017 à 10:17, ja...@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.) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Procmail got updated!
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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: A small problem after switching from portmaster to synth
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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Canberra
>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-unsubscr...@freebsd.org"
Re: Canberra
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-unsubscr...@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. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports and LLVM's lld linker
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*-client230 lang/fpc76 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Canberra
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/]. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: A small problem after switching from portmaster to synth
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 E
Re: Procmail got updated!
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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Canberra
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. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Canberra
The port audio/freedesktop-sound-theme just has sound files, and no libraries. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
devel/R-cran-gsubfn: broken because of missing dependency
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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg flavors breaks "make run-depends-list"
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-unsubscr...@freebsd.org"
Re: A small problem after switching from portmaster to synth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224407 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/R-cran-gsubfn: broken because of missing dependency
Is in math/R the option tcl/tk=on? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Canberra
> 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. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Canberra
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. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/R-cran-gsubfn: broken because of missing dependency
On my system (with tcl/tk in math/R=on) no problem (10.4amd64). ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
