FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › General Discussion › The case for reviving Firefly
- This topic has 135 replies, 48 voices, and was last updated 14 years, 5 months ago by blamm.
-
AuthorPosts
-
08/02/2010 at 1:24 AM #18746AnonymousInactive
Folks, seriously… This is really really simple. The fork is the future. http://git.debian.org/?p=users/jblache/forked-daapd.git
This is the only place where active development is happening, as far as I can tell. The fork supports Front Row, smart playlists, itunes library xml, >2GB movie files, bug fixes of all stripes, and soon full control with an iPhone Remote. Oh, and did I mention active development?
Project management and resources are a wonderful thing, to be sure. But what really counts is code.
10/02/2010 at 10:23 PM #18748blammParticipantHi Ace.
Is there a windows version of this fork?
ta
10/02/2010 at 11:35 PM #18749EVILRipperParticipantNope, there has been chosen for linux only.
11/02/2010 at 6:32 PM #18750blammParticipantSo not “really really simple” then 🙁
12/02/2010 at 1:12 AM #18751AnonymousInactiveI’ve been under the impression that in the FOSS world, “Linux only” attitude is the equivalent to the familiar “Windows only” thing that we all know and love passionately.
12/02/2010 at 4:37 AM #18752AnonymousInactiveI am not a programmer, but I went out on a limb and checked out the forked-daapd commits. The BSD user in me rejoiced. All hail, it is not Linux-only.
jblache, question: why keep separate code paths for inotify and kqueue, when you can have gamin to do the dirty work for you on both platforms? It uses inotify and dnotify on Linux and kqueue/kevent plus some extra magic for directory contents on FreeBSD, so it could simplify the code a bit and make it easier to port it. No?
17/02/2010 at 4:57 AM #18753AnonymousInactiveWell, for our friends running Windows, it seems to be the end of the line, unless someone is willing to pick it up. Not great news, but still simple 🙂
17/02/2010 at 1:12 PM #18754blammParticipantSo I guess our only option is to run Linux in a virtual machine if we want to use this fork. Is there a way of doing this using minimal resources? E.g. using Damn Small Linux?
22/02/2010 at 2:05 PM #18755jelockwoodParticipant@ace wrote:
Folks, seriously… This is really really simple. The fork is the future. http://git.debian.org/?p=users/jblache/forked-daapd.git
This is the only place where active development is happening, as far as I can tell. The fork supports Front Row, smart playlists, itunes library xml, >2GB movie files, bug fixes of all stripes, and soon full control with an iPhone Remote. Oh, and did I mention active development?
Project management and resources are a wonderful thing, to be sure. But what really counts is code.
As you probably know, the current (read old) Firefly is used as an embedded iTunes/DAAP server on many, many different NAS servers including the ReadyNAS from NetGear. The ReadyNAS like most NAS servers uses Linux as its operating system. Are there any plans to either package up forked-daapd yourselves for use on a ReadyNAS so mere users do not have to try compiling it themselves. Or perhaps contacting NetGear and getting them to switch from ‘ye olde’ Firefly to forked-daapd instead?
The following open-source links may be of interest/help –
http://www.flyn.org/projects/libdmapsharing/index.html
http://www.flyn.org/projects/dmapd/index.htmlAmongst other things they should allow serving iPhoto libraries as well as iTunes.
My goal is to be able to connect an Apple TV to a server – presumably forked-daapd running on a ReadyNAS.
23/02/2010 at 7:21 AM #18756RigasWParticipantWill the fork still run with my good old nslu2 slug?
Rigas
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.