Why doesn't svntogit/{community, packages} describe cloning (or download) of individual packages?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Why doesn't svntogit/{community, packages} describe cloning (or download) of individual packages?

David C. Rankin
All,

  After abs demise, I ran into needed to rebuild gtk2 with --enable-debug=yes
for a gtk.org bug report. Finding the packages from the normal package search
is simple, but when you are on svntogit -- the only helpful discussions are to
clone the entire repository, e.g.:

Clone
https://git.archlinux.org/svntogit/community.git
git://git.archlinux.org/svntogit/community.git
ssh://git.archlinux.org/srv/git/svntogit/community.git

  Nowhere are there options to download or clone the current repository (like
github) and nowhere is there a mention of 'asp export pkgname'. There is no
wiki for asp and the only mention is in the ABS page -- and that information
relates to the svn part of the tree.

  'asp export' works fine, but if there is nothing on the svntogit that
directs folks to it, the only information given is to 'Clone' as shown above.
(which will result in roughly 500M each for community and packages if the
instructions on the page are followed (compared to what was 88M total for abs).

  Can individual clone or download urls be provided on each package page like
with github? Can references to 'asp export' also be provided? Those seems like
things that should be done to help with the transition away from abs and help
preserve bandwidth.

--
David C. Rankin, J.D.,P.E.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Why doesn't svntogit/{community, packages} describe cloning (or download) of individual packages?

Thomas Bächler-3
Am 05.08.2017 um 07:15 schrieb David C. Rankin:

> All,
>
>   After abs demise, I ran into needed to rebuild gtk2 with --enable-debug=yes
> for a gtk.org bug report. Finding the packages from the normal package search
> is simple, but when you are on svntogit -- the only helpful discussions are to
> clone the entire repository, e.g.:
>
> Clone
> https://git.archlinux.org/svntogit/community.git
> git://git.archlinux.org/svntogit/community.git
> ssh://git.archlinux.org/srv/git/svntogit/community.git
>
>   Nowhere are there options to download or clone the current repository (like
> github) and nowhere is there a mention of 'asp export pkgname'. There is no
> wiki for asp and the only mention is in the ABS page -- and that information
> relates to the svn part of the tree.
>
>   'asp export' works fine, but if there is nothing on the svntogit that
> directs folks to it, the only information given is to 'Clone' as shown above.
> (which will result in roughly 500M each for community and packages if the
> instructions on the page are followed (compared to what was 88M total for abs).
>
>   Can individual clone or download urls be provided on each package page like
> with github? Can references to 'asp export' also be provided? Those seems like
> things that should be done to help with the transition away from abs and help
> preserve bandwidth.
>
git clone --branch packages/gtk2 --single-branch
https://git.archlinux.org/svntogit/packages.git gtk2

Regards
Thomas


signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Why doesn't svntogit/{community, packages} describe cloning (or download) of individual packages?

Eli Schwartz-2
In reply to this post by David C. Rankin
On 08/05/2017 01:15 AM, David C. Rankin wrote:

> All,
>
>   After abs demise, I ran into needed to rebuild gtk2 with --enable-debug=yes
> for a gtk.org bug report. Finding the packages from the normal package search
> is simple, but when you are on svntogit -- the only helpful discussions are to
> clone the entire repository, e.g.:
>
> Clone
> https://git.archlinux.org/svntogit/community.git
> git://git.archlinux.org/svntogit/community.git
> ssh://git.archlinux.org/srv/git/svntogit/community.git
>
>   Nowhere are there options to download or clone the current repository (like
> github) and nowhere is there a mention of 'asp export pkgname'. There is no
> wiki for asp and the only mention is in the ABS page -- and that information
> relates to the svn part of the tree.
>
>   'asp export' works fine, but if there is nothing on the svntogit that
> directs folks to it, the only information given is to 'Clone' as shown above.
> (which will result in roughly 500M each for community and packages if the
> instructions on the page are followed (compared to what was 88M total for abs).
>
>   Can individual clone or download urls be provided on each package page like
> with github? Can references to 'asp export' also be provided? Those seems like
> things that should be done to help with the transition away from abs and help
> preserve bandwidth.
Those *are* individual clone/download URLs. Because "community" and
"packages" are whole repositories, and indivual packages are implemented
as branches. And the download instructions are autogenerated by cgit,
the same way Github would autogenerate the same instructions.

It seems this is a good opportunity for you to share the knowledge you
just gained in order to further improve our Wiki. :)

--
Eli Schwartz


signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Why doesn't svntogit/{community, packages} describe cloning (or download) of individual packages?

beest
In reply to this post by David C. Rankin
On Sat, Aug 05, 2017 at 12:15:42AM -0500, David C. Rankin wrote:
>   Nowhere are there options to download or clone the current repository (like
> github) and nowhere is there a mention of 'asp export pkgname'. There is no
> wiki for asp and the only mention is in the ABS page -- and that information
> relates to the svn part of the tree.

Actually (aside from what you've already been told about the nature of
the repository and the opportunity to change the wiki), you could have
discovered this from the very same place you ostensibly learned about
the switch to asp -- from arch-announce, where 'asp export pkgname' is
currently plastered at the top of the archlinux.org feed. So not only is
there very much a mention of it, it's in exactly the one place we're
expected to monitor for distro changes.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Why doesn't svntogit/{community, packages} describe cloning (or download) of individual packages?

David C. Rankin
On 08/06/2017 12:32 PM, beest wrote:
> Actually (aside from what you've already been told about the nature of
> the repository and the opportunity to change the wiki), you could have
> discovered this from the very same place you ostensibly learned about
> the switch to asp -- from arch-announce, where 'asp export pkgname' is
> currently plastered at the top of the archlinux.org feed. So not only is
> there very much a mention of it, it's in exactly the one place we're
> expected to monitor for distro changes.

  You misunderstood the purpose of the post. The purpose of the post was to
explain "when you are sitting on the svntogit page for any package" there is
no reference to asp and no direction for cloning anything other than the full
community or packages repository.

  If your response is to chastise or belittle someone for making a suggested
improvement by reference to

"the very same place you ostensibly learned about the switch to asp -- ...
where 'asp exprot pkgname' is currently plastered at the top of the
archlinux.org feed."

Then that is a problem that directly discourages anyone from trying to help.

  There was nothing in my post discussing 'asp export pkgname' not being
available on the arch feed. The intent was to suggest it would be a useful
addition on the svntogit package pages. The feed will soon scroll away.

  If the Arch position is "we already listed 'asp export' on the main page",
that's fine. A simple, "we think the announcement was sufficient" is all that
was needed.

  It just appeared helpful to have that information or a convenient link for
download on the 'tree' or 'summary' views, rather than the summary page
suggesting a clone of the entire repository.


--
David C. Rankin, J.D.,P.E.
Loading...