Hi Jonathan, could you please clarify the request?

Directory /usr/include is already created&owned by filesystem package. I don't think filesystem package should own /usr/include/d (even if it will result in owning /usr/include/d by both llvm and gcc). Is there any reason for owning this directory by filesystem package?

the reason it is :
 - both ldc / gdc take include  file from  /usr/include/d

If an user use only ldc and gdc own /usr/include/d they are an extra dependency

same in other way


If an user use only gdc and ldc own /usr/include/d they are an extra dependency

then it seem the better way that is to set file-system as owner, no ?

ldc-2-29.20120921git8968103.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/ldc-2-29.20120921git8968103.fc17

Package ldc-2-29.20120921git8968103.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ldc-2-29.20120921git8968103.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-14865/ldc-2-29.20120921git8968103.fc17
then log in and leave karma (feedback).

If both packages own the directory, I don't see any reason for additional unnecessary dependency. You'll simply have one of the packages installed and that's just fine - if you'll have two of them, two of the packages will own the directory.
Note: There are already many directories under /usr/share which are owned by multiple packages. 

Reason for filesystem inclusion is usually:
1) Many common packages will need to own this directory (because they put/use files in it)
2) Directory needs to be on place even if the packages which should normally own it are not installed (e.g. common plugins place/initscripts directory)