[arch-general] Note on Trinity R14 (3.5.14)
Guys, There will be an upcoming release of TDE 3.5.14 in the next few months and I have worked to update the build system for Arch. All packages below are building on current libraries. The only AUR base package utilized is HAL. I will update the wiki with current information after the remaining PKGBUILD development is complete. Many bugs have been fixed and enhancements added. The desktop is significantly faster than 3.5.10, 3.5.12 or 3.5.13 without any additional bloat. See trinitydesktop.org for the latest info. If you have any interest in contributing, please feel free to join Calvin, Pawell, Baho and I on the project. The current list of packages building is: tde-abakus tde-arts tde-dbus-1-tqt tde-dbus-tqt tde-dolphin tde-gtk-qt-engine tde-kgtk-qt3 tde-kio-locate tde-kipi-plugins tde-kpowersave tde-libart-lgpl tde-libcaldav tde-libcarddav tde-libkdcraw tde-libkexiv2 tde-libkipi tde-libksquirrel tde-python-tqt tde-rosegarden tde-sip(replaces sip) tde-sip4-tqt (replaces python2-sip) tde-tde-style-qtcurve tde-tdeaddons tde-tdeartwork tde-tdebase(with upower) tde-tdegames tde-tdegraphics tde-tdelibs tde-tdemultimedia tde-tdenetwork tde-tdepim tde-tdesvn tde-tdetoys tde-tdeutils tde-tdevelop tde-tdewebdev tde-tqca-tls tde-tqt3 tde-tqtinterface tde-wlassistant That is a majority of the desktop and it is truly a joy to use. Currently I have a development build script for building. Once R14 is released, I will revise it to build from traditional pkgbuild.src.tz files and make that available for anyone interested. I don't know if kaiting still has server space, but I have binary packages for both i686 and x86_64 that I can make available for testing. -- David C. Rankin, J.D.,P.E.
[arch-general] [SOLVED - id 10 t error] Re: arch chroot - makepkg.conf - Howto unset $PKGDEST, $SRCDEST, etc...
On 03/23/2012 04:49 PM, David C. Rankin wrote: > Where do I remove this information from the chroot cache so everything is > reset to the default and finished packages are left in the original PKGBUILD > directory? > > Also, do I have to edit both $CHROOT/root and $CHROOT/david, or just > $CHROOT/david makepkg.conf? Sorry for the noise, seemed I slipped and did a vi /etc/makepkg.conf when I set the PKGDEST. I don't understand why that mattered, but removing the setting from the host system makepkg.conf allowed the chroot/etc/makepkg.conf to put the packages in their default location. (an 'id 10 t' error, or in all caps w/o spaces 'ID10T' error :) -- David C. Rankin, J.D.,P.E.
[arch-general] arch chroot - makepkg.conf - Howto unset $PKGDEST, $SRCDEST, etc...
Guys, I experimented with different locations for PKGDEST, SRCDEST, etc. and now I just want to have the finished package left in the default directory where the PKGBUILD is located. However, when I comment out the PKGDEST, SRCDEST and SRCPKGDEST, the finished packages still show up in the last set PKGDEST directory. Where do I remove this information from the chroot cache so everything is reset to the default and finished packages are left in the original PKGBUILD directory? Also, do I have to edit both $CHROOT/root and $CHROOT/david, or just $CHROOT/david makepkg.conf? -- David C. Rankin, J.D.,P.E.
Re: [arch-general] makechrootpkg -d goes in repo.db why not local.db consistent with DevWiki?
On 03/22/2012 06:22 PM, baho Utot wrote: > On 03/22/2012 06:54 PM, David C. Rankin wrote: >> Guys, >> >>I have followed the DeveloperWiki:Building in a Clean Chroot page closely >> for >> the trinity build and it has worked fine. For major rebuilds it has you >> create a >> local.db.tar.gz in /root/repo as a local repo. However, I was experimenting >> with >> makechrootpkg -d and it suggest it will add the package to the local /repo, >> but >> instead it creates /root/repo/repo.db. Why not local.db? >> >>Looking at the developer wiki and then looking at the help file for >> makechrootpkg: >> >>-d Add the package to a local db at /repo after building >> >>I expected both to be consistent. Is there a reason for the difference? >> > > The repo.db.tar.gz is what I would expect. > > -d says It will add the path to a local repo not that the repo database will > be > called local.db.tar.gz > > Just put > > [repo] > Server = file:///repo > > into the pacman.conf in the chroot directory and it will work. > > Then the chroot evironment will be able to load/install dependcy packages when > needed for building the "package under building". > > I do this all the time. > > > That's what I would have thought, but the DeveloperWiki says: The chmod statement allows for the coping of package files and for the creation of the local repo as your user rather than root. cp $CHROOT/root/repo cd $CHROOT/root/repo repo-add local.db.tar.gz Then add the local repo to $CHROOT/root/etc/pacman.conf [local] Server = file:///repo I think they should be consistent. No big deal. The point being if you start out following DeveloperWiki:Building in a Clean Chroot and the read the description for -d you are left wondering "Why in the heck are they not consistent?" :) -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Anyone willing to share experiences running Arch on a current-gen MacBook Pro?
I had two macbook pro (one unibody and a previous one) and I finally got rid of it last year to buy a dell latitude. I could not be more happy, and I don't really understand in what sense macbooks are so good. - the pro machine has a crappy glossy monitor by default - it gets too hot (mine definitively did) - optical drive fails all the time - it's a lot more painful than other machines to get Linux running correctly - the warranty is ridicolous, 1 year instead of my 3 by default so well I really don't get it ;)
