summaryrefslogtreecommitdiffstats
path: root/audio-players/audacious/DETAILS
blob: 1f16b1542dd17a624710118d3580176a9eddd8de (plain) (blame)
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
           SPELL=audacious
         VERSION=3.3.2
          SOURCE=${SPELL}-${VERSION}.tar.bz2
   SOURCE_URL[0]=http://distfiles.audacious-media-player.org/$SOURCE
      SOURCE_GPG="gurus.gpg:${SOURCE}.sig"
SOURCE_DIRECTORY=${BUILD_DIRECTORY}/${SPELL}-${VERSION}
        WEB_SITE="http://audacious-media-player.org"
      LICENSE[0]=GPL
         ENTERED=20070520
           SHORT="a fork of beep-media-player 0.9.7.1"
cat << EOF
From the audacious FAQ: Why did you fork beep-media-player?

First off, the fork has no political reasons, it is based entirely on
technical merit. It's based on a few issues:

    * BMP classic had a number of deficiencies relating to Unicode.  
    * BMP classic is no longer actively maintained by the development team.
    * We had our own ideas about how a player should be designed, which we
      wanted to try in a production environment.  
    * Beep lacked functionality that is useful for people who do streaming, 
      such as the songchange plugin from XMMS.

Therefore, a fork seemed most logical as a choice for accomplishing
our goals. The BMP team has done very good work, but their ideas for a
next-generation beep do not align with ours.
EOF