Selon "Eric S. Raymond" <[EMAIL PROTECTED]>: > Wiith the NR merge coming up, I decided to give macroscope the > capability to find and detect cliques of duplicate files, so I > can drop redundant copies of images in NR. > > You can generate this report by going to data/tools and typing > > make collisions > > My code uses MD5 hashing rather than byte-by-byte comparison, so > this works pretty fast. > > Here's a copy of the current report. I deduce from this, for example, > that it ought to be possible to remove the file > data/campaigns/The_South_Guard/images/misc/cross.png. >
AFAIK there a few images where duplication is necessary. Thing like this : > ../../data/tutorial/images/units/elder-mage-ranged1.png > ../../data/campaigns/Heir_To_The_Throne/images/units/elder-mage-ranged1.png These are images for campaign-specific units. Mainline campaigns are expected to be packagable alone (just like user campaigns), without dependancies, that is why when a campaign-specific unit is used in more than one campaign, it is duplicated. And things like this : > ../../data/campaigns/Under_the_Burning_Suns/external_binary_data/images/UtBS_campaign_icon.png > ../../data/campaigns/Under_the_Burning_Suns/images/newelves/kaleh.png Campaign specific images are usually packaged inside a #ifdef to avoid to pollute content for other campaign, thus they are only available within the campaign. By the way, a few content like icons for the campaign selection must be shared (ie outside of the #ifdef), this is the purpose of that external_binary_data/images directory (through this path might be different is some campaigns). Often, this content is portait or unit frames thus is also found in the normal image directory. It is more convenient for scripts and artist to find all the graphics like frames and portaits in the same tree; that is the main reason why there is duplication in external_binary_data/ _______________________________________________ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev