-
Notifications
You must be signed in to change notification settings - Fork 0
pyqt: Add PyQt for Qt4 and Qt5 #209
Conversation
export QTDIR=/usr/local/qt4 | ||
|
||
## The source URL(s) array | ||
SRCURL[0]="file:///src/mariux/beeroot/downloads/PyQt-x11-gpl-${PKGVERSION}.tar.gz" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don’t we download stuff from the Internet, and let Bee itself do the caching?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, but Sourceforge-Urls suck.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
root:afk:/usr/share/bee/# grep sourcef */*.be* | wc
128 145 18424
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
translation: "we have 128 bees with sourceforge URLs, please use them". First question in case of debugging: WTF do these sources come from.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, convinced.
Please prepend commands with |
Don't know what you mean, is there some documentation? |
@thomas, documentation about |
Which parts should be called with 'start_cmd', or will I find 'approved' examples in the repo? |
@thomas, I’d prepend the configure, make, and install lines, because then you also see the passed arguments. |
I forget, that one commit per program would be useful. These two commits are then grouped in a branch (merge/pull request). |
IIRC we have talked about having more than one bee file ina branch, which was ok. The granularity wasn't discussed. To achieve agreements about howto do 'this and that' via the git chat is way tedious. What about having a 'Best-Practices'-thingy somewhere written down? |
I've took a quick look, seems like the thing I've meant. But without the hint I wouldn't have guessed that SubmittingPatches has something to do with creating bee files. |
PyQt is a set of Python v2 and v3 bindings for the Qt application framework. Naming is a bit inconsistent: - PyQt-x11-gpl-4.11.4 -> Qt4 - PyQt5_gpl-5.7 -> Qt5 Homepage: https://www.riverbankcomputing.com/software/pyqt/intro
PyQt is a set of Python v2 and v3 bindings for the Qt application framework. Naming is a bit inconsistent: - PyQt-x11-gpl-4.11.4 -> Qt4 - PyQt5_gpl-5.7 -> Qt5 Homepage: https://www.riverbankcomputing.com/software/pyqt/intro
I've split PyQt for Qt4 and PyQt for Qt5 into two separate commits, squashed the minor fixes ( add start_cmd and switch to sourceforge url ) and rebased on current master. Tree is unchanged. |
I'll install it on the distmaster |
Merci |
PyQt is a set of Python v2 and v3 bindings for the Qt application
framework. Naming is a bit inconsistent:
Homepage:
https://www.riverbankcomputing.com/software/pyqt/intro