Re: [pacman-dev] [PATCH 6/6] New VerbosePkgLists option

2011-02-26 Thread Xavier Chantry
On Fri, Feb 25, 2011 at 4:30 PM, Dan McGee wrote: > On Mon, Feb 21, 2011 at 1:02 PM, Jakob Gruber wrote: >> diff --git a/src/pacman/conf.h b/src/pacman/conf.h >> index 92c379f..f440090 100644 >> --- a/src/pacman/conf.h >> +++ b/src/pacman/conf.h >> @@ -70,6 +70,7 @@ typedef struct __config_t { >>

Re: [pacman-dev] Style questions and concerns

2011-02-26 Thread Xavier Chantry
On Fri, Feb 25, 2011 at 5:27 PM, Dan McGee wrote: > I've noticed these things a lot in recent patches, so let the > discussion commence. > > 1) typedef-ed structs. This is just a "copy the rest of them" habit, > but I really feel we should stop doing this, only typedef-ing when we > are making a p

Re: [pacman-dev] [PATCH 6/6] New VerbosePkgLists option

2011-02-26 Thread Xavier Chantry
On Mon, Feb 21, 2011 at 8:02 PM, Jakob Gruber wrote: > If enabled, displays package lists for upgrade, sync and remove > operations formatted as a table. Falls back to default list display if > insufficient terminal columns are available. > > Example output (-Su): > > Targets (25): > > Pkg Name  

Re: [pacman-dev] [PATCH 6/6] New VerbosePkgLists option

2011-02-26 Thread Ivan c00kiemon5ter Kanak
On 26 February 2011 13:46, Xavier Chantry wrote: > On Mon, Feb 21, 2011 at 8:02 PM, Jakob Gruber > wrote: > > If enabled, displays package lists for upgrade, sync and remove > > operations formatted as a table. Falls back to default list display if > > insufficient terminal columns are available

[pacman-dev] License for new contributions?

2011-02-26 Thread edmeister46
Hello pacman team! I've been following development for quite some time, and would like to submit my package signing patches for review. However, since some of the files are entirely new, they would have a license header. I would like to know under what license should I release my work. I brin

Re: [pacman-dev] License for new contributions?

2011-02-26 Thread Xavier Chantry
On Sat, Feb 26, 2011 at 6:42 PM, wrote: > Hello pacman team! > > I've been following development for quite some time, and would like > to submit my package signing patches for review. > Out of curiosity, what do these patches accomplish exactly ? > However, since some of the files are entirely

Re: [pacman-dev] Paralellising integrity checks

2011-02-26 Thread Tavian Barnes
On 25 February 2011 11:13, Dan McGee wrote: > On Sat, Feb 19, 2011 at 6:11 PM, Tavian Barnes > wrote: >> On a related note, I just tried running the test suite after entirely >> patching out integrity checks, and there weren't any regressions. >> Maybe the test suite should test the handling of c

Re: [pacman-dev] Paralellising integrity checks

2011-02-26 Thread Tavian Barnes
On 26 February 2011 18:56, Tavian Barnes wrote: > On 25 February 2011 11:13, Dan McGee wrote: >> * Downloads. I see a call to do this in parallel a lot and I will >> continue to think this is stupid, but maybe that is just me. If you >> can't find a mirror that saturates your connection, look aro

Re: [pacman-dev] Style questions and concerns

2011-02-26 Thread Tavian Barnes
On 25 February 2011 11:27, Dan McGee wrote: > I've noticed these things a lot in recent patches, so let the > discussion commence. > > 1) typedef-ed structs. This is just a "copy the rest of them" habit, > but I really feel we should stop doing this, only typedef-ing when we > are making a public-

[pacman-dev] Removing empty directories

2011-02-26 Thread Allan McRae
I just noticed this: > pacman -Qk | grep "^warning" warning: filesystem: /opt/ (No such file or directory) warning: hal: /usr/share/hal/fdi/information/20thirdparty/ (No such file or directory) warning: hal-info: /usr/share/hal/fdi/information/20thirdparty/ (No such file or directory) warning:

[pacman-dev] Namcap 3.0 coming soon

2011-02-26 Thread Rémy Oudompheng
Hello people, Namcap can still be found at the usual Git repository. I should release version 3.0 in a few days. Here are some highlights of what's new: * it works with Python 3.x (tested with Python 3.2) * it no longer outputs crazy contradicting messages about dependencies missing/unneeded a