On Sun, Mar 20, 2011 at 11:55 AM, Evangelos Foutras wrote:

On Sun, Mar 20, 2011 at 6:18 PM, keenerd wrote:

...

It seems accidentally commiting package binaries is an easy error among new TUs.  A simple way to keep this from happening: svn propset svn:ignore '*.pkg.*' .

That would not prevent source tarballs (say foobar-software-1.2.3.tar.gz) from being added to the repo by 'svn add *'.

So, let's just be careful when adding files and never use 'svn add *'. :)

...

It does not occur often (only twice in the last year) but why not use the tools we have to their fullest.

If it's only happened twice in the period of one year, I'd say it's a non-issue.

I think the better solution is to update the wiki information rather then letting new TUs wander off without someone holding their hand. I think someone needs to step up and update things that a TU should know before doing anything.

Hi, On Mon, 21 Mar 2011, Ray Rashif wrote:

Is the packaging workflow not clear enough from the guidelines?

I have to admit (and I don't intend to offend anyone) that I found it a little confusing at first, though the "how to be a packager" page appears to have become a little clearer recently :-) It confused me a little that the "How to use SVN" and "The Process" sections are separate but cover some of the same matierial, though the latter with e.g. communitypkg, which then doesn't require some of the aforementioned steps. I guess looking back it might have been helpful to have the process laid out separately for the use cases of "I want to add, build and release a new package" and "I am maintaining a package and want to upgrade it, build it and release it". Does this make sense? Pete. PS. Having said that, I don't think there's any major problem with the instructions (but since you asked, eh?) We all obviously learnt how to do it (unless I was the one who made the mistakes and everyone's being very polite!)

When i was working on arch-games we used this .gitignore. https://github.com/Arch-Games/arch-games/blob/master/.gitignore Ofcourse it doesn't match everything but it helps, although i have never had issues. -- Jelle van der Waa On Mon, 2011-03-21 at 14:31 +0800, Ray Rashif wrote:

On 21 March 2011 00:18, keenerd wrote:

...

It seems accidentally commiting package binaries is an easy error among new TUs.

Never heard of this accident. New TUs should always clear things up before jumping in. One or two mistakes are fine.

Is the packaging workflow not clear enough from the guidelines? Two distinct steps for PKGBUILDs and binaries respectively:

* SVN (commit) for buildscripts ** SVN (archrelease) to "finalise"

* SSH (scp) for packages ** SSH (db-update) to "distribute"

Now, if you accidentally make the addition after a build, and then commit, you have to change your habit. Make the addition, then do the build, then commit (using devtools).