Cal, Pawel, Baho, all,
To keep things straight with PKGBUILDs and source files (including PKGBUILD and patches, etc..) between those that build with Qt3 and those utilizing TQt3, I have simply made a name change:
All Qt3 based packages and sources will be trinity-xxx. Eg:
trinity-tqtinterface trinity-arts
All TQt3 based packages will be tde-xxx. Eg:
tde-tqtinterface tde-arts
...and so on. Let me know your thoughts on this. I thought this made more sense than monkeying with the $pkgver or other variables.
On 2 March 2012 22:28, David C. Rankin drankinatty@suddenlinkmail.com wrote:
Cal, Pawel, Baho, all,
To keep things straight with PKGBUILDs and source files (including PKGBUILD and patches, etc..) between those that build with Qt3 and those utilizing TQt3, I have simply made a name change:
All Qt3 based packages and sources will be trinity-xxx. Eg:
trinity-tqtinterface trinity-arts
All TQt3 based packages will be tde-xxx. Eg:
tde-tqtinterface tde-arts
if
The thing is, tde and trinity are ambiguous, Trinity and tde don't tell you if it's qt3 or not. what about tde-tqt-xxx if it is TQt3 and tde-qt3-xxx for Qt3?
or we could just drop Qt3 builds altogether - that actually seems saner
Calvin
On 03/02/2012 10:55 PM, Calvin Morrison wrote:
or we could just drop Qt3 builds altogether - that actually seems saner
Calvin
That's what I'm trying to do, but you have to work through each PKGBUILD basically line-by-line for any that have custom build() or install() function.
I'm messing with a master-build script that parses the directory setup I have and that has been easiest so far:
## check which Qt being used and set prefix [[ $useqt == tqt3 ]] && _pfx=tde || _pfx=trinity
It could be anything we want. Could easily be:
[[ $useqt == tqt3 ]] && _pfx=trinity-tqt || _pfx=trinity
... that just makes the names longer :)
-
Calvin Morrison -
David C. Rankin