Re: [Fwd: Re: [gentoo-user] Gentoo Rules]
7v5w7go9ub0o wrote: > My concerns with this, other than my abilities, are: > 1. Showing proper respect to the guy who pioneered the effort to date, > and who may simply be out of town. (This disrespect would be alleviated > if there was an official policy encouraging "volunteer ebuilds".) It's not disrespectful, IMO, to do something that you don't see getting done. Especially since it's less work for another guy. I wouldn't worry about that point. > 2. He won't be there to proofread my work anyway, so therefor my ebuild > would still not get into the disribution. (This could be alleviated if > there was a "designated backup" for each package - someone who could > either temporarily fill, or accept a "volunteer ebuild", and move it > forward. This can happen. I've submitted ebuilds for backuppc-3.0.0, and so have many other people. In fact, the bug for it has several ebuilds that have been submitted but haven't made it into the official tree. I think that particular bug report might not be getting attention from the right people or something. That doesn't mean it isn't worth doing though, because people can still use the ebuild from the bug report. Ideally, a dev would see that, check it out for correctness, and add it to ~arch. Does anybody know how to call attention to a bug report that doesn't seem to have any devs paying attention to it? I think BackupPC is a fine product, and would like to see it in the tree for others to use. I'm using my own ebuild successfully, as are many of the fine folks who have contributed on that bug report. I'd just like my and others' efforts to be something that benefits more of the Gentoo community :) > 3. If a volunteer ebuild isn't proofread, it could contain a bug. (you > don't know me.) I don't think an ebuild would make it into the tree without being checked by a dev, and that's not what I am suggesting. I'm suggesting taking the burden of writing ebuilds off of the devs' shoulders so they can spend more of their time checking. Ebuilds for the majority of packages are pretty simple anyways, especially packages that just need a ./configure && make && make install, so getting a bad bug in the ebuild itself isn't going to be that hard to avoid. -- Randy Barlow http://electronsweatshop.com -- [EMAIL PROTECTED] mailing list
Re: [Fwd: Re: [gentoo-user] Gentoo Rules]
Randy Barlow wrote: 7v5w7go9ub0o wrote: OTOH, the good news is that a newbie like me can install an outdated package (e.g. Vidalia); resolve dependencies; uninstall the portage version; download and compile the current version from the developer. If you know how to do those things, learning how to make the ebuild that does it isn't that much more to do. Then, instead of just filing the bug report, you can submit an ebuild as a suggested fix with it and help out. Linux works best when the users take part in it! Fair enough! My concerns with this, other than my abilities, are: 1. Showing proper respect to the guy who pioneered the effort to date, and who may simply be out of town. (This disrespect would be alleviated if there was an official policy encouraging "volunteer ebuilds".) 2. He won't be there to proofread my work anyway, so therefor my ebuild would still not get into the disribution. (This could be alleviated if there was a "designated backup" for each package - someone who could either temporarily fill, or accept a "volunteer ebuild", and move it forward. It would also be nice if there was a single, "temporary homeless" list of ebuilds belonging to folks who will be out of town for a while - this would be a "one-stop" page to notify designated backup people, and others who could keep an eye on the distributions.) 3. If a volunteer ebuild isn't proofread, it could contain a bug. (you don't know me.) P.S. A good place to start in writing an e-build for a new version of a package is to use the ebuild for the old version ;) I'll do that; and I'll also look forward to the reply to b.n.'s request. -- [EMAIL PROTECTED] mailing list
Re: Documentation about ebuilds (was: [Fwd: Re: [gentoo-user] Gentoo Rules])
On Dec 14, 2007 6:15 PM, b.n. <[EMAIL PROTECTED]> wrote: > Randy Barlow ha scritto: > > 7v5w7go9ub0o wrote: > >> OTOH, the good news is that a newbie like me can install an outdated > >> package (e.g. Vidalia); resolve dependencies; uninstall the portage > >> version; download and compile the current version from the developer. > > > > If you know how to do those things, learning how to make the ebuild that > > does it isn't that much more to do. Then, instead of just filing the > > bug report, you can submit an ebuild as a suggested fix with it and help > > out. Linux works best when the users take part in it! > > > > P.S. A good place to start in writing an e-build for a new version of a > > package is to use the ebuild for the old version ;) > > Can someone link a good tutorial for writing ebuilds? > > I know, there is the official Gentoo documentation, but last time I > checked, I found it pretty technical and, even if holy bible as a > reference, doesn't seem friendly for people who want to start hacking > ebuilds. > > m. > -- > [EMAIL PROTECTED] mailing list > > Here is one place: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml Here is another one: http://devmanual.gentoo.org/ And yet another one: http://gentoo-wiki.com/HOWTO_Create_an_Updated_Ebuild Use the one you like best. I personally like the second one.
Re: Documentation about ebuilds (was: [Fwd: Re: [gentoo-user] Gentoo Rules])
Randy Barlow ha scritto: > 7v5w7go9ub0o wrote: >> OTOH, the good news is that a newbie like me can install an outdated >> package (e.g. Vidalia); resolve dependencies; uninstall the portage >> version; download and compile the current version from the developer. > > If you know how to do those things, learning how to make the ebuild that > does it isn't that much more to do. Then, instead of just filing the > bug report, you can submit an ebuild as a suggested fix with it and help > out. Linux works best when the users take part in it! > > P.S. A good place to start in writing an e-build for a new version of a > package is to use the ebuild for the old version ;) Can someone link a good tutorial for writing ebuilds? I know, there is the official Gentoo documentation, but last time I checked, I found it pretty technical and, even if holy bible as a reference, doesn't seem friendly for people who want to start hacking ebuilds. m. -- [EMAIL PROTECTED] mailing list
Re: [Fwd: Re: [gentoo-user] Gentoo Rules]
7v5w7go9ub0o wrote: > OTOH, the good news is that a newbie like me can install an outdated > package (e.g. Vidalia); resolve dependencies; uninstall the portage > version; download and compile the current version from the developer. If you know how to do those things, learning how to make the ebuild that does it isn't that much more to do. Then, instead of just filing the bug report, you can submit an ebuild as a suggested fix with it and help out. Linux works best when the users take part in it! P.S. A good place to start in writing an e-build for a new version of a package is to use the ebuild for the old version ;) -- Randy Barlow http://electronsweatshop.com -- [EMAIL PROTECTED] mailing list
[Fwd: Re: [gentoo-user] Gentoo Rules]
Volunteer to pick up part of the load, I guess - something that I, as a newbie, am reluctant to do - but I guess I will if filezilla continues to languish. There is indeed an issue; e.g. TOR, a popular desktop package, is a release behind; Vidalia, is two releases behind - one a security release. Probably this is the consequence of a busy maintainer, but you'd think someone would pick up the slack (and yes, I've already filed a bugzilla security report on Vidalia). OTOH, the good news is that a newbie like me can install an outdated package (e.g. Vidalia); resolve dependencies; uninstall the portage version; download and compile the current version from the developer. --- Begin Message --- > > Lately I've been shopping around for other distros as well as looking > > at *BSD. Gentoo development seems to have slowed way down and I like > > things being improved as quickly as possible. FreeBSD is supposed to > > be the closest relation, but even that won't do. I don't think there > > is anything as satisfying as Gentoo out there. The concept is second > > to none, the execution of that concept is fantastic, but it needs to > > keep moving forward. What is the next step? Or should we keep > > treading water? > > > > - Grant > > I love gentoo and can't settle for anything else. What can I do to > make sure development doesn't stop? Let me in on that. What can I do too? - Grant -- [EMAIL PROTECTED] mailing list --- End Message ---
