Git-Url: http://git.frugalware.org/gitweb/gitweb.cgi?p=pacman-tools.git;a=commitdiff;h=deec63f0dda750351122fd0772601bc6850ee70b
commit deec63f0dda750351122fd0772601bc6850ee70b Author: Miklos Vajna <vmik...@frugalware.org> Date: Sat Jul 2 11:33:05 2011 +0200 repoman: what to use a wip repo, when to feed syncd diff --git a/repoman.txt b/repoman.txt index e8f4aa7..da5cde7 100644 --- a/repoman.txt +++ b/repoman.txt @@ -207,6 +207,19 @@ $ repoman -k push WARNING: You should not use 'repoman push' unless you understand what it does! +Also, if you built a package locally, tested it, but you do not want to +upload it (lack of bandwidth, avoid some oddity in your local build +environment, etc.), you can do a simple: + +---- +$ git push +---- + +and buildservers will build the binary package for you. + +IMPORTANT: Never use the above command to publish packages you did not +test locally! + == Removing packages Removing a package means that you want to remove the buildscript and @@ -260,6 +273,11 @@ WIP stands for "Work In Progress". Such repos are used usually only for a few days or weeks, if you except that a package upgrade will break several others, then it's good to create a WIP repo, and merge when you fixed all the revdeps. +In general, if you expect that the breakage you introduce takes more +than a workday to fix, please use a WIP repo. If you do so, nobody will +urge you to finish your work quickly -- and it's free, so if you are +unsure, use this feature. + === Before you begin If the repo you use for your work already exists, it may need some work: _______________________________________________ Frugalware-git mailing list Frugalware-git@frugalware.org http://frugalware.org/mailman/listinfo/frugalware-git
