Fix build on 9.3.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 26 2016
Mar 25 2016
Mar 12 2016
s/\+=/=/
Upstream now handles variable substitution for install paths, so only the variables instead of a whole sed command are required.
Mar 6 2016
In D5002#118737, @johjeff_gmail.com wrote:My apologies if this is not the right place to mention this, but I am trying to run the 10.2 binary port of lxqt and I get the following fault when I startx:
/usr/local/bin/lxqt-session: Undefined symbol "_ZN6QDebug9putStringEPK5QCharm"
and then I get dumped back to console. I also tried doing a deinstall and following instructions for building from ports, but that fails during QT5 build. This FreeBSD install is new in a VM with updates applied.
My apologies if this is not the right place to mention this, but I am trying to run the 10.2 binary port of lxqt and I get the following fault when I startx:
Mar 2 2016
In D5510#117726, @mat wrote:There is that, yes
There is that, yes. Also, subpackages, that are coming soon™, need a separator, that won't be anywhere in the package name, the + would be nice.
Implements suggestions from mat.
In D5510#117709, @mat wrote:Yes, and because other people did stupid things does not mean you have to.
Please don't.
Yes, and because other people did stupid things does not mean you have to.
In D5510#117460, @mat wrote:Having + in the PORTNAME is a pain, and should be avoided. As the GitHub project is called powerdxx, maybe this port should be called that too. (even if it installs a powerd++ binary.)
Mar 1 2016
Not installing the man page is a very bad idea, this is FreeBSD, not Linux, we install the basic documentation with our software. And then, there is only one file which installation is controlled by the DOCS option, remove it, and always install the README.md file.
Having + in the PORTNAME is a pain, and should be avoided. As the GitHub project is called powerdxx, maybe this port should be called that too. (even if it installs a powerd++ binary.)
Feb 22 2016
ping @olivierd
Jan 25 2016
In D5002#107786, @rakuco wrote:I keep getting "context not available" for most of the patch. Is there an option I'm too dumb to notice?
I keep getting "context not available" for most of the patch. Is there an option I'm too dumb to notice?
Fix typo, otherwise poudriere complains.
Jan 24 2016
Jan 22 2016
Update Mk/Uses/lxqt.mk after comments from rakuco@:
Jan 21 2016
Jan 20 2016
Nov 10 2015
Oct 14 2015
Oct 13 2015
Sep 25 2015
Aug 28 2015
Aug 9 2015
Jun 12 2015
Jun 11 2015
Not sure is USES is requires, left it alone.