On 7/24/05, Philip Dillon-Thiselton <[EMAIL PROTECTED]> wrote:
Hello all,
I have done a nice big rewrite of my CVS/SVN guidelines and now think it
is much better. I have also created the worlds simplest "wrapper" to
allow you to build cvs and svn pkgs that are automatically updated with
the current date/revision number without using back tick execution in
the PKGBUILD itself. The script depends on a few simple custom
variables and a compatible checkout command but leaves you with a
PKGBUILD that can be used by anyone, whether they run the script or not,
which makes it great for working with the AUR.
One thing I don't know is if it is possible to build in the checkout dir
and then use a svn/cvs command to clean up the checked out code read for
the next check out - if someone could fill me in on that it's be even better
Let me know what you all think, it's on the new wiki - of course:
http://www.archlinux.org/archwiki/index.php/Arch_CVS/SVN_PKGBUILD_guidelines
The migration of the wiki is not yet complete but i think it is ok for
you to have a look at it!
Phil
Philip Dillon-Thiselton wrote:
> Jason Chu wrote:
>
>> On Tue, Jul 12, 2005 at 06:56:26PM +0100, Philip Dillon-Thiselton wrote:
>>
>>
>>> I take it this is the guidelines I am trying to develop? The AUR
>>> freaks out if your try and upload a PKGBUILD without source or
>>> md5sum fields - but it will let you put blank ones :)
>>>
>>
>>
>> I think that's probably something that needs to be fixed in the AUR
>> then.
>> The parsing script is definitely sub-par.
>>
>>
> It be better if it checked that they were filled _if they were there_
> rather than if they are there or not. Actually, it'd be ideal if:
>
> Check for a source field
> - If source= found but empty maybe fail
> - If source= found and filled then check for m5sums= - should also
> be able to match the number of source entries to the number of md5sum
> entries
> - If source= not found at all then skip md5sums= check
>
>> Jason
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> arch mailing list
>> [email protected]
>> http://www.archlinux.org/mailman/listinfo/arch
>>
>>
>
> _______________________________________________
> arch mailing list
> [email protected]
> http://www.archlinux.org/mailman/listinfo/arch
>
>
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
