On Fri, Apr 08, 2005 at 03:35:17PM -0400, Sam Hartman wrote:
> 
> I hate to be a pain in the ass, but it is going to be very difficult
> for me to take a huge .diff.gz that applies all the debian patches.
> 
> That's hard to audit, hard to understand and not well documented.  I'm

Well documented? The diff is just a forward patch of the Debian patches, so 
I've basicly done:

1) take pam-0.78
2) apply the patch used for 0.76-22 to 1)
3) fix the rejects
4) build the package and fix the building issues. 

> happy to give you access to the repository so you can work on a branch
> and try to get things in shape, but you'll need to make reasonably
> small commits with good commit logs.

Ok. If you want to go that route is fine by me. My alioth login is the same 
as my Debian login btw. I will need to investigate subversion branches if 
you intend for me to create one, I'm familiar enough with CVS, but not that 
much with subversion (although I do contribute in some subversion repos at 
alioth, mainly d-i)

> I want to make it clear that I do appreciate the effort you've put in.
> However I think having pam work is critical and so I think we need to
> work on the package using good software engineering methodology.

Regardless of the changes at subversion, and to get wider testing, would 
you approve to an upload to _experimental_ of pam 0.78? (maybe with big red 
warnings labeling it as an untested release, even though it's in 
experimental). 

Also note that one of the reasons of such an unwildely patch is that the 
Debian sources are heavily patched. Actually, I really cannot understand 
why some of the improvements (like the manpages in debian/local/) have not 
been contributed back upstream. Some Debian fixes seem to have found their 
way back upstream, but there are still a number of deviations...

I've also looked up at the patches produced by Mandrake, RedHat and SuSE to 
PAM 0.78 and I'm wondering if it would be worthwhile to review these and 
add them to the Debian shipped version too...

Regards

Javier

Attachment: signature.asc
Description: Digital signature

Reply via email to