We have a continuous integration machine that builds everyday. Instead of
downloading same packages from centos each day, we copy 5.5 rpms on a local web
server and build uses that server. In fact, this is one of the alternatives
that build system supplies.
By doing this, I did not notice that we are using a snapshot of centos in the
first place. Do they update 5.5 branch when they make any enhancements ? I
suppose that they freeze as is in a branch. Do they change the content under
5.5 for example ?
So we are not trying to get a mirror in fact. Just do not want to do same
downloads each day.
_lvnd_
{^_^}
On 13 Haz 2011, at 12:23, Douglas Hubler <[email protected]> wrote:
> On Sat, Jun 11, 2011 at 2:35 PM, Levend Sayar <[email protected]> wrote:
>> Hi, all.
>>
>> There is a commit due to deprecation of centos 5.5. All url related to
>> centos moved from 5.5 to 5 in the build scripts.
>> We are using a local web server instead of downloading each time from
>> centos during the build.
>> For this 5.5 to 5 change, we just made a link in the folder
>> /var/www/html/centos/5.5 where we serve centos rpms
>> like
>>
>> ln -s 5.5 5
>>
>> So we are using rpms from 5.5 but build thinks it is 5.
>>
>> This cause a problem or we have to download 5 from centos and use them ?
>
> Making a copy of CentOS on any random day and picking that version as
> your "standard version" may seem like a good idea, but you're only
> cutting your product off from security updates. Why are you making a
> copy of centos 5.5?
>
> You may be going down this path which i point out the issues with
> http://article.gmane.org/gmane.comp.telephony.pbx.sipfoundry.general/34371
>
> Now if you want to maintain a mirror of CentOS and is updated to
> upstream on a automatic basis, so you systems will have a reliable
> source of RPMs, that is a different story. Is that what you want?
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
