[ANN] Source code of all eggs as git repositories

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[ANN] Source code of all eggs as git repositories

Mario Domenech Goulart-4
Hi,

In the past we used to have the source code of all eggs under our
central subversion repository, from which users could conveniently check
out the source code of the whole set of eggs.

Nowadays we have the egg repositories distributed [1], which is
absolutely great for egg developers, as they can use whatever version
control system they want and still have their eggs available from the
official egg index.  On the other hand, the distribution nature makes it
a bit inconvenient for users to fetch the source code of all eggs.

To fill this gap, we are making available git repositories that contain
the source code of the whole set of eggs.  See [2] for more information
on how to clone them.

[1] http://wiki.call-cc.org/distributed-egg-repos
[2] http://wiki.call-cc.org/how-to-obtain-the-source-code-of-eggs#using-git

All the best.
Mario
--
http://parenteses.org/mario

Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Source code of all eggs as git repositories

chicken-users mailing list
Hi Mario,

Mario Domenech Goulart writes:
> To fill this gap, we are making available git repositories that contain
> the source code of the whole set of eggs.  See [2] for more information
> on how to clone them.

This is great!  Thank you.  This reminds me: one thing that I've always
wondered is whether it would be possible to add links directly from the
wiki.call-cc.org/eggref/* pages to the relevant repository.  This would
have helped me quite a bit in my early days of using Chicken, as I
remember being very confused about where to find the official repository
associated with any given package.

Cheers,
Tim


Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Source code of all eggs as git repositories

Ivan Raikov-2
Great idea, automatic links from the eggref page to the egg
repository/source would be very useful.
-Ivan

On Fri, Nov 1, 2019 at 5:43 AM plugd via <[hidden email]> wrote:

>
> Hi Mario,
>
> Mario Domenech Goulart writes:
> > To fill this gap, we are making available git repositories that contain
> > the source code of the whole set of eggs.  See [2] for more information
> > on how to clone them.
>
> This is great!  Thank you.  This reminds me: one thing that I've always
> wondered is whether it would be possible to add links directly from the
> wiki.call-cc.org/eggref/* pages to the relevant repository.  This would
> have helped me quite a bit in my early days of using Chicken, as I
> remember being very confused about where to find the official repository
> associated with any given package.
>
> Cheers,
> Tim
>
>

Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Source code of all eggs as git repositories

Mario Domenech Goulart-4
In reply to this post by chicken-users mailing list
Hi Tim,

On Fri, 01 Nov 2019 13:43:09 +0100 plugd via <[hidden email]> wrote:

> Mario Domenech Goulart writes:
>> To fill this gap, we are making available git repositories that contain
>> the source code of the whole set of eggs.  See [2] for more information
>> on how to clone them.
>
> This is great!  Thank you.  This reminds me: one thing that I've always
> wondered is whether it would be possible to add links directly from the
> wiki.call-cc.org/eggref/* pages to the relevant repository.  This would
> have helped me quite a bit in my early days of using Chicken, as I
> remember being very confused about where to find the official repository
> associated with any given package.

Thanks for the feedback.

Back when we had all eggs in svn, the information about the repository
where eggs could be found was a bit redundant, as all of them were in
the same repository.  Thus, this information was omitted from the egg
documentation pages.

Since we adopted the distributed approach, most eggs not hosted in svn
have a link to their repository in their respective wiki page.  Usually
when the documentation of eggs doesn't mention the repository, it's
because they are in svn.  Now that the distributed approach is the
recommented way to store eggs, I think the documentation of eggs stored
in svn should also include a link to their repostories.  Unfortunatelly,
I don't think there is an easy way to do that automatically.

All the best.
Mario
--
http://parenteses.org/mario