Issue 42 in flvmeta: man/1/flvmeta.1 is not included in distribution tarball

[flv...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement

New issue 42 by neo.neut...@gmail.com: man/1/flvmeta.1 is not included in
distribution tarball
http://code.google.com/p/flvmeta/issues/detail?id=42

During the preparation of the new DEB, I found that the new committed
manpage is not included in the distribution tarball.

Therefore, I have prepared a simple patch to fixes this issue.

Please review.

PS: Please update the AUTHOR, COPYRIGHT, CONTACT in the manpage.

Best regards,
Neutron Soutmun

Attachments:
0001-Includes-manpage-in-distribution-tarball.patch 567 bytes

[flv...@googlecode.com]

Comment #1 on issue 42 by marc.noi...@gmail.com: man/1/flvmeta.1 is not

included in distribution tarball
http://code.google.com/p/flvmeta/issues/detail?id=42

Hi,
Could you tell me exactly which release you are using ?

The 1/flvmeta.1 path has changed recently and I have moved the files
directly to `man' in order to simplify the build process.

At first, I basically applied something close to your patch there:
https://github.com/noirotm/flvmeta/commit/d92860cd5945a0940da69151f9399d4afbc520c5#man/Makefile.am

And then completely changed the build approach by having the man page built
from the markdown source using pandoc, which means it must be added as a
build-time dependancy, as seen there :
https://github.com/noirotm/flvmeta/commit/01b5fd68adce15ddb8048f54eb40ff2895fad0f0#man/Makefile.am.

It must be noted that pandoc is being searched in the configure.ac file,
and the man page is only built if pandoc is present, no error being
generated if the tool is not present.

I am currently focusing on Github as the reference repository. The
googlecode git is merely a mirror, as I think the authentication process
here is quite annoying. I will sync it to the latest version anyways.

I'm also wondering whether the Autotools build system is the only one
officially sanctioned by the Debian project, since I'm pondering stopping
supporting autotools altogether in favour of CMake, which I feel does a
better job, is quite easier to maintain, and is much more Windows friendly.

If you want to discuss this with me, I'm usually online on #flvmeta on
irc.freenode.net.

[flv...@googlecode.com]

Comment #2 on issue 42 by neo.neut...@gmail.com: man/1/flvmeta.1 is not

included in distribution tarball
http://code.google.com/p/flvmeta/issues/detail?id=42

> Could you tell me exactly which release you are using ?

I track git remote with the url https://code.google.com/p/flvmeta/

> I am currently focusing on Github as the reference repository. The
> googlecode git
> is merely a mirror, as I think the authentication process here is quite
> annoying.
> I will sync it to the latest version anyways.

OK, I'll track the Github for the latest changes.

Do you plan to release the tarball at github or still release here
(googlecode) ?
The current debian watch file is tracking the
http://code.google.com/p/flvmeta/downloads/list?can=1 for the new release
which I could track from the Debian Package Tracking System (PTS).

> I'm also wondering whether the Autotools build system is the only one
> officially
> sanctioned by the Debian project, since I'm pondering stopping supporting
> autotools altogether in favour of CMake, which I feel does a better job,
> is quite
> easier to maintain, and is much more Windows friendly.

Don't worry, I think, I could change the build system to CMake in the next
DEB upload as you prefer. The debian package should be build in the way
that the upstream and the package maintainers could maintain together. :)

[flv...@googlecode.com]

Updates:
Status: Accepted
Owner: marc.noi...@gmail.com
Labels: Priority-Critical Milestone-1.2

Comment #3 on issue 42 by marc.noi...@gmail.com: man/1/flvmeta.1 is not

included in distribution tarball
http://code.google.com/p/flvmeta/issues/detail?id=42

Hi,

I'm working on finishing the man file to reach a releasable state.

You can still use the current url to track new releases without worry, I'll
be using download features from both sites.

My plan for the build system is to keep autotools for the current branch,
currently 1.1, but that will be released as stable version 1.2.0 and enter
a stable maintenance cycle as 1.2.x.

The next instable development branch will be 1.3.x, for which I will drop
autotools. I believe the whole ./configure && make && make install thing
makes less sense these days, since most distributions now have binary
packages and with the support of Debian, many popular derivatives will have
flvmeta packages de-facto.
I know that among others, FLVmeta has been packaged for Archlinux, FreeBSD,
and NetBSD, and other platforms are likely to support CMake, therefore I'm
confident this is a right decision in the long term.

Regards,
Marc

[flv...@googlecode.com]

Updates:
Status: Fixed
Labels: -Milestone-1.2 Milestone-1.1

Comment #4 on issue 42 by marc.noi...@gmail.com: man/1/flvmeta.1 is not

included in distribution tarball
http://code.google.com/p/flvmeta/issues/detail?id=42

Documentation is ready in 1.1.0 release.

[flv...@googlecode.com]

Updates:
Status: Verified

Comment #5 on issue 42 by marc.noi...@gmail.com: man/1/flvmeta.1 is not

included in distribution tarball
http://code.google.com/p/flvmeta/issues/detail?id=42

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings