Re: File_CSV as standalone package?

Zitat von Stefan Neufeind <stefan@neufeind.net>: > On 30 Aug 2003 at 4:19, Marshall Roch wrote: > > > Stefan Neufeind wrote: > [...] > > > But since File is marked as "stable" I guess we can't remove CSV > > > from File. The only solution to me seems a dependency from File to > > > File_CSV? > > > > Yes, but we could make it optional, and you'd only *have* to install > > it if you're using it, which it doesn't sound like many people are. A > > short note (but longer than the one that mentions CSV in the package > > description!) in the documentation and the changelog might be enough. > > Oh yes, got a wrong assumption here. I assumed that File.php does an > include on File_CSV.php (which is unlogical now that I think about it > and have a look at File.php). Then we would maybe have broken > compatibility. But since we only would move File_CSV to a separate > package and dir-locations remain the same there shouldn't be a > problem with BC. But there is. Documention for applications that depend on File_CSV tell users to install the File package. The only way to not break BC is to copy the File_CSV class to a new package and maintain it there while keeping the current state of this class in the File package. > By the way: What if you install File_CSV and afterwards upgrade File > to a version that doesn't contain CSV anymore? I guess then upgrading > File might remove File/CVS.php - correct? I guess this could be > solved by giving a dependency from File_CSV that demands File v1.0.4 > (or what the next release will be called) so that prior to installing > File_CSV you have to upgrade File. Greg, might this work as expected? No, because File/CSV.php will still be removed if you upgrade File. Jan. -- http://www.horde.org - The Horde Project http://www.ammma.de - discover your knowledge http://www.tip4all.de - Deine private Tippgemeinschaft