[Slackbuilds-users] for testing - 'sbopkg' tool
chess at chessgriffin.com
Mon Mar 24 12:37:30 EDT 2008
Alan Hicks wrote:
> 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
>> 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.
Yeah, the only reason I specifically did not include --delete was that I
did not want to delete the source tarballs to save having to redownload
them. However, maybe a separate directory could be created where all
source tarballs are kept (like the /distfiles directory in FreeBSD) and
that this directory is checked for a copy of the source tarball before
building the package. If it's there, the source is moved to where it
needs to be for the SlackBuild to run. If not, it's downloaded into
that directory for future use.
GPG Key: 0x0C7558C3
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 250 bytes
Desc: OpenPGP digital signature
More information about the Slackbuilds-users