Gabor Grothendieck
2008-Oct-04 15:58 UTC
[Rd] Attributes of top level environments clobbered (was Re: [R] possible bug in function 'var' in R 2.7.2?)
On Sat, Oct 4, 2008 at 10:45 AM, laurent <lgautier at gmail.com> wrote:> > On Sat, 2008-10-04 at 12:00 +0200, r-devel-request at r-project.org wrote: >> Message: 18 >> Date: Fri, 3 Oct 2008 15:35:18 -0500 (CDT) >> From: Luke Tierney <luke at stat.uiowa.edu> >> Subject: Re: [Rd] Attributes of top level environments clobbered (was >> Re: [R] possible bug in function 'var' in R 2.7.2?) >> To: Gabor Grothendieck <ggrothendieck at gmail.com> >> Cc: "r-devel at r-project.org" <r-devel at r-project.org>, Martin Maechler >> <maechler at stat.math.ethz.ch> >> Message-ID: <Pine.LNX.4.64.0810031433350.14866 at itasca2.wildberry.org> >> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed >> >> On Fri, 3 Oct 2008, Gabor Grothendieck wrote: >> >> > On Fri, Oct 3, 2008 at 12:46 PM, Luke Tierney <luke at stat.uiowa.edu> wrote: >> >> On Fri, 3 Oct 2008, Gabor Grothendieck wrote: >> >> >> >>> On Fri, Oct 3, 2008 at 11:43 AM, Luke Tierney <luke at stat.uiowa.edu> wrote: >> >>>> > [...] >> > I do appreciate the excellent R software; however, there are a few points like >> > those addressed on the proto home page which do need to be addressed in R >> > for it to be fully functional. >> >> There are some interesting poins on that page that are worth looking >> into. Over time I suspect all but the current 3. will be addressed, >> but 3., which is a variant on the unclass issue, is not likely to be. >> You can call this a deficiency in R if you like, and I would agree in >> the sense that I think it is inappropriate to allow attributes to be >> set but not in a reliable way because they can be inadvertenly >> removed. We should have done this differently. THere were/are two >> choices: >> >> Make reference values, including environments, special in that they >> may not have attributes. This woud have been fairly easy (modulo one >> use made in decorating the frames on the search path) and could be >> done now to clean things up. >> >> Make R-visible environments in two parts--a wrapper that is passed by >> value like standard R objects and could have attributes, and an >> internal part that is essentially the current environment object. >> This is analogous to the way that character vectors, even of length 1, >> consist of an STRSXP wrapper containing CHARSXPs that hold the string. >> The STRSXP's are visible at the R level, the CHARSXPs are not. This >> would have been messier to implement, and unfortunately would be very >> messy to retro-fit at this point, so it isn't likely to happen unless >> there is some other compelling reason to do so. > > Couldn't the two options be merged into one for a start ? > > - Make reference values either attribute-free entities (seems important, > as the "poor reliability" of assigning attributes to environment is > probably not widely known), or generate warnings upon assignment of > attributes.Some specifics need to be added to the "poor reliability" phrase relating to of attributed environments. The proto package changes the class attribute of environments (but no other attribute of environments) and proto in turn underlies large widely used packages which likely exercise it thoroughly yet through this experience the only places where this was noticeable were points #1 and #3 of the Avoiding R Bugs section of the proto home page at http://r-proto.googlecode.com Neither of these are two points are deal breakers as - #1 has an easy workaround (just change one line in your DESCRIPTION file) and if the promised fix is made even this won't be necesary, - #3 mostly seems mostly harmless in the context of proto as the only attribute change is from a class of "enviornment" to c("proto", "environment"). Artificial examples can be constructed where this is a problem but substantial experience with it suggests that it is not a problem in practice. (The remaining R problems listed are all related to promises, not environments.)> > - Create an R-level class that contains an environment ("Environment" ?, > "envobj" ?) and implements an environment-like interface by delegation > (somehow like your option 2. above). > Gabor could certainly create his own class, but having this administered > at the R-core level would have the following potential benefits: > - Anyone with similar needs will think twice before starting to > implement his own solution. > - That one class can be moved to a lower level in the internals > (C-level, with a new given SEXPTYPE) if it proves a working solution, > and as time permits. > > Just a thought,Actually, I see the main benefit of this or other approach as providing the missing elements of S3 support to environments thereby potentially streamlining the implementation of every package that needs it (proto, tcltk, R.oo, ...) or more perhaps more accurately allowing tcltk and R.oo and other such packages to become as streamlined as proto already is. Each of these packages could then use inheritance rather than containment thereby leveraging the S3 OO facilities that one really expects R to provide. It would be important that the new class whose objects contain environments is sufficiently indistinguishable in terms of its methods from regular environments so that inheritance works transparently. I assume that if e is a new style environment then parent.env(e) can be an old style or new style environment and in a sense all the new style environments can be regarded as childen of the old style environment they contain. There is some question of what happens if parent.env(e) is deleted in the case that its a new style environment but its contained old style environment is not deleted. Is it left undefined or does it revert to the old style environment? Implementation and performance considerations may suggest how best to handle this. Using these three packages as example cases may help clarify the desired functionality here. Another possible approach would be to only have new style environments rather than both or possibly only expose new style environments to the user even if both existed. Some thought would be required to determine which was the most desirable.> > > > L. > > > >> The bottom line is that this situation isn't likely to change any time >> soon as far as I can see. If that means that for you R will not be >> "fully functional" then so be it. Attributes on environments are not >> reliable and hence it is a Bad Idea to try to use them. This is a >> feature of R as it is now, has been for a while, and will be for a >> while. If you write code for language X, you can write it for >> X-as-it-s or X-as-you-wish-it-to-be; but if you chose >> X-as-you-wish-it-to-be and find things don't work out it's hard to >> argue that the fault is with X. >> >> luke >> >> > >> >> >> >> luke >> >> >> >>> - if time is a problem perhaps the core group needs to add resources >> >>> to reasonably address the problems in R. Traditional economics >> >>> do not apply to an open source project. There is no monetary cost to >> >>> adding additional developers. >> >>>> >> >>>> luke >> >>>> >> >>>> On Fri, 3 Oct 2008, Gabor Grothendieck wrote: >> >>>> >> >>>>> On Fri, Oct 3, 2008 at 3:23 AM, Martin Maechler >> >>>>> <maechler at stat.math.ethz.ch> wrote: >> >>>>>> >> >>>>>> a much better (and much less error-prone) idea would be to install >> >>>>>> R 2.8.0 alpha even now. >> >>>>>> It will become 'beta' early next week. >> >>>>>> >> >>>>>> We are asking the R community to please install and use >> >>>>>> pre-release versions of R (if you can / are allowed to) >> >>>>>> at least from beta onwards, and report problems you see early on >> >>>>>> *before* the final release. >> >>>>> >> >>>>> The bug discussed in the following year-old post suggested that >> >>>>> the problem of clobbering attributes of top level environment objects >> >>>>> would be fixed for 2.7 but its still in R version 2.7.2 (2008-08-25)" >> >>>>> and also still in "R version 2.8.0 alpha (2008-10-01 r46589)" >> >>>>> >> >>>>> https://stat.ethz.ch/pipermail/r-devel/2007-October/047184.html >> >>>>> >> >>>>> The Avoiding R Bugs section of this page: >> >>>>> >> >>>>> http://r-proto.googlecode.com >> >>>>> >> >>>>> has more discussion as well as a list of some other R bugs. >> >>>>> >> >>>>> This can be tested by creating a package with these two files only: >> >>>>> >> >>>>> ---DESCRIPTION--- >> >>>>> Package: testlazy >> >>>>> Version: 1.0-0 >> >>>>> Date: 2008-10-03 >> >>>>> Title: Test lazy loading >> >>>>> Author: G Grothendieck >> >>>>> Maintainer: G Grothendieck <ggrothendieck at gmail.com> >> >>>>> Description: Test lazy loading with top level objects. >> >>>>> Depends: proto >> >>>>> LazyLoad: yes >> >>>>> License: GPL-2 >> >>>>> ---R/testlazy.R--- >> >>>>> TopLevel <- proto() >> >>>>> --- >> >>>>> >> >>>>> And then testing it: >> >>>>> >> >>>>> library(testlazy) >> >>>>> class(TopLevel) >> >>>>> >> >>>>> If its class is "environment" only then the class attribute was >> >>>>> stripped. >> >>>>> >> >>>>> ______________________________________________ >> >>>>> R-devel at r-project.org mailing list >> >>>>> https://stat.ethz.ch/mailman/listinfo/r-devel >> >>>>> >> >>>> >> >>>> -- >> >>>> Luke Tierney >> >>>> Chair, Statistics and Actuarial Science >> >>>> Ralph E. Wareham Professor of Mathematical Sciences >> >>>> University of Iowa Phone: 319-335-3386 >> >>>> Department of Statistics and Fax: 319-335-3017 >> >>>> Actuarial Science >> >>>> 241 Schaeffer Hall email: luke at stat.uiowa.edu >> >>>> Iowa City, IA 52242 WWW: http://www.stat.uiowa.edu >> >>>> >> >>> >> >> >> >> -- >> >> Luke Tierney >> >> Chair, Statistics and Actuarial Science >> >> Ralph E. Wareham Professor of Mathematical Sciences >> >> University of Iowa Phone: 319-335-3386 >> >> Department of Statistics and Fax: 319-335-3017 >> >> Actuarial Science >> >> 241 Schaeffer Hall email: luke at stat.uiowa.edu >> >> Iowa City, IA 52242 WWW: http://www.stat.uiowa.edu >> >> >> > >> >> -- >> Luke Tierney >> Chair, Statistics and Actuarial Science >> Ralph E. Wareham Professor of Mathematical Sciences >> University of Iowa Phone: 319-335-3386 >> Department of Statistics and Fax: 319-335-3017 >> Actuarial Science >> 241 Schaeffer Hall email: luke at stat.uiowa.edu >> Iowa City, IA 52242 WWW: http://www.stat.uiowa.edu >> >> >> >> ------------------------------ >> >> Message: 19 >> Date: Fri, 3 Oct 2008 14:49:17 -0700 >> From: Kasper Daniel Hansen <khansen at stat.berkeley.edu> >> Subject: Re: [Rd] Can DESCRIPTION Maintainer: field contain general >> URL instead of only email address? >> To: William Dunlap <wdunlap at tibco.com> >> Cc: R-devel at stat.math.ethz.ch >> Message-ID: <F5426BA5-BBBF-438E-AADC-DA62E2A2918B at stat.berkeley.edu> >> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes >> >> Why don't you just give a company email address? Remember this email >> address is to contact the maintainer. Contacting the maintainer is not >> only done in order to request support, it could be a copy right issue, >> code re-use request etc - although I do agree that most emails are >> probably support requests. >> >> Kasper >> >> On Oct 3, 2008, at 11:01 , William Dunlap wrote: >> >> > Our firm would like to route support requests through >> > a website instead of using email. However R will refuse >> > to install a package if DESCRIPTION's Maintainer field >> > does not have a valid email adress or the special value >> > "ORPHANED". (The check is done with >> > tools:::.valid_maintainer_field_regexp.) >> > >> > I imagine a typical Maintainer line for the package "foo" >> > might be something like >> > Maintainer: Amalgamated Widget's Support Team >> > <http://support.amalgamatedwidgets.com/spackage?name=foo> >> > >> > How much does the package system (or CRAN) depend on >> > the Maintainer field being an email address? I can imagine >> > programs would find mailing to an address easier than >> > dealing with a website, but humans would have a better experience >> > with a well designed website. Perhaps we could add an optional >> > %s field to the website so a program could post a small message. >> > >> > Bill Dunlap >> > TIBCO Spotfire Inc. >> > wdunlap tibco.com >> > >> > ______________________________________________ >> > R-devel at r-project.org mailing list >> > https://stat.ethz.ch/mailman/listinfo/r-devel >> >> >> >> ------------------------------ >> >> Message: 20 >> Date: Fri, 3 Oct 2008 22:40:35 +0000 >> From: Shantanu Unknown <shantanu9847 at hotmail.com> >> Subject: [Rd] Unable to install R on CentOS 64 bit machine >> To: <r-devel at r-project.org> >> Message-ID: <BAY133-W27E5EFD8BD4F6EE0FCAE05D73C0 at phx.gbl> >> Content-Type: text/plain; charset="iso-8859-1" >> >> >> Hi all, >> I am unable to install R on CentOS5 64 bit machine. >> >> When I do ./configure >> I get the message >> >> "checking for X... no >> configure: error: --with-x=yes (default) and X11 headers/libs are not available" >> >> from doing a websearch it seems I need to install x11-xorg. But I could not find it when I did a yum install. >> >> I did "yum list xorg-x11*" and following is what I get >> Could someone tell me which is the missing X11 package I need to install for CentOS5? >> Thanks a lot for any help. >> Shantanu >> >> Installed Packages >> xorg-x11-apps.x86_64 7.1-4.0.1.el5 installed >> xorg-x11-drivers.x86_64 7.1-4.1.el5 installed >> xorg-x11-drv-acecad.x86_64 1.1.0-2.1 installed >> xorg-x11-drv-aiptek.x86_64 1.0.1-2 installed >> xorg-x11-drv-ast.x86_64 0.81.0-3 installed >> xorg-x11-drv-ati.x86_64 6.6.3-3.13.el5 installed >> xorg-x11-drv-calcomp.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-cirrus.x86_64 1.1.0-2.fc6 installed >> xorg-x11-drv-citron.x86_64 2.2.0-1.1 installed >> xorg-x11-drv-digitaledge.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-dmc.x86_64 1.1.0-2 installed >> xorg-x11-drv-dummy.x86_64 0.2.0-2.1 installed >> xorg-x11-drv-dynapro.x86_64 1.1.0-2 installed >> xorg-x11-drv-elo2300.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-elographics.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-evdev.x86_64 1:1.0.0.5-3.el5 installed >> xorg-x11-drv-fbdev.x86_64 0.3.0-2 installed >> xorg-x11-drv-fpit.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-hyperpen.x86_64 1.1.0-2 installed >> xorg-x11-drv-i810.x86_64 1.6.5-9.13.el5 installed >> xorg-x11-drv-jamstudio.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-joystick.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-keyboard.x86_64 1.1.0-3 installed >> xorg-x11-drv-magellan.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-magictouch.x86_64 1.0.0.5-2.1 installed >> xorg-x11-drv-mga.x86_64 1.4.2-7.el5 installed >> xorg-x11-drv-microtouch.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-mouse.x86_64 1.1.1-1.1 installed >> xorg-x11-drv-mutouch.x86_64 1.1.0-2 installed >> xorg-x11-drv-nv.x86_64 2.1.6-6.el5 installed >> xorg-x11-drv-palmax.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-penmount.x86_64 1.1.0-2.1 installed >> xorg-x11-drv-s3.x86_64 0.4.1-2.1 installed >> xorg-x11-drv-s3virge.x86_64 1.9.1-2.1 installed >> xorg-x11-drv-savage.x86_64 2.1.1-5.fc6 installed >> xorg-x11-drv-siliconmotion.x86_64 1.4.1-2.1 installed >> xorg-x11-drv-sis.x86_64 0.9.1-7.1.el5 installed >> xorg-x11-drv-sisusb.x86_64 0.8.1-4.1 installed >> xorg-x11-drv-spaceorb.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-summa.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-tdfx.x86_64 1.2.1-3.1 installed >> xorg-x11-drv-tek4957.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-trident.x86_64 1.2.1-3.fc6 installed >> xorg-x11-drv-ur98.x86_64 1.1.0-1.1 installed >> xorg-x11-drv-vesa.x86_64 1.3.0-8.1.el5 installed >> xorg-x11-drv-vga.x86_64 4.1.0-2.1 installed >> xorg-x11-drv-via.x86_64 0.2.1-9 installed >> xorg-x11-drv-vmmouse.x86_64 12.4.0-2.1 installed >> xorg-x11-drv-vmware.x86_64 10.13.0-2.1 installed >> xorg-x11-drv-void.x86_64 1.1.0-3.1 installed >> xorg-x11-drv-voodoo.x86_64 1.1.0-3.1 installed >> xorg-x11-filesystem.noarch 7.1-2.fc6 installed >> xorg-x11-font-utils.x86_64 1:7.1-2 installed >> xorg-x11-fonts-100dpi.noarch 7.1-2.1.el5 installed >> xorg-x11-fonts-75dpi.noarch 7.1-2.1.el5 installed >> xorg-x11-fonts-ISO8859-1-100dpi.noarch 7.1-2.1.el5 installed >> xorg-x11-fonts-ISO8859-1-75dpi.noarch 7.1-2.1.el5 installed >> xorg-x11-fonts-Type1.noarch 7.1-2.1.el5 installed >> xorg-x11-fonts-base.noarch 7.1-2.1.el5 installed >> xorg-x11-fonts-misc.noarch 7.1-2.1.el5 installed >> xorg-x11-fonts-truetype.noarch 7.1-2.1.el5 installed >> xorg-x11-server-Xnest.x86_64 1.1.1-48.41.el5_2.1 installed >> xorg-x11-server-Xorg.x86_64 1.1.1-48.41.el5_2.1 installed >> xorg-x11-server-Xvfb.x86_64 1.1.1-48.41.el5_2.1 installed >> xorg-x11-server-utils.x86_64 7.1-4.fc6 installed >> xorg-x11-twm.x86_64 1:1.0.1-3.1 installed >> xorg-x11-utils.x86_64 7.1-2.fc6 installed >> xorg-x11-xauth.x86_64 1:1.0.1-2.1 installed >> xorg-x11-xfs.x86_64 1:1.0.2-4 installed >> xorg-x11-xinit.x86_64 1.0.2-15.el5 installed >> xorg-x11-xkb-utils.x86_64 1.0.2-2.1 installed >> Available Packages >> xorg-x11-drv-i810.i386 1.6.5-9.13.el5 base >> xorg-x11-drv-i810-devel.x86_64 1.6.5-9.13.el5 base >> xorg-x11-drv-i810-devel.i386 1.6.5-9.13.el5 base >> xorg-x11-drv-via.i386 0.2.1-9 base >> xorg-x11-drv-via-devel.i386 0.2.1-9 base >> xorg-x11-drv-via-devel.x86_64 0.2.1-9 base >> xorg-x11-fonts-ISO8859-14-100dpi.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-ISO8859-14-75dpi.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-ISO8859-15-100dpi.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-ISO8859-15-75dpi.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-ISO8859-2-100dpi.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-ISO8859-2-75dpi.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-ISO8859-9-100dpi.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-ISO8859-9-75dpi.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-cyrillic.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-ethiopic.noarch 7.1-2.1.el5 base >> xorg-x11-fonts-syriac.noarch 7.1-2.1.el5 base >> xorg-x11-proto-devel.x86_64 7.1-9.el5.centos base >> xorg-x11-proto-devel.i386 7.1-9.el5.centos base >> xorg-x11-resutils.x86_64 7.1-2.fc6 base >> xorg-x11-server-Xdmx.x86_64 1.1.1-48.41.el5_2.1 updates >> xorg-x11-server-Xephyr.x86_64 1.1.1-48.41.el5_2.1 updates >> xorg-x11-server-randr-source.x86_64 1.1.1-48.41.el5_2.1 updates >> xorg-x11-server-sdk.x86_64 1.1.1-48.41.el5_2.1 updates >> xorg-x11-util-macros.x86_64 1.0.2-4.fc6 base >> xorg-x11-xbitmaps.x86_64 1.0.1-4.1 base >> xorg-x11-xfs-utils.x86_64 1:1.0.2-4 base >> xorg-x11-xfwp.x86_64 1.0.1-3.1 base >> xorg-x11-xsm.x86_64 1.0.2-4.fc6 base >> xorg-x11-xtrans-devel.x86_64 1.0.1-1.1.fc6 base >> xorg-x11-xtrans-devel.i386 1.0.1-1.1.fc6 base >> _________________________________________________________________ >> >> of your life. >> >> >> >> ------------------------------ >> >> Message: 21 >> Date: Sat, 4 Oct 2008 08:16:28 +0100 (BST) >> From: Prof Brian Ripley <ripley at stats.ox.ac.uk> >> Subject: Re: [Rd] Unable to install R on CentOS 64 bit machine >> To: Shantanu Unknown <shantanu9847 at hotmail.com> >> Cc: r-devel at r-project.org >> Message-ID: >> <alpine.LFD.2.00.0810040813400.26585 at gannet.stats.ox.ac.uk> >> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed >> >> config.log will tell you what is missing. But most likely it is X11 >> headers/libraries in packages like libX11-devel and libXt-devel. (Note >> that the R-admin manual does tell you this.) >> >> Real names and proper signature blocks are preferred here. >> >> On Fri, 3 Oct 2008, Shantanu Unknown wrote: >> >> > >> > Hi all, >> > I am unable to install R on CentOS5 64 bit machine. >> > >> > When I do ./configure >> > I get the message >> > >> > "checking for X... no >> > configure: error: --with-x=yes (default) and X11 headers/libs are not available" >> > >> > from doing a websearch it seems I need to install x11-xorg. But I could not find it when I did a yum install. >> > >> > I did "yum list xorg-x11*" and following is what I get >> > Could someone tell me which is the missing X11 package I need to install for CentOS5? >> > Thanks a lot for any help. >> > Shantanu >> > >> > Installed Packages >> > xorg-x11-apps.x86_64 7.1-4.0.1.el5 installed >> > xorg-x11-drivers.x86_64 7.1-4.1.el5 installed >> > xorg-x11-drv-acecad.x86_64 1.1.0-2.1 installed >> > xorg-x11-drv-aiptek.x86_64 1.0.1-2 installed >> > xorg-x11-drv-ast.x86_64 0.81.0-3 installed >> > xorg-x11-drv-ati.x86_64 6.6.3-3.13.el5 installed >> > xorg-x11-drv-calcomp.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-cirrus.x86_64 1.1.0-2.fc6 installed >> > xorg-x11-drv-citron.x86_64 2.2.0-1.1 installed >> > xorg-x11-drv-digitaledge.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-dmc.x86_64 1.1.0-2 installed >> > xorg-x11-drv-dummy.x86_64 0.2.0-2.1 installed >> > xorg-x11-drv-dynapro.x86_64 1.1.0-2 installed >> > xorg-x11-drv-elo2300.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-elographics.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-evdev.x86_64 1:1.0.0.5-3.el5 installed >> > xorg-x11-drv-fbdev.x86_64 0.3.0-2 installed >> > xorg-x11-drv-fpit.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-hyperpen.x86_64 1.1.0-2 installed >> > xorg-x11-drv-i810.x86_64 1.6.5-9.13.el5 installed >> > xorg-x11-drv-jamstudio.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-joystick.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-keyboard.x86_64 1.1.0-3 installed >> > xorg-x11-drv-magellan.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-magictouch.x86_64 1.0.0.5-2.1 installed >> > xorg-x11-drv-mga.x86_64 1.4.2-7.el5 installed >> > xorg-x11-drv-microtouch.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-mouse.x86_64 1.1.1-1.1 installed >> > xorg-x11-drv-mutouch.x86_64 1.1.0-2 installed >> > xorg-x11-drv-nv.x86_64 2.1.6-6.el5 installed >> > xorg-x11-drv-palmax.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-penmount.x86_64 1.1.0-2.1 installed >> > xorg-x11-drv-s3.x86_64 0.4.1-2.1 installed >> > xorg-x11-drv-s3virge.x86_64 1.9.1-2.1 installed >> > xorg-x11-drv-savage.x86_64 2.1.1-5.fc6 installed >> > xorg-x11-drv-siliconmotion.x86_64 1.4.1-2.1 installed >> > xorg-x11-drv-sis.x86_64 0.9.1-7.1.el5 installed >> > xorg-x11-drv-sisusb.x86_64 0.8.1-4.1 installed >> > xorg-x11-drv-spaceorb.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-summa.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-tdfx.x86_64 1.2.1-3.1 installed >> > xorg-x11-drv-tek4957.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-trident.x86_64 1.2.1-3.fc6 installed >> > xorg-x11-drv-ur98.x86_64 1.1.0-1.1 installed >> > xorg-x11-drv-vesa.x86_64 1.3.0-8.1.el5 installed >> > xorg-x11-drv-vga.x86_64 4.1.0-2.1 installed >> > xorg-x11-drv-via.x86_64 0.2.1-9 installed >> > xorg-x11-drv-vmmouse.x86_64 12.4.0-2.1 installed >> > xorg-x11-drv-vmware.x86_64 10.13.0-2.1 installed >> > xorg-x11-drv-void.x86_64 1.1.0-3.1 installed >> > xorg-x11-drv-voodoo.x86_64 1.1.0-3.1 installed >> > xorg-x11-filesystem.noarch 7.1-2.fc6 installed >> > xorg-x11-font-utils.x86_64 1:7.1-2 installed >> > xorg-x11-fonts-100dpi.noarch 7.1-2.1.el5 installed >> > xorg-x11-fonts-75dpi.noarch 7.1-2.1.el5 installed >> > xorg-x11-fonts-ISO8859-1-100dpi.noarch 7.1-2.1.el5 installed >> > xorg-x11-fonts-ISO8859-1-75dpi.noarch 7.1-2.1.el5 installed >> > xorg-x11-fonts-Type1.noarch 7.1-2.1.el5 installed >> > xorg-x11-fonts-base.noarch 7.1-2.1.el5 installed >> > xorg-x11-fonts-misc.noarch 7.1-2.1.el5 installed >> > xorg-x11-fonts-truetype.noarch 7.1-2.1.el5 installed >> > xorg-x11-server-Xnest.x86_64 1.1.1-48.41.el5_2.1 installed >> > xorg-x11-server-Xorg.x86_64 1.1.1-48.41.el5_2.1 installed >> > xorg-x11-server-Xvfb.x86_64 1.1.1-48.41.el5_2.1 installed >> > xorg-x11-server-utils.x86_64 7.1-4.fc6 installed >> > xorg-x11-twm.x86_64 1:1.0.1-3.1 installed >> > xorg-x11-utils.x86_64 7.1-2.fc6 installed >> > xorg-x11-xauth.x86_64 1:1.0.1-2.1 installed >> > xorg-x11-xfs.x86_64 1:1.0.2-4 installed >> > xorg-x11-xinit.x86_64 1.0.2-15.el5 installed >> > xorg-x11-xkb-utils.x86_64 1.0.2-2.1 installed >> > Available Packages >> > xorg-x11-drv-i810.i386 1.6.5-9.13.el5 base >> > xorg-x11-drv-i810-devel.x86_64 1.6.5-9.13.el5 base >> > xorg-x11-drv-i810-devel.i386 1.6.5-9.13.el5 base >> > xorg-x11-drv-via.i386 0.2.1-9 base >> > xorg-x11-drv-via-devel.i386 0.2.1-9 base >> > xorg-x11-drv-via-devel.x86_64 0.2.1-9 base >> > xorg-x11-fonts-ISO8859-14-100dpi.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-ISO8859-14-75dpi.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-ISO8859-15-100dpi.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-ISO8859-15-75dpi.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-ISO8859-2-100dpi.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-ISO8859-2-75dpi.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-ISO8859-9-100dpi.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-ISO8859-9-75dpi.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-cyrillic.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-ethiopic.noarch 7.1-2.1.el5 base >> > xorg-x11-fonts-syriac.noarch 7.1-2.1.el5 base >> > xorg-x11-proto-devel.x86_64 7.1-9.el5.centos base >> > xorg-x11-proto-devel.i386 7.1-9.el5.centos base >> > xorg-x11-resutils.x86_64 7.1-2.fc6 base >> > xorg-x11-server-Xdmx.x86_64 1.1.1-48.41.el5_2.1 updates >> > xorg-x11-server-Xephyr.x86_64 1.1.1-48.41.el5_2.1 updates >> > xorg-x11-server-randr-source.x86_64 1.1.1-48.41.el5_2.1 updates >> > xorg-x11-server-sdk.x86_64 1.1.1-48.41.el5_2.1 updates >> > xorg-x11-util-macros.x86_64 1.0.2-4.fc6 base >> > xorg-x11-xbitmaps.x86_64 1.0.1-4.1 base >> > xorg-x11-xfs-utils.x86_64 1:1.0.2-4 base >> > xorg-x11-xfwp.x86_64 1.0.1-3.1 base >> > xorg-x11-xsm.x86_64 1.0.2-4.fc6 base >> > xorg-x11-xtrans-devel.x86_64 1.0.1-1.1.fc6 base >> > xorg-x11-xtrans-devel.i386 1.0.1-1.1.fc6 base >> > _________________________________________________________________ >> > >> > of your life. >> > >> > ______________________________________________ >> > R-devel at r-project.org mailing list >> > https://stat.ethz.ch/mailman/listinfo/r-devel >> > >> >> -- >> Brian D. Ripley, ripley at stats.ox.ac.uk >> Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ >> University of Oxford, Tel: +44 1865 272861 (self) >> 1 South Parks Road, +44 1865 272866 (PA) >> Oxford OX1 3TG, UK Fax: +44 1865 272595 >> >> >> >> ------------------------------ >> >> _______________________________________________ >> R-devel at r-project.org mailing list DIGESTED >> https://stat.ethz.ch/mailman/listinfo/r-devel >> >> >> End of R-devel Digest, Vol 68, Issue 4 >> ************************************** > >
Seemingly Similar Threads
Wisdom of the Ancients
