On Thu, Oct 05, 2006 at 12:17:23PM -0500, Manoj Srivastava wrote:
A trivial patch would be:
Patch applied (thanks Raphael!), together with an added entry for the
Monotone VCS (I'm kinda scared by the amount of VCS produced by the free
software community in recent years )
Cheers.
--
Hi,
Coming back to what it would take to fully specify sources in
an arch archive so that users can download the sources, I think that
the best thing to use would be to provide a URL for a grab file. The
grab file has a syntax:
,
| Archive-Name: [the name of the archive]
|
On Thu, Oct 05, 2006 at 10:32:49AM -0500, Manoj Srivastava wrote:
I would also like to change the field name to XS-VCS-Arch
(tla is one implementation, baz is another, the VCS is called arch).
==
XS-VCS-Arch:
On Thu, 5 Oct 2006 17:49:29 +0200, Stefano Zacchiroli [EMAIL PROTECTED] said:
On Thu, Oct 05, 2006 at 10:32:49AM -0500, Manoj Srivastava wrote:
I would also like to change the field name to XS-VCS-Arch (tla is
one implementation, baz is another, the VCS is called arch).
On Thu, 2006-10-05 at 17:49 +0200, Stefano Zacchiroli wrote:
Ok, then please propose a patch for:
http://svn.debian.org/wsvn/qa/trunk/pts/www/bin/common.py?op=file
I think it would be quicker for you to propose it, than for me to
actually find out the pedigree of bzr wrt tla/arch/...
On Thu, Oct 05, 2006 at 12:17:23PM -0500, Manoj Srivastava wrote:
What more needs to be done? Would that not handle:
XS-VCS-Arch: http://people.debian.org/~srivasta/grab-flex
Nothing, it would be enough, I will forward it for inclusion in the PTS,
together with the addition of a couple of
On Sun, 24 Sep 2006 17:40:54 +1000, Robert Collins
[EMAIL PROTECTED] said:
config-manager supports reading a config straight out of the VCS:
http://arch.debian.org/arch/private/srivasta/archive-2003/dists--debian--0/flex/flex-2.5.31.config
But that would involve checking out the
On Tue, 2006-09-26 at 14:16 -0500, Manoj Srivastava wrote:
On Sun, 24 Sep 2006 17:40:54 +1000, Robert Collins
[EMAIL PROTECTED] said:
config-manager supports reading a config straight out of the VCS:
On Sat, 2006-09-23 at 04:21 -0500, Manoj Srivastava wrote:
URL's are not what would be needed.
The information that is required could possibly be couched
like so (RFC 2822 field folding) (for flex in stable)
,
| XS-VCS-ARCH-Repo: [EMAIL PROTECTED]
|
* Joey Hess:
To make a Vcs-Svn field work, dpkg-dev needs to be modified to recognise
that field. A simple modification but it would need to be done for all
the other ones for other RCSes, which could be a problem since there are
more and more of them. If we wanted to use a formalised field
On Sun, 24 Sep 2006 17:40:54 +1000, Robert Collins [EMAIL PROTECTED] said:
On Sat, 2006-09-23 at 04:21 -0500, Manoj Srivastava wrote:
URL's are not what would be needed.
The information that is required could possibly be couched like so
(RFC 2822 field folding) (for flex in stable) , |
On Sun, Sep 24, 2006 at 05:37:44PM -0500, Manoj Srivastava wrote:
URI's accept parameters:
http://arch.debian.org/arch/private/srivasta/archive-2003;gpg-keyid=0x40612c84/dists--debian--0/flex/flex-2.5.31.config
(again, this is a for instance).
That sounds good. Would this be an
On Fri, 22 Sep 2006 21:43:37 +0200, Stefano Zacchiroli [EMAIL PROTECTED]
said:
On Fri, Sep 22, 2006 at 02:21:22PM -0500, John Goerzen wrote:
I would also like to raise a question: does it make any sense to be
able to list two URLs, one for the Debian branch and one for the
upstream branch?
also sprach Manoj Srivastava [EMAIL PROTECTED] [2006.09.23.0936 +0200]:
Seems to me that this is fit for centralized single branch
repositories only -- at least, I fail to see how I can represent my
mlti-branch (no yet multi-repository) configs that need at least 3
different
Manoj Srivastava [EMAIL PROTECTED] writes:
XS-Vcs-XXX was in my mind a one-size-does-fit-all solution, assuming
the target of the information is a human. YMMV.
Seems to me that this is fit for centralized single branch
repositories only -- at least, I fail to see how I can represent
On Fri, Sep 22, 2006 at 08:25:13PM -0400, Joey Hess wrote:
file without the XS- prefix. Am I wrong? Request for help on this ...
snipped useful info about XS-
Vcs: svn svn://...
My preference is either the above or XS-Vcs-*
Thanks, my preference is now for XS-Vcs-*, it requires changes
On Sat, Sep 23, 2006 at 02:36:46AM -0500, Manoj Srivastava wrote:
Seems to me that this is fit for centralized single branch
repositories only -- at least, I fail to see how I can represent my
mlti-branch (no yet multi-repository) configs that need at least 3
different branches from
On Sat, 23 Sep 2006 09:58:39 +0200, martin f krafft [EMAIL PROTECTED] said:
also sprach Manoj Srivastava [EMAIL PROTECTED] [2006.09.23.0936
+0200]:
Seems to me that this is fit for centralized single branch
repositories only -- at least, I fail to see how I can represent my
mlti-branch (no
On Sat, 23 Sep 2006 10:20:15 +0200, Stefano Zacchiroli
[EMAIL PROTECTED] said:
Still I see your point, it can be that not all repository layouts
can be expressed with it. My point on this is still the same: where
do you use to commit patches to the packaging?
I commit changes to a
On Sat, Sep 23, 2006 at 04:21:21AM -0500, Manoj Srivastava wrote:
I commit changes to a local repo behind a couple of firewalls
that do not accept external connections.
That settles this. If your repo does not accept external connections,
your users have no point in knowing it exists.
On Sat, Sep 23, 2006 at 04:09:11AM -0500, Manoj Srivastava wrote:
The role of arch is to make life easier for me, the developer,
not to fit some arbitrary criteria like all projects must be
describable by a single URL. If you think lacking that characteristic
You are stretching the
On Sat, 23 Sep 2006 12:37:20 +0200, Stefano Zacchiroli [EMAIL PROTECTED]
said:
On Sat, Sep 23, 2006 at 04:09:11AM -0500, Manoj Srivastava wrote:
The role of arch is to make life easier for me, the developer, not
to fit some arbitrary criteria like all projects must be
describable by a
On Sat, 23 Sep 2006 12:33:18 +0200, Stefano Zacchiroli [EMAIL PROTECTED]
said:
On Sat, Sep 23, 2006 at 04:21:21AM -0500, Manoj Srivastava wrote:
I commit changes to a local repo behind a couple of firewalls that
do not accept external connections.
That settles this. If your repo does not
Stefano Zacchiroli wrote:
On Fri, Sep 22, 2006 at 08:25:13PM -0400, Joey Hess wrote:
file without the XS- prefix. Am I wrong? Request for help on this ...
snipped useful info about XS-
Vcs: svn svn://...
My preference is either the above or XS-Vcs-*
Thanks, my preference is now for
On Sat, Sep 23, 2006 at 12:02:00PM -0400, Joey Hess wrote:
Thanks, my preference is now for XS-Vcs-*, it requires changes which
only affect the code I'm able to change right now and it's nice looking.
I will send a new patch for the PTS and try to document it.
While the name is still in
also sprach Stefano Zacchiroli [EMAIL PROTECTED] [2006.09.23.2108 +0200]:
I don't like XS-Repo-* because Repo is neither an acronym nor
a full word. What about XS-Repository-*? I like it. But this
choice still leaves me puzzled about the name repository, is it
a significant name across
On Sat, 23 Sep 2006 21:08:55 +0200, Stefano Zacchiroli [EMAIL PROTECTED]
said:
On Sat, Sep 23, 2006 at 12:02:00PM -0400, Joey Hess wrote:
Thanks, my preference is now for XS-Vcs-*, it requires changes
which only affect the code I'm able to change right now and it's
nice looking. I will
Joey Hess [EMAIL PROTECTED] writes:
Stefano Zacchiroli wrote:
Thanks, my preference is now for XS-Vcs-*
While the name is still in flux, could I suggest XS-Repo-*?
I tend to get VCS and RCS confused :-)
On the other hand, repo is ambiguous and doesn't necessarily suggest
repository of a
On Sat, Sep 23, 2006 at 05:20:01PM -0500, Manoj Srivastava wrote:
Before we go on statndardizing it and writing coed to make
part of of infrastructure do stuff with it, can we have a clear idea
of the semantics of the field?
As I currently understand it, the format is
On Sun, Sep 24, 2006 at 01:42:25AM +0200, Stefano Zacchiroli wrote:
The proposed meaning is: a URL meaningful for the given VCS so that a
user seeing it is able to find the source code.
Sorry, I should have said more on this. That was the original intended
meaning (to me), listening to Joey
On Fri, Sep 22, 2006 at 11:17:56AM -0500, John Goerzen wrote:
This is an *excellent* idea, but a terrible way of introducing it. Why
was it posted only on a blog, and not to -- at least -- debian-devel?
I'm growing increasingly annoyed with things that are announced only on
blogs and not on
On Fri, Sep 22, 2006 at 06:39:35PM +0200, Stefano Zacchiroli wrote:
On Fri, Sep 22, 2006 at 11:17:56AM -0500, John Goerzen wrote:
This is an *excellent* idea, but a terrible way of introducing it. Why
was it posted only on a blog, and not to -- at least -- debian-devel?
I'm growing
* Stefano Zacchiroli:
As an answer specific for this case. The field is still an X- field,
because I actually don't know how and if it should be standardized.
If you use the X- prefix and the field gains widespread acceptance, a
transition is needed. Debian might be able to do this in a
On Fri, Sep 22, 2006 at 12:55:01PM -0500, John Goerzen wrote:
I hadn't even thought about the reference. That's indeed a good way to
go, but the problem with doing that only is that existing developers
won't learn about it very quickly.
I wasn't really sure that this might be of *that*
On Fri, Sep 22, 2006 at 08:46:51PM +0200, Florian Weimer wrote:
If you use the X- prefix and the field gains widespread acceptance, a
transition is needed.
Not really, being the PTS the only piece of software considering the
field it would be enough to document the non X- version and support
On Fri, Sep 22, 2006 at 09:02:31PM +0200, Stefano Zacchiroli wrote:
My doubt was on the line: who am I to suggest a non X- field to be
added to Sources files? If no one has objections on the field
XS-Vcs-XXX-Url I will add support for it and document its usage (without
the X-.
So, poll
On Fri, Sep 22, 2006 at 02:21:22PM -0500, John Goerzen wrote:
I would also like to raise a question: does it make any sense to be able
to list two URLs, one for the Debian branch and one for the upstream
branch?
I've thought about similar issues. I made up my mind about these
questions being
As far as using this field for svn repos, I assume that it should be to
an anonymous-friendly version of the repo if possible (svn:// not
svn+ssh://). Should it link to the trunk, rather than the head of the
repo? I think so and that's how your example gives it.
As to it being an XS- field,
On Fri, Sep 22, 2006 at 09:43:37PM +0200, Stefano Zacchiroli wrote:
On Fri, Sep 22, 2006 at 02:21:22PM -0500, John Goerzen wrote:
I would also like to raise a question: does it make any sense to be able
to list two URLs, one for the Debian branch and one for the upstream
branch?
I've
On Fri, Sep 22, 2006 at 03:42:47PM -0500, John Goerzen wrote:
That doesn't work so well for heavily distributed systems such as darcs.
In darcs, every repo is a branch, and every branch is a repo. Every
repo represents exactly 1 branch. Of course, branching is cheap, so
creating repos is
On Fri, Sep 22, 2006 at 04:18:56PM -0400, Joey Hess wrote:
As far as using this field for svn repos, I assume that it should be to
an anonymous-friendly version of the repo if possible (svn:// not
svn+ssh://). Should it link to the trunk, rather than the head of the
repo? I think so and that's
Stefano Zacchiroli wrote:
As to it being an XS- field, dpkg-dev doesn't warn at all about building
packages with such a field (unlike an XB- field), so I don't really
care, although it seems it would be better to lose the XS- if possible.
Note that we were more discussing about losing the
On Sat, Sep 23, 2006 at 01:04:59AM +0200, Stefano Zacchiroli wrote:
I'm a casual user of distributed VCS (used sparingly hg and baz here),
but I don't see how this is related to the field as we are intending it.
But maybe it's just because I'm not that familiar with them, let me know
if this
43 matches
Mail list logo
