Guys,
I have completed a set of traditional PKGBUILD scripts for Trinity that
download the needed svn source and build the Trinity packages as usual rather
than you needing to put the PKGBUILD script in the svn tree. The are normal
tarballs that contain the PKGBUILDs and any patches needed.
N
On 02/17/2011 06:31 PM, Jan Steffens wrote:
> makepkg includes some magic to adjust the $pkgver - however the
> variables have to be named _svntrunk and _svnmod. See man PKGBUILD,
> section DEVELOPMENT DIRECTIVES.
>
Thank you Jan,
That is *exactly* what I was missing. I could have stared at:
On Fri, Feb 18, 2011 at 1:10 AM, David C. Rankin
wrote:
> Guys,
>
> I'm working on a second set of pkgbuild for Trinity that do the svn download
> for you and work like normal pkgbuilds for other svn projects.
>
> One issue I'm having is getting the "finished package name" to include the
> svn
Guys,
I'm working on a second set of pkgbuild for Trinity that do the svn download
for you and work like normal pkgbuilds for other svn projects.
One issue I'm having is getting the "finished package name" to include the svn
revision as $pkgver instead of the initial (eg. pkgver=).
The
On Thursday 17 of February 2011 23:01:00 David C. Rankin wrote:
> Guys,
>
> Removing kde4 from a test box to work with Trinity, I ran across a few
> kde4 files that looked like they were orphans. I had already removed kde4
> with:
>
> pacman -R kde gtk-kde4 kdebindings-smoke kdeplasma-addons-li
Guys,
Removing kde4 from a test box to work with Trinity, I ran across a few kde4
files that looked like they were orphans. I had already removed kde4 with:
pacman -R kde gtk-kde4 kdebindings-smoke kdeplasma-addons-libs kmldonkey
konq-plugins kopete-cryptography qtcurve-kde4 yakuake
Checking
At Donnerstag, 17. Februar 2011 21:30 David C. Rankin wrote:
> Just a quick question on the vi dependency of mailx. Why not mailx-
heirloom? It
> provides a great deal more capability with attachments, and flexibility as a
cli
> mailer. The issues is down in the noise, but why drive a pin
Guys,
Just a quick question on the vi dependency of mailx. Why not
mailx-heirloom? It
provides a great deal more capability with attachments, and flexibility as a cli
mailer. The issues is down in the noise, but why drive a pinto if you can drive
a jag?
--
David C. Rankin, J.D.,P.E.
On Wednesday 16 February 2011 17:32:59 David C. Rankin wrote:
> It works! After building kdebase (and fighting with other modules), I
> just decided to start trinity and see if it would work. Changed ~/.xinitrc
> to 'startkde' and then typed 'startx' and:
>
> http://www.3111skyline.com/dl/dt/tri
On Thu, Feb 17, 2011 at 06:25, Thomas S Hatch wrote:
[...]
> Heh, I like OCaml, but I chose Python for a few reasons, one was so that
> more people could hack on it, I want it to be very modular, so for instance
> it will be possible to make a variety of modules to watch different SCM
> managers,
10 matches
Mail list logo
