[pacman-dev] Frugalware changes merged.
aaronmgriffin at gmail.com
Sat Oct 21 17:32:29 EDT 2006
On 10/21/06, VMiklos <vmiklos at frugalware.org> wrote:
> 35. to be honest the problem is that this is an api change and we use
> already alpm in many places. an unnecessary recompile of all the
> packages should be avoided if possible. yes, i know that the answer now
> will be "we always said pacman3 is not yet ready, we said don't use it
> yet - now see, why can't you guys wait?" :)
> so it's up to you. currently such an api change for you is not a
> problem, for us it is
Ok, so here's what we'll do. I'll revert to using 1, for now... at a
later date I'd like to switch it to a higher number, just to prevent
some random conflicts... it's rather unimportant, but it's worthwhile.
Fixed in cvs.
> my first opensource project where i started hacking was MPlayer and
> there any patch that contained whitespace changes was rejected with a
> short "whitespace changes mixed with functional changes, rejected"
> message, so i'm used to do things this way. i'll try to stop blaming you
> because of your cosmetics ;)
Yeah, I've contributed to projects which said tabs were equally as
dumb. i.e. vim's scripts require :set et ts=8 sw=8:. In 99% of cases
it's up to the author. In this case, I'll let judd do a "coding
format" writeup and we can all use that. On a personal note, I prefer
:set et ts=4 sw=4: - I hate tabs, but that's a holy war I don't really
care to get into.
Personally, I could care less about whitespace, because i use vim. If
the modelines are proper, gg=G fixes any whitespace issues...
> > Yes I'm aware, I never said it was fixed - I said i was going to do it
> > when I had the time.
> ok and thank you for your fixes
Should be fixed now... at least it compiles and succeeds with all
pactests, and runs fine... I didn't really test it because I need to
head out in like 10 minutes, but it should be in CVS.
I'll work on this some when I get home in 5 hours or so...
More information about the pacman-dev