Re: Vcs-Svn field and trunk
On Mon, Jun 01, 2009 at 09:09:48PM +0300, Fabian Fagerholm wrote:
If this is the consensus, should then Vcs-Browser point to trunk also?
Without having given it too much thought, I would suggest not. Instead
point it at the root of the repository.
Why? Vcs-* are meant to be in sync, with -Browser being the
human-friendly facet to inspect what is in the repo. I fail to see why
it should point elsewhere.
Meanwhile, it could be useful to have a field pointing explicitly to
trunk or equivalent and another to the repository root, to
facilitate automation.
I think you are considering a svn-biased point of view. The notion of
having the equivalent of the source package root in VCS I believe is
more or less equivalent throughout all VCSs. On the contrary, the
notion of having trunk/ and stuff like tags/ side by side to it is
svn-specific, isn't it?
So, even for automation, I consider pointing to the source package
root (i.e. what contains debian/) to be the better minimum requirement
addressable by all VCS.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Re: Vcs-Svn field and trunk
On Tue, 2009-06-02 at 09:13 +0200, Stefano Zacchiroli wrote: Why? Vcs-* are meant to be in sync, with -Browser being the human-friendly facet to inspect what is in the repo. I fail to see why it should point elsewhere. [...] I think you are considering a svn-biased point of view. The notion of having the equivalent of the source package root in VCS I believe is more or less equivalent throughout all VCSs. On the contrary, the notion of having trunk/ and stuff like tags/ side by side to it is svn-specific, isn't it? That's the case, yes. Actually the fact that svn treats everything (tags and branches, that is) as directories is quite unfortunate. So, even for automation, I consider pointing to the source package root (i.e. what contains debian/) to be the better minimum requirement addressable by all VCS. You're right. I had also completely forgotten that svn can easily determine the repository root if given any URL within that repository. This is useful if one wants to, say, analyse the entire repository. It will require a little bit more logic in any automation but it's still easy enough. I will now go change the packages I maintain to follow this convention and (again) consider switching away from svn. :) -- Fabian Fagerholm fa...@paniq.net signature.asc Description: This is a digitally signed message part
Vcs-Svn field and trunk
Recently I've ran into a few cases were doing debcheckout of a package using svn downloads the whole thing: tags, branches and trunk. I would expect debcheckout to give me just the HEAD of development. What should be the sane behavior? -- Felipe Sateler -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Vcs-Svn field and trunk
On Mon, Jun 1, 2009 at 2:04 PM, Felipe Sateler fsate...@gmail.com wrote: Recently I've ran into a few cases were doing debcheckout of a package using svn downloads the whole thing: tags, branches and trunk. I would expect debcheckout to give me just the HEAD of development. What should be the sane behavior? Checking out trunk sounds like reasonable behaviour, I guess file minor bugs when you encounter this issue. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Vcs-Svn field and trunk
On Mon, Jun 01, 2009 at 04:04:48PM +1000, Felipe Sateler wrote:
Recently I've ran into a few cases were doing debcheckout of a package using
svn downloads the whole thing: tags, branches and trunk. I would expect
debcheckout to give me just the HEAD of development. What should be the sane
behavior?
Should be somewhere where you can natually invoke a package build
command. Ideally, and for $VCS that contain injected upstream sources,
it should be the root of a debianized source tree, i.e. `pwd` should
contain debian/.
For SVN, Vcs-Svn should then point to trunk/ and not to the dir above
it.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Re: Vcs-Svn field and trunk
On Mon, 2009-06-01 at 08:18 +0200, Stefano Zacchiroli wrote: Should be somewhere where you can natually invoke a package build command. Ideally, and for $VCS that contain injected upstream sources, it should be the root of a debianized source tree, i.e. `pwd` should contain debian/. For SVN, Vcs-Svn should then point to trunk/ and not to the dir above it. If this is the consensus, should then Vcs-Browser point to trunk also? Without having given it too much thought, I would suggest not. Instead point it at the root of the repository. Meanwhile, it could be useful to have a field pointing explicitly to trunk or equivalent and another to the repository root, to facilitate automation. Cheers, -- Fabian Fagerholm fa...@paniq.net signature.asc Description: This is a digitally signed message part
