[arch-general] Any place I can host the Trinity binary packages for testing?
Guys, Is there a place I can upload and host the finished Trinity packages for testing? I have less than 500K upstream capability at home, so that makes hosting the binaries impossible for me. I have both i686 and x86_64 packages done for the following: 20:53 archangel:~/arch/tpkg> ls -1 i686/ trinity-arts-1221147-1.1-i686.pkg.tar.xz trinity-kdebase-1221122-1.0-i686.pkg.tar.xz trinity-kdelibs-1221122-1.1-i686.pkg.tar.xz trinity-kdevelop-1221146-1.0-i686.pkg.tar.xz trinity-kdewebdev-1221146-1.0-i686.pkg.tar.xz trinity-pyqt3-3.18.1-9-i686.pkg.tar.xz trinity-qt3-3.3.8-20-i686.pkg.tar.xz trinity-tqtinterface-1221146-1.0-i686.pkg.tar.xz The total size is 69M for i686 20:59 archangel:~/arch/tpkg> ls -1 x86_64/ trinity-arts-1220940-1.1-x86_64.pkg.tar.xz trinity-kdebase-1221126-1.0-x86_64.pkg.tar.xz trinity-kdelibs-1220940-1.1-x86_64.pkg.tar.xz trinity-kdevelop-1221141-1.0-x86_64.pkg.tar.xz trinity-kdewebdev-1221146-1.0-x86_64.pkg.tar.xz trinity-pyqt3-3.18.1-9-x86_64.pkg.tar.xz trinity-qt3-3.3.8-20-x86_64.pkg.tar.xz trinity-tqtinterface-1221146-1.0-x86_64.pkg.tar.xz The total size is 65M for x86_64 If there is any interest, I can put them up somewhere for testing. I'm running them in virtualbox at the moment, but there is no reason you couldn't just install the binaries alongside kde4 or kdemod3 for that matter. They install trinity in '/opt/trinity'. The only impact to installing along with kdemod3 is the updated Qt3 will make kdemod3 gwenview unhappy, but other than that, they should get along peacefully. Let me know if there is any interest for hosting the binaries somewhere. -- David C. Rankin, J.D.,P.E.
On 02/16/2011 09:07 PM, David C. Rankin wrote:
there is no reason you couldn't just install the binaries alongside kde4 or kdemod3 for that matter. They install trinity in '/opt/trinity'.
Correction... Stick to a clean environment for now. I just installed Trinity on a box with both kdemod3 and kde4 present and started Trinity. It started, the kdemod3 splash appeared, then Akonadi/nepomuk started trying to index everything, the kde4 plasma panel loaded and the window decorations disappeared. I suspect it was pulling the decorations from kdemod3 not finding what it wanted. The akonadi mess and plasma-panel were from /usr/share/autostart. I'll have to try it on a box with just kde4. Sure runs good in a clean environment though :) -- David C. Rankin, J.D.,P.E.
On 02/16/2011 10:08 PM, David C. Rankin wrote:
On 02/16/2011 09:07 PM, David C. Rankin wrote:
there is no reason you couldn't just install the binaries alongside kde4 or kdemod3 for that matter. They install trinity in '/opt/trinity'.
Correction...
Stick to a clean environment for now. I just installed Trinity on a box with both kdemod3 and kde4 present and started Trinity. It started, the kdemod3 splash appeared, then Akonadi/nepomuk started trying to index everything, the kde4 plasma panel loaded and the window decorations disappeared. I suspect it was pulling the decorations from kdemod3 not finding what it wanted. The akonadi mess and plasma-panel were from /usr/share/autostart. I'll have to try it on a box with just kde4. Sure runs good in a clean environment though :)
Darn, I had moved ~/.kde and ~/.kde4 to ~/.kde-sav and ~/.kde4-sav, but forgot to delete the kbuildsycoca from /var/tmp. I'll retest that issue because I think the previous cache from kdemod3 probably drove Trinity nuts due to the crystal window decor not being present in Trinity - yet. The real challenge is telling Trinity to ignore the kde4 autostart files in /usr/share/autostart. I don't know if there is anything I can do from a packaging standpoint to fix that, but I posted the issue to Trinity to see if the code can be fixed to ignore the kde4 autostart files within Trinity going forward. If there is anyway to do this from a pkgbuild or startup script standpoint on Arch, I would welcome the ideas. -- David C. Rankin, J.D.,P.E.
On Wed, Feb 16, 2011 at 10:07 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
Is there a place I can upload and host the finished Trinity packages for testing? I have less than 500K upstream capability at home, so that makes hosting the binaries impossible for me. I have both i686 and x86_64 packages done for the following:
20:53 archangel:~/arch/tpkg> ls -1 i686/ trinity-arts-1221147-1.1-i686.pkg.tar.xz trinity-kdebase-1221122-1.0-i686.pkg.tar.xz trinity-kdelibs-1221122-1.1-i686.pkg.tar.xz trinity-kdevelop-1221146-1.0-i686.pkg.tar.xz trinity-kdewebdev-1221146-1.0-i686.pkg.tar.xz trinity-pyqt3-3.18.1-9-i686.pkg.tar.xz trinity-qt3-3.3.8-20-i686.pkg.tar.xz trinity-tqtinterface-1221146-1.0-i686.pkg.tar.xz
The total size is 69M for i686
20:59 archangel:~/arch/tpkg> ls -1 x86_64/ trinity-arts-1220940-1.1-x86_64.pkg.tar.xz trinity-kdebase-1221126-1.0-x86_64.pkg.tar.xz trinity-kdelibs-1220940-1.1-x86_64.pkg.tar.xz trinity-kdevelop-1221141-1.0-x86_64.pkg.tar.xz trinity-kdewebdev-1221146-1.0-x86_64.pkg.tar.xz trinity-pyqt3-3.18.1-9-x86_64.pkg.tar.xz trinity-qt3-3.3.8-20-x86_64.pkg.tar.xz trinity-tqtinterface-1221146-1.0-x86_64.pkg.tar.xz
The total size is 65M for x86_64
If there is any interest, I can put them up somewhere for testing. I'm running them in virtualbox at the moment, but there is no reason you couldn't just install the binaries alongside kde4 or kdemod3 for that matter. They install trinity in '/opt/trinity'.
The only impact to installing along with kdemod3 is the updated Qt3 will make kdemod3 gwenview unhappy, but other than that, they should get along peacefully. Let me know if there is any interest for hosting the binaries somewhere.
You can host this stuff on my server if you'd like. Arch-Haskell already hosts their stuff here. Send me an email with your name, email, and your desired uid and I'll get you set up. --Kaiting. -- Kiwis and Limes: http://kaitocracy.blogspot.com/
participants (2)
-
David C. Rankin
-
Kaiting Chen