Old kdesvn-buildrc files are still accepted, and the persistent data should also be read
just like it was before (although it will be written out with a different name from now
on).
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-buildrc.xml; revision=1143246
uninitialized variable warnings, and there's probably a cleaner way to achieve the same
effect hanging in there somewhere.
CCBUG:237527
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1131025
I'm doing this to support building multiple branches with git repositories
from the same clone. With this change its possible to have this in the config:
module kdevplatform
branch master
prefix /home/andreas/kdevelop
repository git@gitorious.org:kdevelop/kdevplatform.git
end module
module kdevplatform-stable
branch 1.0
manual-build true
dest-build-dir kdevplatform-stable
dest-dir kdevplatform
prefix /home/andreas/kdevelop-stable
repository git@gitorious.org:kdevelop/kdevplatform.git
end module
To build the stable and development branches of kdevplatform easily with
kdesvn-build and without build-files interfering with one another.
CCMAIL: mpyne@kde.org
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1126303
modules on the command line, then those are directly uninstalled. Otherwise the normal
build list is used, modified so that only modules kdesvn-build thinks it has actually
installed are attempted to be uninstalled. (This means that git modules don't play nice
because I am not setting the last-install-rev persistent property for those yet, sorry).
You can set the option use-clean-install to true in your kdesvn-buildrc to also have
kdesvn-build uninstall a module just before installing it to keep stray files from
accumulating.
Probably not quite fully baked, but should be good enough for 1.12 (the first release it
will show up in).
BUG:211745
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1123842
It's just like --resume-from, except that if you've already verified that your fix
allows the module to build and install there's no reason to run kdesvn-build through
the same process again. Using --resume-after tells kdesvn-build to pick up with the
module after the one you've supplied (which would normally be the module that failed).
CCMAIL:toma@kde.org
svn path=/trunk/KDE/kdesdk/doc/scripts/kdesvn-build/; revision=1089384
have a chance to take effect before looking at global fallbacks. This allows
e.g. module-base-path for a module to still override a global branch
(previously only module-specific branch options would do so)
BUG:223341
CCMAIL:faure@kde.org
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1082654
using CFQ, in kdesvn-build. Also update the documentation at the same time for once.
To enable, set use-idle-io-priority to true in your .kdesvn-buildrc (it is
disabled by default for now).
BUG:194635
svn path=/trunk/KDE/kdesdk/doc/scripts/kdesvn-build/; revision=1082647
defines. (This was broken after the switch to resetting env vars for each module).
BUG:217638
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1072397
Hansen (the bug reporter).
Also make miscellaneous cleanups of some of the various var names involved.
BUG:220242
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1072396
While I was at it I improved the "no config" message to show what file to edit
to get a configuration.
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1070567
* Fix options available in kate syntax highlighting file for kdesvn-buildrc and fix the
space/tab consistency while I'm at it.
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1063683
- The ssh-agent check is now performed for all svn-servers being used and not just
global (although this case is so rare no one has complained about it). More importantly,
git:// module updates do not complain about ssh-agent.
- SSL signature checking is only performed if a Subversion module is being updated (it's
not required for gitorious.org, at least not yet).
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1061547
- The weirdly-named remote repository name is only used if there is not an existing remote
name to use.
- kdesvn-build will find and use existing remote-tracking branches to perform a checkout
if necessary.
- If a remote/branch combination is requested that isn't already available then kdesvn-build
will create a remote-tracking branch and try to intelligently name it.
The update mechanism has had a git merge step added for the highly common case where the
branch didn't change since without git pull we don't actually advance our checkout :(
Please test test test and let me know if there are issues.
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1061544
would intermingle. Unfortunately we're also quieter even when the user select --verbose
(also noted by Trever Fischer who provided a patch that was almost exactly right :)
Fixed now.
CCMAIL:tdfischer@fedoraproject.org
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1059157
kernel.org git user guide on how to do what I want better. In this case the alias is
always created so there shouldn't be missing alias errors though.
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1058743
required for one of the ways I was doing git updates when prototyping the feature but
doesn't appear required the way I'm doing it now.
- Remove -no-exceptions from default qt-copy args and correct spelling of the -dbus
option based on feedback on kde-buildsystem
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1049778
If you are screen-scraping kdesvn-build then you are 1) crazy and 2) now probably in need
of verifying this change doesn't break your script's expectations.
In addition the --src-only and --no-src options have been added (which are just aliases
for --svn-only and --no-svn at this point).
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1039965
- git clone correctly sets up the __kdesvn-build-remote alias
- updating a module should hopefully "always work" since kdesvn-build always
runs the git fetch and git checkout separately, so in theory (and from my
experimentation) the result should be the same whether or not you were on
the right repository already, and whether a remote tracking branch already
existed or not.
One flaw is that if there is a git branch with the same name as the branch name
given in the kdesvn-buildrc file, then kdesvn-build will always use that one
(even if it doesn't point to the correct remote branch). Not sure if this will
be an issue in practice though.
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1039964
Also improve default branch handling.
Finally, split out output "slurping" into a specific subroutine.
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1039951
correctly handle the "branch" option yet, but if you don't mind HEAD then you'll get
the correct build for a KDE module.
For example, this works:
module amarok
repository git://gitorious.org/amarok/amarok.git
end module
If you already have a subversion checkout in that directory, you need to remove it
yourself first, kdesvn-build won't delete your source for you.
Also, warn if you change the repository option since kdesvn-build also doesn't handle
that.
svn path=/trunk/KDE/kdesdk/scripts/kdesvn-build; revision=1013453
Script Kiddy
Michael Pyne
Burkhard Lück
Andreas Pakulat
David Faure