Re: DA 1.7.1 is released

Mike Jackson wrote:

> Hi,
>  I just released 1.7.1 on the website. There is a source tarball, RPM,
> and SRPM available. This release contains official support for Samba
> 3, and Samba 2 will no longer work with DA. As well, there are some
> small fixes and additions.
>
>
>
> Changes:
>
>
> Version 1.7.1 - release date 2005-08-04
> * Richard Bullington-McGuire <[email protected]>
>     - removed reference to test.c
>     - corrected segmentation violation in appfunctions.c
> * Mike Jackson <[email protected]>
>     - added PADL schema for netscape password policies
>     - added PADL schema for hostObject and authorizedServiceObject
>       so that DA will work with OpenLDAP 2.2->
>     - added an OpenLDAP -> Fedora DS schema file converter in the schema
>       directory
>
> Version 1.7 - release date 2005-02-27
> * Changed to support the Samba v3.0 schema
> * Added support for changing passwords via the LDAP_EXOP_MODIFY_PASSWD
>   extended operation
> * Various fixes to error handling
> * Added support for mailLocalAddress mail aliases
> * Added support for the Windows well known system groups
>
>
>
>
>  Please test and report bugs.
>
> -- 
> mike
>
I noticed that you forgot to change configure.in
("AM_INIT_AUTOMAKE(directory_administrator, 1.7)") to 1.7.1, so I did
that :)
I also, took the liberty of splitting out the debug stuff from my LDAPS
patch and port it to 1.7.1. I'm working on porting the LDAPS changes to
1.7.1 (it seems the .glade file changed so I'll have to take a look at
what changed there before I cam add the gui part of the LDAPS hack, so
the LDAPS patch will take a little longer).
I also converted "a few" g_print's to DBG_PRINT_DM's, I'd like to hear
some feedback on if I got them all or too many.
Don't forget to read the README.BRANCH.
I'd recomend these steps on a copy of the 1.7.1 trunk:
-----------------
cd /the/dir
bzcat /path/to/1.7.1-debug_patch.diff.bz2 | patch -p0
# it will wine about md5.[ch], don't what happened but it's somehow
getting upset about $Id$ having been expanded - no idea why it whines
since the diffs from esvn doesn't show that :/

# make the tools executeable, lest make will fail when trying to run
svnrev.sh
# ***AND*** remember to change config_* to match your machine!!!
chmod +x tools/*
sh tools/automess.sh && sh tools/config_debug && make
# then run ./src/directory_administrator
# if you want to see how it behaves when --enable-debug is omitted and
optimizations turned on
# run: sh tools/config_rc && make clean all && directory_administrator
----------
The difference should be "a few lines of debugging code in the console".

I've introduced a "build X" in addition to the version (only showed and
used in "debug mode"), this X is simply the HEAD-reversion, it tries to
get it from "svn log -q", if that fails it tries .svn_lastlog, and if
that fails it set's the svnrev.h's defines to "N/A" or -1 (depending on
'type'). Give that the official "builds" and source released (which must
include the .svn_lastlog) will be fetched from the officail svn tree the
build number will tell us what revision the sources are (hence  it's
possible to keep track of changes between version/build A and B - I
thinkmaybe the "DEBUG main[main.c:44]: Starting Directory Administrator
v. 1.7.1 (build 164)" should be a pure g_print and thus be printed
(witout the 'DEBUG main[main.c:44]: ' which comes from the
preprocessor/macro) not only when debug stuff is compiled in, (also, I
admit I think it's a little c00l to have a build number :P)).
(note-of-no-greater-importance: the reversion number comes from my local
svn tree, which is a bit more messy than the official :)

and as a side note, I've run the "tools/sanitize.sh" with "my"
preferences on the sources (not just does it reduce the file sizes
(sanitize shows the delta), but also, imo, improves readabillity), so it
might be a little hard to see all the "real" changes (mainly g_print ->
DBG_PRINT_DM). You can run sanitize.sh on the trunk first and then diff
it to see the "real" changes if you want to see them.

...and this time I remembered the CREDITS file ;)

Cheers
Fredrik

-- 
After all, if you are in school to study computer science, then a
professor saying: 
 "use this proprietary software to learn computer science" is the
same as English professor handing you a copy of Shakespeare
and saying:
 "use this book to learn Shakespeare without opening the book itself."
  -- Bradley Kuhn