21 Mar
2011
21 Mar
'11
6:31 a.m.
On 21 March 2011 00:18, keenerd <keenerd@gmail.com> 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).