In our previous episode, Felipe Monteiro de Carvalho said: > > - There are writeln's in several places. This will break Windows GUI (Darwin > > ?too?) programs, and look sloppy on other systems. > > I isolated them in ifdefs > I removed the lazarus files, they aren't needed at all. > > Another thing is about the dependencies, a single unit, > "fpvtocanvas.pas" depends on fp-image, so the whole fpvectorial needs > to depend on it too as a build requisite, but nothing from fp-image is > used except in this unit, which has no other unit depending on it.
Yes. Our dependancies have package granularity. This avoids too much micro-managing dependancies (which means effectively they are always out of date). As long as it doesn't pull in unnecessary external dependancies, that is not a problem. Note that this is just a bunch of barren units. To make a decent package, this needs to be done: - Add to all units a decent copyright header WITH a description that is more descriptive than the unit name. - Add an entry to the "packages list" lemma in the wiki - examples, tests. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal