From: Nathan Scott <nscott@aconex.com>
To: xfs@oss.sgi.com
Subject: [PATCH] remove remaining unused-but-installed headers
Date: Wed, 28 Jan 2009 22:24:03 +1100 [thread overview]
Message-ID: <1233141843.4584.40.camel@verge.scott.net.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
Looks like Barry missed a few headers... or at least, I can't
find anything outside xfsprogs that uses these anymore. But,
no sane reason we should be installing these in /usr/include/
disk on everyone's systems - build can get 'em out of its own
include/ directory already.
cheers.
--
Nathan
[-- Attachment #2: disk.patch --]
[-- Type: text/x-patch, Size: 988 bytes --]
diff --git a/include/Makefile b/include/Makefile
index 0403536..07076cc 100644
--- a/include/Makefile
+++ b/include/Makefile
@@ -29,9 +29,9 @@ QAHFILES = libxfs.h libxlog.h \
xfs_imap.h xfs_inode.h xfs_inode_item.h xfs_inum.h \
xfs_log.h xfs_log_priv.h xfs_log_recover.h xfs_metadump.h \
xfs_mount.h xfs_quota.h xfs_rtalloc.h xfs_sb.h \
- xfs_trans.h xfs_trans_space.h xfs_types.h
+ xfs_trans.h xfs_trans_space.h xfs_types.h xfs_dfrag.h
-HFILES = handle.h jdm.h xqm.h xfs.h xfs_dfrag.h xfs_fs.h
+HFILES = handle.h jdm.h xqm.h xfs.h xfs_fs.h
HFILES += $(PKG_PLATFORM).h
PHFILES = darwin.h freebsd.h irix.h linux.h
DKHFILES = volume.h fstyp.h dvh.h
@@ -51,8 +51,6 @@ install-dev: default
$(INSTALL) -m 755 -d $(PKG_INC_DIR)
$(INSTALL) -m 644 $(HFILES) $(PKG_INC_DIR)
$(INSTALL) -m 644 platform_defs.h $(PKG_INC_DIR)
- $(INSTALL) -m 755 -d $(DK_INC_DIR)
- $(INSTALL) -m 644 $(DKHFILES) $(DK_INC_DIR)
install-qa: install-dev
$(INSTALL) -m 644 $(QAHFILES) $(PKG_INC_DIR)
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-01-28 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 11:24 Nathan Scott [this message]
2009-01-29 22:37 ` [PATCH] remove remaining unused-but-installed headers Christoph Hellwig
2009-01-29 22:39 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233141843.4584.40.camel@verge.scott.net.au \
--to=nscott@aconex.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox