In any case, most of the packages are already in repo. In case of 
foreign repo - we need to change paths every time when package is moved 
on the server into other place, and in case of server failure/package 
deletion we'll have a headache.

02.06.2012 15:24, Erich Titl ???????:
> on 02.06.2012 12:46, Andrew wrote:
>> Hi.
>> Yes, I think that it should be placed into localrepo - we have almost
>> all in localrepo, except some packages.
> I don't know about you guys, but I believe this is highly redundant and
> one of the reasons of this unnatural blow up of big global datacenters
> which use quite a big portion of global energy and IMHO plain wrong as
> it forces us to keep our source up to date all the time.
>
> If a product is not maintained anymore and we feel it is necessary to
> have it in our repository then we should take responsabilitiy for it and
> not just make another copy.
>
> My 0.02
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> leaf-devel mailing list
> leaf-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-devel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to