[pacman-dev] NEWS for 3.4.0 - very, very draft
A very draft NEWS item based on "git shortlog --no-merges master --not v3.3.0". May be a bit makepkg-centric, but numbers of patches for makepkg is quite high this time and many pacman patches are the "not-newsworthy" type... Anyway, cut/add entries and I can flash it out some more. pacman: -D --database option show required by in -Sii output Architecture --arch option / check package arch / $arch --print/--print-format only extract new DB entiries -Su foo util: deltacleanup rankmirror -> bash repo-add - can create "empty" repo when removing last package makepkg: new packaging variable - changelog Allow overriding pkgver, pkgrel, arch in split packages Can specify subsets of packages to build from a split package warn about references to build root in package deprecate repackaging without a package function can only use package() function strip options are configurable auto abort on any packaging error SRCPKGDEST --skipinteg syntax checking for backup and optdepends entries contrib: pactree - reverse tree
On Sun, May 9, 2010 at 1:09 PM, Allan McRae <allan@archlinux.org> wrote:
A very draft NEWS item based on "git shortlog --no-merges master --not v3.3.0". May be a bit makepkg-centric, but numbers of patches for makepkg is quite high this time and many pacman patches are the "not-newsworthy" type...
That's an interesting git command, but shouldn't you use maint or v3.3.3 rather than v3.3.0 ? And maybe it's better to look at the bug tracker for finding the most important and visible changes : http://bugs.archlinux.org/index.php?do=index&tasks=&project=3&due=69&status[]= But I think your list is already mostly fine, except it miss the single most important change IMO :) commit 0da96abc900560f21c643b255c94a60232f4a24b Author: Nagy Gabor <ngaba@bibl.u-szeged.hu> Date: Tue Jun 9 17:23:46 2009 +0200 Use sync.c for upgrade transaction prepare and commit This patch utilizes the power of sync.c to fix FS#3492 and FS#5798. Now an upgrade transaction is just a sync transaction internally (in alpm), so all sync features are available with -U as well: * conflict resolving * sync dependencies from sync repos * remove unresolvable targets That's two long standing bugs, to say the least.
On 09/05/10 22:22, Xavier Chantry wrote:
On Sun, May 9, 2010 at 1:09 PM, Allan McRae<allan@archlinux.org> wrote:
A very draft NEWS item based on "git shortlog --no-merges master --not v3.3.0". May be a bit makepkg-centric, but numbers of patches for makepkg is quite high this time and many pacman patches are the "not-newsworthy" type...
That's an interesting git command, but shouldn't you use maint or v3.3.3 rather than v3.3.0 ?
No idea... I just discovered how to do that! I figure the maint/v3.3.3 changes to 3.3.0 are not new features so that should not matter.
And maybe it's better to look at the bug tracker for finding the most important and visible changes : http://bugs.archlinux.org/index.php?do=index&tasks=&project=3&due=69&status[]=
But I think your list is already mostly fine, except it miss the single most important change IMO :)
commit 0da96abc900560f21c643b255c94a60232f4a24b Author: Nagy Gabor<ngaba@bibl.u-szeged.hu> Date: Tue Jun 9 17:23:46 2009 +0200
Use sync.c for upgrade transaction prepare and commit
This patch utilizes the power of sync.c to fix FS#3492 and FS#5798. Now an upgrade transaction is just a sync transaction internally (in alpm), so all sync features are available with -U as well: * conflict resolving * sync dependencies from sync repos * remove unresolvable targets
That's two long standing bugs, to say the least.
I very much agree! The commit header just did not stand out to me. Allan
That's an interesting git command, but shouldn't you use maint or v3.3.3 rather than v3.3.0 ?
And maybe it's better to look at the bug tracker for finding the most important and visible changes : http://bugs.archlinux.org/index.php?do=index&tasks=&project=3&due=69&status[]=
But I think your list is already mostly fine, except it miss the single most important change IMO :)
commit 0da96abc900560f21c643b255c94a60232f4a24b Author: Nagy Gabor <ngaba@bibl.u-szeged.hu> Date: Tue Jun 9 17:23:46 2009 +0200
Use sync.c for upgrade transaction prepare and commit
This patch utilizes the power of sync.c to fix FS#3492 and FS#5798. Now an upgrade transaction is just a sync transaction internally (in alpm), so all sync features are available with -U as well: * conflict resolving * sync dependencies from sync repos * remove unresolvable targets
That's two long standing bugs, to say the least.
I mention one more thing (which is related to this patch): The next major pacman release _always_ asks for user confirmation with all -U and -R operations. This behaviour change should be added to (archlinux.org's?) NEWS, since it can break scripts. Scripts are advised use --noconfirm switch to skip user interaction (if needed). Bye
On Sat, May 15, 2010 at 4:53 AM, Nagy Gabor <ngaba@bibl.u-szeged.hu> wrote:
That's an interesting git command, but shouldn't you use maint or v3.3.3 rather than v3.3.0 ?
And maybe it's better to look at the bug tracker for finding the most important and visible changes : http://bugs.archlinux.org/index.php?do=index&tasks=&project=3&due=69&status[]=
But I think your list is already mostly fine, except it miss the single most important change IMO :)
commit 0da96abc900560f21c643b255c94a60232f4a24b Author: Nagy Gabor <ngaba@bibl.u-szeged.hu> Date: Tue Jun 9 17:23:46 2009 +0200
Use sync.c for upgrade transaction prepare and commit
This patch utilizes the power of sync.c to fix FS#3492 and FS#5798. Now an upgrade transaction is just a sync transaction internally (in alpm), so all sync features are available with -U as well: * conflict resolving * sync dependencies from sync repos * remove unresolvable targets
That's two long standing bugs, to say the least.
I mention one more thing (which is related to this patch):
The next major pacman release _always_ asks for user confirmation with all -U and -R operations. This behaviour change should be added to (archlinux.org's?) NEWS, since it can break scripts. Scripts are advised use --noconfirm switch to skip user interaction (if needed).
Bye
Anything for translator?
On Sun, May 9, 2010 at 6:09 AM, Allan McRae <allan@archlinux.org> wrote: > A very draft NEWS item based on "git shortlog --no-merges master --not > v3.3.0". May be a bit makepkg-centric, but numbers of patches for makepkg > is quite high this time and many pacman patches are the "not-newsworthy" > type... > > Anyway, cut/add entries and I can flash it out some more. > > > pacman: > -D --database option > show required by in -Sii output > Architecture --arch option / check package arch / $arch I'd definitely give more space to $arch, as that is a nice deal that should prevent some stupid errors (and allow us to make pacman-mirrorlist 'any', yay). > --print/--print-format > only extract new DB entiries > -Su foo * Allow -Qo to perform a functional 'which' * Cache cleaning cleans all directories, not just first > > util: > deltacleanup > rankmirror -> bash > repo-add - can create "empty" repo when removing last package Static vercmp > > makepkg: > new packaging variable - changelog > Allow overriding pkgver, pkgrel, arch in split packages > Can specify subsets of packages to build from a split package > warn about references to build root in package > deprecate repackaging without a package function > can only use package() function > strip options are configurable > auto abort on any packaging error > SRCPKGDEST > --skipinteg > syntax checking for backup and optdepends entries bash [ -> [[ refactor? I usually put big changes like that in NEWS > > contrib: > pactree - reverse tree bacman- small improvements?
participants (5)
-
Allan McRae
-
Dan McGee
-
Nagy Gabor
-
Xavier Chantry
-
甘露(Gan Lu)