2008/2/27, Xavier <[EMAIL PROTECTED]>: > On Wed, Feb 27, 2008 at 05:09:11PM +0100, Thomas Bächler wrote: > > I am not sure if our repository scripts already recognize that. Anyway, > > the package has a force flag in the repo db and is updated properly. > > > > > I can't assure you that it works, but the updatesync-many script (if that's > used) apparently support the new, correct, and consistent syntax : > > http://projects.archlinux.org/git/?p=dbscripts.git;a=blob;f=updatesync-many;h=40c5e4d8bc0e867bc090d3dc3b53e63391087f35;hb=HEAD#l125 > > Besides, since makepkg 3.1.2, the options=(force) syntax in PKGBUILD is > supported, which means this information is now put in the packages themselves > (in .PKGINFO). > This information will then be recognized by repo-add when adding a package to > a database. > Before 3.1.2, specifying the force flag in PKGBUILD had no effect to makepkg > and repo-add. The only way was to use repo-add --force when adding the > package. This option is now deprecated in favor of the above method. > > To sum up, if you use the standard makepkg / repo-add tools, only > options=(force) will work. > And I heard that making use of repo-add in dbscripts was Aaron's first > priority :)
ehm, shouldn't all packages that have 'force' (in either form) be rebuilt with makepkg 3.1.2 then? otherwise old packages won't get 'forced' in db. -- Roman Kyrylych (Роман Кирилич)
