Hi Reinhard, Yeah, I see. Thanks alot. So there are question:
Right not script get-orig-source is not actual, and do not make effective result. To "import" my version of script(which I actually use for import sources) I need to know next: what must be result of script execution ? "Fresh" source tree? "Fresh" source repacked tree ? With debian directory ? As tar(.gz) archive ? If this is described in some place, please point me the there. Also package not complete yet so there was no need to remove the binary package crtmpserver(from control) :) I'll finish this package for a few days. Also there is old question: in which way I can "release" "old" version with incremented minor version, if my "master" git-branch goes forward from old version? Make git brach and point tag to it ? On Mon, Oct 03, 2011 at 10:21:22AM +0200, Reinhard Tartler wrote: > > I noticed crtmpserver on PET hanging around, waiting for a reviewer and > I took a look at it. > > On Fr, Jul 29, 2011 at 15:04:17 (CEST), Andriy Beregovenko wrote: > > > Hi, > > > > On Thursday 28 July 2011 14:04:39 Alessio Treglia you wrote: > >> On Thu, Jul 28, 2011 at 8:25 AM, <jet-gu...@users.alioth.debian.org> > >> wrote: > >> > The following commit has been merged in the master branch: > >> > commit 589879437b6083106bb2ffa4a09ec6fff7cd5b0c > >> > Author: Andriy Beregovenko <j...@jet.kiev.ua> > >> > Date: Thu Jul 28 01:31:05 2011 +0300 > >> > > >> > Split package to 4 parts > >> > > >> > libs will install only basic libs (common and thelib) > >> > apps will install only applications > >> > main will install main binary, doc, examples, init script and basic > >> > configuration file > >> > >> \o/ > >> > >> What's the rationale? > > > > In fact, this software is the platform that consists of several components: > > - the main component library; > > - applications that use these libraries; > > - actually the main executable file / daemon and supported files like docs, > > configs etc... > > > > We can install only crtmpserver-libs and crtmpserver-dev and makes own > > software. > > Do you do this? Do you have any indication that there are users doing > this? I'm asking because I notice the libs are installed in a private > path, so this isn't directly accessible. Of course you can override this > with proper linker paths, but there is neither documentation nor helper > scripts/pkg-config files that would assist with that. > > Moreover, the package descriptions don't really explain what's going on, > so I have doubts that the split in the current form is helpful for the > users. > > I also note that the .orig.tar gz is an svn checkout. Please use 'svn > export' instead. > > For the next upload (the package is RC buggy atm, after all), what shall > we do? Shall we revert the fix, or do we want to keep it? > > Cheers, > Reinhard > > -- > Gruesse/greetings, > Reinhard Tartler, KeyID 945348A4 _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
