On Thu, Mar 24, 2011 at 11:59, David C. Rankin
<drankinatty@...> wrote:
> On 03/24/2011 10:17 AM, Robert Xu wrote:
>>
>> On Thu, Mar 24, 2011 at 11:04, David C. Rankin
>> <drankinatty@...>  wrote:
>>>
>>> On 03/21/2011 01:42 PM, David C. Rankin wrote:
>>>>
>>>> On 03/17/2011 01:14 PM, Kristopher Gamrat wrote:
>>>>>
>>>>> Right before you commit, do "svn add *". This will add the stuff to
>>>>> your local copy of svn. After, you no longer need to use the add
>>>>> function except if you add something else, for which you would replace
>>>>> the star with the new item. To remove some, it is "svn delete item",
>>>>> replacing item with what you want to delete.
>>>>>
>>>>
>>>> Thanks Tim, Kristopher, I'll give it a go after work today :)
>>>>
>>>
>>> Hah!!  It worked :) Arch pkgbuilds are in the svn repo.  Sorry for the
>>> delay
>>> -- real world called ;-)
>>>
>>> --
>>> David C. Rankin, J.D.,P.E.
>>>
>>
>> Can you please upload all these files to SVN in a non-tar.gz format?
>> like a folder for each package.
>> ex:
>>
>> master/
>>      trinity-kdebase/
>>      trinity-kdelibs/
>> ...
>>
>>
>
> Yes, but traditionally, Arch PKGBUILDS are always contained within .tar.gz
> packages that also contain all *needed* patches for the build. It would be
> somewhat meaningless to have the PKGBUILDS that require patches uploaded as
> plain text. (they wouldn't build anything - Qt3, etc..) At least for Trinity
> there are only a couple that have patches, so that will help. What I can do
> it create a structure like
>
> master
>  \PKGBUILDS
>      \trinity-kdebase
>          \PKGBUILD
>      \ etc...
>
> That would just hold the PKGBUILD files by themselves, but I suspect you
> want the PKGBUILD + patches in each of the directories.
>
> I expanded and did the commit. Let me know if that is what you wanted :)
>
>
Yup!
Please remove the svn-commit.tmp though :P


-- 
later, Robert Xu