On 2006-12-02 "Adam Cécile (Le_Vert)" <[EMAIL PROTECTED]> wrote: > audacious-dev can't depends on audacious because it will create a circular > dependency that woud render audacious unusable and audacious-plugins not > buildable.
Hello, I do not get that. Where is the loop? Currently I can install audacious without pulling in audacious-dev: | (SID)[EMAIL PROTECTED]:/# apt-get install audacious | Reading package lists... Done | Building dependency tree... Done [...] | The following NEW packages will be installed: | audacious audacious-plugins defoma fontconfig fontconfig-config libasound2 | libasyncns0 libatk1.0-0 libcairo2 libexpat1 libflac7 libfontconfig1 | libfreetype6 libglade2-0 libglib2.0-0 libgtk2.0-0 libgtk2.0-common libjpeg62 | libogg0 libpango1.0-0 libpango1.0-common libpng12-0 libpulse0 libsndfile1 | libtag1c2a libtagc0 libtiff4 libvorbis0a libvorbisfile3 libxcursor1 libxext6 | libxfixes3 libxft2 libxi6 libxinerama1 libxml2 libxrandr2 libxrender1 | ttf-dejavu [...] cu andreas PS: At a short glance shipping the shared library in the audacious *binary* package seems to be absolutely wrong *if* this is a regular public library. (Policy 8.2). -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken. (c) Jasper Ffforde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
