RF vs GITHUB and ports trouble

[Philip M. Gollucci]

On 1/12/2010 3:18 AM, Stanislav Sedov wrote:
> This was discussed several times already[1].
> While certainly valuable, it is impossible
> to do due to several reasons.  The main ones:
> 1) Inability to check checksums of files
>    downloaded.  Are you going to calculate
>    the hash from the each file in the repo?
> 2) Inability to save distfiles. This also means
>    that there will be no mirrors.
> 3) These ports will be much more vulnerable
>    to failures due to breakages/changes in
>    the repo, etc. This problem will be also
>    amplified by the lack of FreeBSD mirrors
>    due to 2).
I don't disagree, I still think we should be able to come up with
something to address those points.  But thats another day.

> I don't think it poses a problem for the
> maintainer to create the snapshot from a github
> repo, as it can be done automatically by a simple
> script.  If he has no space to host the file,
> he can also ask to put it onto FreeBSD servers
> in PR he submits.  We had this practice for a
> long time.  As the additional benefit this
> will also guarantee, that the maintainer 
> performed at least minimum visual check of
> changes, and this was not a blind version
> bump as always happens.
It would then be quite useful for one us [possibly me] to create such a
script in put it in Mk/bsd*.mk or in Tools/ that works generically for
all 'github' ports starting with www/rubygem-rails and www/rubygem-hoe.



-- 
------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci at p6m7g8.com) c: 703.336.9354
VP Apache Infrastructure; Member, Apache Software Foundation
Committer,                        FreeBSD Foundation
Sr. System Admin,                 Ridecharge Inc.
Consultant,                       P6M7G8 Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.