Gentoo Binary Packages repository

Like I heard many people saying, I really like [gentoo](http://gentoo.org) very much but sometimes I just one this package real quick. For that, a Binary Packages Repository (BPR) would be quite appreciated. There was the [Chinstrap Project](http://chinstrap.alternating.net/) that unfortunately being abandoned. I think it is very sad such a project is abandoned. There is also [klik](http://klik.atekon.de/) which actually is VERY GOOD, but aimed for (cross-distrib) desktop use, not as a core system solution. I think gentoo needs something on its own to his image. There has been [discussion](http://groups.google.com/group/linux.gentoo.user/browse_thread/thread/24cc78b55f6b97e0/fbe226112b28a5ee?lnk=st&q=gentoo+binary+repository&rnum=1#fbe226112b28a5ee) about it before, and apparently the problem with binary distribution is that it breaks and needs to be reinstalled. My personal problem with Binary package distribution just as Mandrake or SuSE is package availability. some and few packages that I want are not available. and/or you need to manage a list of download sources, which is a pain in the butt. Then it finally comes down to compiling it from source except that it won't be registered in your system database. which I don't like. I want everything and every-file to be registered, removable and manageable. That is why I like gentoo. every single packages are there. even proprietary stuff like [CrossOver](http://www.codeweavers.com/). The Gentoo portage won't be able to download it, because its paid software. but if you download it, put the file in your distfiles directory. it will check the digest and record this package into your system package database. THAT is GOOOOD. What I am thinking is having emerge being modified to upload packages after the compilation is done. so everyone in the world would be uploading package unless already found, in which case it would have got downloaded. So If found, download, if not, compile and upload. In order to keep system stability, I'm not sure how many duplicates of the packages we should need to store. I would be thinking.... http://gentoo.packages.example.com/gentoo/[arch]/[CHOST]/[gcc version]/[glibc version]/[package group]/[package name]/[package version]/file that might become crazy, but it might be what it needs. even USE flags might have to be thrown in there. I'm not sure how would be best to organize the use flags. but one way which would not be human browsable but flexible would be to assign a unique bit-flag to every USE flags. just like filesystem permission, where r-x becomes 5 the total would become a huge number but it would not matter I think. so it might become something like http://gentoo.packages.example.com/gentoo/x86/i686-pc-linux-gnu/gcc4.1.1/glibc2.4/kde-base/kdebase/3.5.5/kdebase-3.5.5.gentoo-bin.tgz that would required a lot of space and bandwidth I would guess, but I think its worth the try. problems can be fix in time. opinion?

Tags , , , ,

Posted in , , | Posted on 11 Oct 2006 19:37by somekool |

Comments

  1. Paul B Says
    I think it's a great idea, though one that would take a lot of work. Rather than modifying emerge, I'd say wrap it in another program which does the checking, and if it's not there, calls emerge --buildpkg On the server side, there'd need to be a tool that checked different versions of the tar file (if there were more than one version) for files that are exactly the same, and pulls those files out into a separate tar file for storage efficiency purposes. Using this method, each download would consist of a "base" file, which contains the portions of a certain package that is the same between all packages, and the portion that is different. These two tar files could then be combined into the one package file to be installed. The other advantage of this is that when upgrading a package, you'd only have to download the files that are different from the version you already have installed, then apply the changes to the package you already have (or make a package from your install, if you've removed the tarball already) and apply the changes there). Another way to avoid having to store too many different versions of packages, is to give the person requesting a package the package that matches *at least* the USE flags they have selected, but that could also have some other use flags selected.
  2. AkiRoss Says
    Hi! I know that 3 years has passed, but I've got the same idea and wrote something about it - and today I found out that someone have this feelings, too! If you're still interested: http://blog.ale-re.net/2008/09/gentoo-binary-repository-network.html Bye :)
  3. Jesse Taylor Says
    This was actually one of the major reasons for my own move away from Gentoo and into Debian-based systems. Not being able to quickly grab a binary of certain packages that I didn't need to fiddle with compiling was a real time-sink for me. I love the ability to compile my own packages when I need the optimization, but I can't stand having to sit there for a few minutes waiting for emacs to compile. Hopefully, an official binary repo will be created as some point for Gentoo. Until then ...
  4. linux Says
    I think this is one of the most important information for me. And i'm glad reading your article. But wanna remark on few general things, The website style is great, the articles is really excellent. Good job, cheers
  5. Watch Thunderstruck Online Says
    I've been surfing online more than 3 hours today, yet I never found any interesting article like yours. It's pretty worth enough for me. In my view, if all website owners and bloggers made good content as you did, the internet will be much more useful than ever before.

Subscribe

my last twitter posts

Personal Links

Tags

Categories

Archives

my Xbox 360 gamertag

Copyright © Mathieu Jobin's Life and Thoughts