app-emulation/vmware-workstation/ChangeLog


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65

# ChangeLog for app-emulation/vmware-workstation
# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
# $Header: /var/cvsroot/gentoo-x86/app-emulation/vmware-workstation/ChangeLog,v 1.3 2002/08/06 18:40:13 gerk Exp $

*vmware-workstation-3.1.1.1790 (2002/4/13)

  06 Aug 2002; Mark Guertin <gerk@gentoo.org> :
  Added -ppc -sparc -sparc64 to keywords

  13 Apr 2002; William McArthur <sandymac@gentoo.org> /etc/init.d/vmare:
  Rewrote the /etc/init.d/vmare script to not mangle error messages that aren't
  in an expected format. Added ~dev-lang/tcl-8.3.3 to the DEPEND line.

  11 Apr 2002; William McArthur <sandymac@gentoo.org> vmware-workstation-3.1.1.1790.ebuild:
  New version of VMware Workstation released. The ebuild was updated for this
  version. The Gentoo (/etc/init.d/vmware) init script was changed to capture
  the output from the VMware (/etc/vmware/init.d/vmware) script and prettify
  (Is that a word?) it's output to look more like the Gentoo boot output. Also,
  any error lines from the vmware init script are sent to the system logger to
  hopefully increase their chance of being noticed. I made an icon from the
  logo off of vmware.com for use in "start" type menus. It can be found in
  /opt/vmware/lib/icon/ .  If kde is in the USE var then menu items are
  automatically added for the user.

*vmware-workstation-3.0.0.1455-r1 (2002/2/20)

  20 Feb 2002; William McArthur <sandymac@gentoo.org> vmware-workstation-3.0.0.1455-r1.ebuild :

  If you had an existing vmware install there was a problem where the file 
  /etc/vmware/not_configured would have a mtime different from what was in the
  locations file. This is fixed by not having a mtime in the locations file for
  the not_configured file.

  At the end of the merge the new locations file is appended to the existing
  locations. This plus the above should solve any problems that people with
  manual vmware installs have.

  If the user was to merge vmware twice without running vmware-config.pl the
  rc#.d dirs in /etc/vmware/init.d/ would be remove despite config protection.
  To keep them around I added .keep files in each of them.
  
*vmware-workstation-3.0.0.1455 (2002/2/10)

  10 Feb 2002; William McArthur <sandymac@gentoo.org> vmware-workstation-3.0.0.1455.ebuild :

  I don't remember the details but the following was written:

  The ebuild bypassed the official install because it doesn't all a install
  prefix.  Basicly the files from the work dir are copyied to the image dir.

  DEBUG=true is set because the strip command line tool dumps core on the
  vmware executable and setting DEBUG will disable it.

  After the files have had their mtime updated we scan the image dir and collect
  the mtimes and add the info to the /etc/vmware/locations file. This file is
  used by vmware to track config choices and it is used in upgrading. By
  creating this file we make sure the vmware config tools work and I think you
  could do a non gentoo package install of vmware and it would work.

  The vmware-config tool insists on a set of init dirs named rc#.d so they are
  created in /etc/vmware/init.d/ . The other option was edit vmware-config.pl .

  VMWare needs some modules loaded so at boot an init script is run that is
  really just glue to start the init script supplied from vmware which is at
  /etc/vmware/init.d/vmware