Date: Tue, 25 Oct 2016 12:13:14 +0300 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r424563 - in head/multimedia: . multicat Message-ID: <20161025091313.GA60716@hades.panopticon> In-Reply-To: <20161024134615.iwac7m4t6ka3eii7@ivaldir.etoilebsd.net> References: <201610241234.u9OCYZ7h016246@repo.freebsd.org> <20161024134615.iwac7m4t6ka3eii7@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Baptiste Daroussin (bapt@FreeBSD.org) wrote: > > Author: amdmi3 > > Date: Mon Oct 24 12:34:35 2016 > > New Revision: 424563 > > URL: https://svnweb.freebsd.org/changeset/ports/424563 > > > > Log: > > - Add multimedia/multicat > > > > multicat is a 1 input/1 output application. Inputs and outputs can > > be network streams (unicast and multicast), files, directories, > > character devices or FIFOs. It is thought to be a multicast equivalent > > of the popular netcat tool. Typical applications are recording live > > transport streams, or playing out TS files without modification. > > Also it is able to record a continuous stream into a directory, > > rotate the files periodically, and make seamless extracts from it. > > > > Multicat tries to rebuild the internal clock of the input stream; > > but it wants to remain agnostic of what is transported, so in case > > of files the said clock is stored to an auxiliary file (example.aux > > accompanies example.ts) while recording. Other inputs are considered > > "live", and the input clock is simply derived from the reception > > time of the packets. > > > > WWW: http://www.videolan.org/projects/multicat.html > > > > Added: > > head/multimedia/multicat/ > > head/multimedia/multicat/Makefile (contents, props changed) > > head/multimedia/multicat/distinfo (contents, props changed) > > head/multimedia/multicat/pkg-descr (contents, props changed) > > Modified: > > head/multimedia/Makefile > > > > Modified: head/multimedia/Makefile > > ============================================================================== > > --- head/multimedia/Makefile Mon Oct 24 12:26:26 2016 (r424562) > > +++ head/multimedia/Makefile Mon Oct 24 12:34:35 2016 (r424563) > > @@ -267,6 +267,7 @@ > > SUBDIR += msdl > > SUBDIR += msopenh264 > > SUBDIR += msx264 > > + SUBDIR += multicat > > SUBDIR += mxflib > > SUBDIR += mythtv > > SUBDIR += mythtv-frontend > > > > Added: head/multimedia/multicat/Makefile > > ============================================================================== > > --- /dev/null 00:00:00 1970 (empty, because file is newly added) > > +++ head/multimedia/multicat/Makefile Mon Oct 24 12:34:35 2016 (r424563) > > @@ -0,0 +1,39 @@ > > +# Created by: Dmitry Marakasov <amdmi3@FreeBSD.org> > > +# $FreeBSD$ > > + > > +PORTNAME= multicat > > +PORTVERSION= git20161007 > > What a creative PORTVERSION, it is totally inconsistent with other version and > looks weird... > > Why not having chosen something more common? > > Like 0.s20161007 > > 0 meaning you do not have yet a 's20161007' s meaning snapshot? which is more > commonly used? I try to stick to meaningful versions, so if it's git snapshot, it's obvious to use git<date>. It's verbose, meaningful, it doesn't have any useless "0." components, it's compatible with switching to actual version (gitYYYYMMDD < 0.0.0 so whatever the version is, it won't require an epoch bump). I've used this in many ports already. Here, though, I could actually use something like 2.1.git20161007 as my git is based on multicat trunk past 2.1 and I've actually missed this. Though I hope to upstream my changes and update the port to e.g. 2.2. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161025091313.GA60716>