blob: 02c74cb0f9cc4c2793ae082ae27aaab50fd36f92 (
plain)
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
|
# ChangeLog for media-plugins/xmms-nas
# Copyright 2002-2005 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/media-plugins/xmms-nas/ChangeLog,v 1.14 2005/04/24 03:00:51 hansmi Exp $
24 Apr 2005; Michael Hanselmann <hansmi@gentoo.org>
xmms-nas-0.2-r1.ebuild:
Stable on ppc.
22 Nov 2004; Jeremy Huddleston <eradicator@gentoo.org>
xmms-nas-0.2-r1.ebuild:
-sparc because it produces static noise.
22 Nov 2004; Jeremy Huddleston <eradicator@gentoo.org>
xmms-nas-0.2-r1.ebuild:
-sparc as it's producing static sound
16 Nov 2004; Jeremy Huddleston <eradicator@gentoo.org>
xmms-nas-0.2-r1.ebuild:
Don't generate a static lib.
Fix install into correct path.
14 Sep 2004; Jeremy Huddleston <eradicator@gentoo.org>
xmms-nas-0.2-r1.ebuild:
Stable amd64, sparc.
17 Jun 2004; Jeremy Huddleston <eradicator@gentoo.org>
xmms-nas-0.2-r1.ebuild:
gnuconfig update for ~amd64 addition.
21 Apr 2004; Jeremy Huddleston <eradicator@gentoo.org>
xmms-nas-0.2-r1.ebuild:
Removed explicit S=.
20 Apr 2004; Jeremy Huddleston <eradicator@gentoo.org>
xmms-nas-0.2-r1.ebuild:
Added IUSE.
10 Apr 2004; Jeremy Huddleston <eradicator@gentoo.org>
xmms-nas-0.2-r1.ebuild:
Works on sparc.
18 Feb 2003; Jon Nall <nall@gentoo.org> xmms-nas-0.2-r1.ebuild :
marking as ~ppc. it seems any endian issues were on the nas end.
this works fine with nas-1.6
Nov 28 2002; Mark Guertin <gerk@gentoo.org> xmms-nas-0.2-r1.ebuild:
set -ppc in keywords, outputs nothing but static, seems like
might be endianess issues
*xmms-nas-0.2-r1 (1 Feb 2002)
30 Aug 2002; Seemant Kulleen <seemant@gentoo.org> * :
Relocated to media-plugins.
1 Feb 2002; G.Bevin <gbevin@gentoo.org> ChangeLog :
Added initial ChangeLog which should be updated whenever the package is
updated in any way. This changelog is targetted to users. This means that the
comments should well explained and written in clean English. The details about
writing correct changelogs are explained in the skel.ChangeLog file which you
can find in the root directory of the portage repository.
|