After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 668218 - file names of directory pages easily change.
file names of directory pages easily change.
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.3
Other Linux
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-01-18 21:05 UTC by John Berendsen
Modified: 2012-02-25 15:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Berendsen 2012-01-18 21:05:39 UTC
The html files for directories (dir_$md5encode.html) apparently use the full path name to generate the md5 key.  With files under revision control and checked out by various users in different directories, the generated file names change per user.

Although I haven't tried the fix I'm proposing, I suspect that the problem can be corrected by using the existing Doxygen feature that finds the minimum file suffix that makes the name unique.  Feeding this minimally unique file name to the md5encode routine should produce stable dir_* file names.

I observed the problem on version 1.7.3, but looked at the code for the latest version (1.7.6) and it seems it has the same problem.

My config file has:

FULL_PATH_NAMES = YES
STRIP_FROM_PATH = ../src ../localLib

This keeps the relative directory structure of the documented code visible to the user.
Comment 1 Dimitri van Heesch 2012-02-18 15:59:18 UTC
Hi John,

You observation is correct. I'll make doxygen ignore the common prefix shared by all directories. 

This is more stable than the mimimum path to make the directory name unique, as this will change as soon as a new directory is added with the same name as one that was previously unique.
Comment 2 Dimitri van Heesch 2012-02-25 15:37:15 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.0. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.