[Slackbuilds-users] for testing - 'sbopkg' tool

[Alan Hicks]

Chess Griffin wrote:
>> The hard part would be integrating properly with rsync.  You don't 
>> want your next rsync fetch using sbopkg to over-write your local copy 
>> changes.
> 
> Yes, my thoughts exactly.  One idea would be have the sbopkg 
> automatically cp the Slackbuild so it's app.SlackBuild.local or 
> something like that and that's the file that is edited.  Right now, 
> sbopkg uses the -avz options with rsync so local changes will get 
> clobbered.  Not ideal.

Nope.  You need --delete as well.  After all, we occasionally remove whole 
SlackBuild scripts.  Additionally, patches that were necessary in an old 
version might not exist in a new one for example.

You *could* have sbopkg add a file into the source that would prevent it 
from clobbering anything in that source directory, but that becomes a major 
hassel because you'd have to run a while loop to construct all your 
--exclude lines.

One possibility is to create a SBo/local/ branch and --exclude local/. 
sbopkg could copy the entire source directory and structure there if a user 
decided to make any changes.

-- 
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/7aa51995/attachment.asc>