Bug 34292 - tarball still contains generated files
Summary: tarball still contains generated files
Status: RESOLVED FIXED
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: 1.4.x
Hardware: Other All
: medium minor
Assignee: Simon McVittie
QA Contact: John (J5) Palmieri
URL: http://git.collabora.co.uk/?p=user/sm...
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2011-02-15 05:13 UTC by Simon McVittie
Modified: 2011-02-17 08:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Remove references to dbus-md5, which hasn't been used for at least 8 years (21.13 KB, patch)
2011-02-15 05:14 UTC, Simon McVittie
Details | Splinter Review
Don't distribute dbus-arch-deps.h in the tarball (1.13 KB, patch)
2011-02-15 05:14 UTC, Simon McVittie
Details | Splinter Review
Don't distribute dbus-daemon.1 in the tarball (1.09 KB, patch)
2011-02-15 05:15 UTC, Simon McVittie
Details | Splinter Review

Description Simon McVittie 2011-02-15 05:13:46 UTC
dbus tarballs still contain a generated header and a generated man page, which will be produced by ./configure anyway.

The linked branch also removes dbus-md5, which hasn't been used for at least 8 years.
Comment 1 Simon McVittie 2011-02-15 05:14:26 UTC
Created attachment 43373 [details] [review]
Remove references to dbus-md5, which hasn't been used for at least 8 years
Comment 2 Simon McVittie 2011-02-15 05:14:46 UTC
Created attachment 43374 [details] [review]
Don't distribute dbus-arch-deps.h in the tarball

It's generated by configure and specific to a system, so there's no point.
Comment 3 Simon McVittie 2011-02-15 05:15:19 UTC
Created attachment 43375 [details] [review]
Don't distribute dbus-daemon.1 in the tarball

It's generated by configure.
    
Also use a more normal way to distribute man pages that are actually
source, and use man1_MANS rather than auto-detecting the section from
the man page, which is best-practice and slightly faster.

(Last patch for now; review would be appreciated.)
Comment 4 Colin Walters 2011-02-17 08:14:23 UTC
Comment on attachment 43373 [details] [review]
Remove references to dbus-md5, which hasn't been used for at least 8 years

Yay for deleting code.  Looks good!
Comment 5 Colin Walters 2011-02-17 08:16:51 UTC
Comment on attachment 43374 [details] [review]
Don't distribute dbus-arch-deps.h in the tarball

I wonder if there's any value in listing dbus-arch-deps.h in a _HEADERS variable at all now, but it should be harmless.

Looks good.
Comment 6 Simon McVittie 2011-02-17 08:20:04 UTC
(In reply to comment #4)
> (From update of attachment 43373 [details] [review])
> Yay for deleting code.  Looks good!

Applied, 1.4.4/1.5.0

(In reply to comment #5)
> (From update of attachment 43374 [details] [review])
> I wonder if there's any value in listing dbus-arch-deps.h in a _HEADERS
> variable at all now

Yes: files in [nodist_]dbusarchinclude_HEADERS are automatically installed in $(dbusarchincludedir) and we rely on that.

Applied, 1.4.4/1.5.0
Comment 7 Colin Walters 2011-02-17 08:20:09 UTC
Comment on attachment 43375 [details] [review]
Don't distribute dbus-daemon.1 in the tarball

Looks fine, though it's weird that in automake, man pages are not default disted; I had to look that up.  Maybe worth a comment in the source?
Comment 8 Simon McVittie 2011-02-17 08:32:43 UTC
(In reply to comment #7)
> (From update of attachment 43375 [details] [review])
> Looks fine, though it's weird that in automake, man pages are not default
> disted; I had to look that up.  Maybe worth a comment in the source?

Committed, with comments. The rationale is that they're often generated with docbook, help2man or (as we do for one of them) sed substitutions.

I note with amusement that the CMake build system contains a doclifter'd copy of the dbus-launch, etc. man pages in docbook fomat. I wonder whether it'd be worth moving to Docbook for the man pages in general... then we'd get free HTML for the website.

1.4.4/1.5.0


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.