On Sat, Nov 22, 2008, Felipe Sateler wrote: > In the case of ffmpeg, where there are no released > tarballs, it would make sense to directly track the git repository (ie, the > upstream branch is a clone of upstream's master branch). In either > case, "upstream" releases should be tagged (eg, upstream/x.y.z~svn123 as > git-buildpackage tags them). The debian diff is not a diff against upstream's > tip, but against these tags.
Unless there's absolutely no generated files when disting ffmpeg, I prefer we don't do that and instead import tarballs in the git tree. I understand this is archaic, but all situations can be handled simply in this scheme, with a classical approach. When you try git pulling from upstream, you might end up with removed files reappearing from the tarball, or keeping generated data in git. > 2. The maintainer field should be set to... A real maintainer when there's an interested one -- when this happens people care more personally for the package -- and the team as uploader. The team as maintainer when nobody wants to take primary reponsability for a source. > 4. How to manage upstream sources? Import tarballs, stripped or not or both. -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
