On Fri, May 21, 2010 at 12:01 AM, Philipp wrote:
> One of the reasons why I like Arch Linux so much is that it makes it
> easy to work together with upstream. Through makepkg I can install the
> latest, even VCS, version in a sane and very comfortable way.
>
> So far I've mainly been testing, repo
On Thu, May 20, 2010 at 18:01, Philipp wrote:
> Now if I wanted to contribute code back to a project that uses git, how
> would I do that without losing the comfort and safety of makepkg?
> I figured it should be possible to write a PKGBUILD that gets the latest
> upstream changes but also integra
One of the reasons why I like Arch Linux so much is that it makes it
easy to work together with upstream. Through makepkg I can install the
latest, even VCS, version in a sane and very comfortable way.
So far I've mainly been testing, reporting bugs, stuff like that, but
rarely needed to contribut
On 20/05/2010, Allan McRae wrote:
> This seems way too complicated... and I am not sure of the advantages
> over the current TODO list system.
>
> The TODO list which shows when packages are built for only one
> architecture. So if someone can only build for one Arch, another person
> already c
-Original Message-
> Date: Thu, 20 May 2010 09:40:56 +0200
> Subject: Re: [aur-general] PKGBUILD for django - orphaned and
> out-of-date
> From: "stefan-husm...@t-online.de"
> To: "Discussion about the Arch User Repository \(AUR\)"
>
>
> -Original Message-
> > Date: Thu, 20 May
-Original Message-
> Date: Thu, 20 May 2010 08:38:54 +0200
> Subject: [aur-general] PKGBUILD for django - orphaned and out-of-date
> From: Puneeth Chaganti
> To: "Discussion about the Arch User Repository (AUR)"
>
> Hello,
>
> The django package [extra/django 1.1.1-4] is out-of-date an
Hello,
The django package [extra/django 1.1.1-4] is out-of-date and orphaned.
Here is a package build for updating it to 1.1.2.
I'm not sure if this should be updated to 1.2 or a new package should
be created for that.
Thanks,
~ punchagan
PKGBUILD
Description: Binary data
