net-misc/directvnc/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

# ChangeLog for net-misc/directvnc
# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
# $Header: /var/cvsroot/gentoo-x86/net-misc/directvnc/ChangeLog,v 1.7 2002/12/09 04:33:15 manson Exp $

\* Autoupdate keywords (12-6-02)
  06 Dec 2002; Rodney Rees <manson@gentoo.org> changed sparc ~sparc keywords
 
*directvnc-0.7 (07 Nov 2002)

  07 Nov 2002; Seemant Kulleen <seemant@gentoo.org> directvnc-0.7.ebuild
  files/digest-directvnc-0.7 :

  Version bump, thanks to: andreh@lddd.org (Andre Heidemann) in bug #9521.

*directvnc-0.6.1 (06 Jul 2002)

  08 Aug 2002; Seemant Kulleen <seemant@gentoo.org> directvnc-0.6.1.ebuild :

  FHS compliance.

  06 Jul 2002; Seemant Kulleen <seemant@gentoo.org> directvnc-0.6.1.ebuild
  files/digest-directvnc-0.6.1 files/dfb.c :

  Version bump, and the dfb.c from directvnc's CVS, where the API changes
  for DirectFB since 0.9.10 have been implemented.  Now, this will compile
  against portage's version of DirectFB.

*directvnc-0.6-r1 (03 Jul 2002)

  03 Jul 2002; Grant Goodyear <g2boojum@gentoo.org> ChangeLog  :

  Fixed DirectFB dep to be ~0.9.10
# ChangeLog for net-misc/directvnc

*directvnc-0.6 (31 May 2002)

  31 May 2002; Grant Goodyear <g2boojum@gentoo.org> 
  New import.  Note that the stuff in src_unpack (and the automake/
  autoconf dependencies) should go away in the next release, since
  they're only there to fix the author's mistake.
 
-- Explanation of ChangeLog format:
 
  Every new version or revision of the package should be marked by a '*'
  seperator line as above. Changes since the last revision have to be added to
  the top of the file, underneath the initial copyright and cvs header
  comments, in exactly the same format as this comment.
  
  This means that you start with header line that has the following format,
  indented two spaces:
  
  DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
  explanation should follow. It should be indented and wrapped at a line width
  of 80 characters.  The changed_files can be omitted if they are obvious; for
  example, if you are only modifying the .ebuild file and committing a new rev
  of a package.  Any details about what exactly changed in the code should be
  added as a message when the changes are committed to cvs, not in this file.