On Mon, Sep 19, 2005 at 09:11:52AM +0200, Pascal Bleser wrote:
I first will look into making RPM's according the rules, becauise now I just run checkinstall and be done with it. Works great for me, personally.
checkinstall is nice to track a package you're only using on your own box, but is definately not a way to build packages to send out into the wild.
I know. But for that it is extremely usefull. Not all programs will be available on a repo, no matter what. There will alwaqys be a reason some people compile their own stuff and then checkinstall comes in very handy.
So I guess the time will come soon for suser-houghi. ;-))
Every "suser" ("suse user", Richard's creation) is encouraged to run createreo over his personal RPM directory at home. You could make it a requirement. I mean I running `createrepo /usr/src/packages/RPMS/` is not THAT difficult. It already IS a requirement in my head, but I am a shepard. ;-))
Not necessarely. I provide apt, yast2 and redcarpet. No need to do createrepo ;) (yast2 with my own scripts around create_package_descr, and redcarpet with opencarpet)
OK. In an ideal world, everybody would just do the yast2 and be done with it. :-) What I wanted to say is that IF you are a repo-mainter (repo-er?) and just had RPM's as most SUSER-* have, doing a createrepo is not a real extra burden.
It's great to have YaST2 being able to use createrepo metadata, but that only counts for >= 10.0, and I intent to provide packages for 9.3, 9.2, 9.1, 9.0 for a while (well, at least 9.3 and 9.2). So unless Novell is willing to backport that to yast2 on those distributions, I'm still stuck ;)
Yes, you are and create_package_descr is much better then createrepo, so please do not change.
One of the first things we should put into place for that is a central mailing-list for all the 3rd party packagers, to at least try to coordinate what we provide and avoid double entries. There are still a lot of them, and there's barely any communication going on.
A specific mailing list for packaging and repo hosting should be a good idea. I am taking the two together, because what I understand is that they are very close related or at least will be. I also understand that I won't be welcome there. :-)
Unfortunately, especially the suse-people don't talk to us non-suse-people.
I am sure that will change once 10.0 is out.
Some RPMs suddenly pop up into SUSE's "extra" repositories (kde, gnome) although they have been provided by others already (e.g. my k3b and amarok packages). Well, nice, I could just remove mine, but they're not always actively maintained.
It would indeed be best to put these extra's on the future shared OSS repo server. Or the "Shared Oss Unified Repositories Community Enhancement". ;-) Would be a lot cleare to have a SPOC to point to. <snip>
We don't even know yet what those build servers will "look like". Sure we do: http://www.es.jamstec.go.jp/esc/eng/GC/b_photo/esc11.jpg
Maybe you'd want to read an RPM presentation I did some time ago at a LUG in Antwerpen: http://linux01.gwdg.de/~pbleser/files/presentations/rpm-packaging.pdf
Nice. Pity I could not be there. Had something else going on. Yes, sometime I DO have a life. Will look into that perhaps sometime in the future. houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html