| 1 |
First check and see if a newer version is available but masked. You can do |
| 2 |
|
| 3 |
ACCEPT_KEYWORDS="~x86" emerge -s ruby |
| 4 |
|
| 5 |
and see what you get. Disclaimer - DO NOT install it using the |
| 6 |
ACCEPT_KEYWORD! |
| 7 |
|
| 8 |
If a newer version is there then update the /etc/portage/package.keyword file. |
| 9 |
|
| 10 |
To contribute create an ebuild and submit it on bugzilla. First search |
| 11 |
bugzilla to see if it's already there. If Rail is maintained you might also |
| 12 |
contact the maintainer to see what his plans are. |
| 13 |
|
| 14 |
On Sunday 01 January 2006 15:18, William Gabriel wrote: |
| 15 |
> Hello and Happy New Year to everybody: |
| 16 |
> |
| 17 |
> I want to start this post off by stressing that I am not complaining, |
| 18 |
> but merely inquiring. |
| 19 |
> |
| 20 |
> I have recently become interested in learning Ruby and Ruby on Rails. |
| 21 |
> I installed Ruby onto my system using Portage, and it happened to be |
| 22 |
> the version (1.8.2) required for Rails. |
| 23 |
> |
| 24 |
> |
| 25 |
> My main question has to do with about how Portage gets updated. Is |
| 26 |
> there some central authority that updates the repository, or is it any |
| 27 |
> user that is interested in making a Portage package? How often does |
| 28 |
> software get updated (it seems like Ruby was pretty close to |
| 29 |
> up-to-date, but Rails was a little behind). |
| 30 |
> |
| 31 |
> Is there any way that I can help update the package? Is there |
| 32 |
> documentation for updating packages? And where would I find the |
| 33 |
> 0.13.1 package source so that I have a base to work with? And then |
| 34 |
> how wou submit the new package to the central repository? |
| 35 |
> |
| 36 |
> Thanks, |
| 37 |
> Bill |
| 38 |
|
| 39 |
-- |
| 40 |
|
| 41 |
Brett I. Holcomb |
| 42 |
-- |
| 43 |
gentoo-user@g.o mailing list |
Archives