I've chosen to at the momement to "dpkg -p panomatic" so that I can "dpkg -i pablomatic"
With regards to patent free panomatic, I assume that name is also under patent restrictions? I'd like to move to a patent free control point detector, not only in code, but also in name. There are several reasons for doing so; I'm testing the control point detectors in Hugin on my system and side by side would be a nice switcheroo option vs. the install/purge option. I'm USA based, and patent CP detectors present a problem for me, not only for stitching, but for distribution of binary form. Not being a programmer, I'd imagine finding and locating every "panomatic" option in the code might be a problem, but not such a daunting problem that I'm not afraid to tackle it. Having the name panomatic in the code, binary name, etc. makes me concerned there is still patent code in the code and binary. I'd heard rumors this was a GSOC 2010 project? The patent free code needs a name? I'd suggested GeoDaisy in a play on the papers names, but during my binary build used PabloMatic in respect to the programmer. Has a decision been made on the name of the patent free CP detector? Possible to get a name for it? My solution currently is to build and purge panomatic (in dpkg form) before building pablomatic. This way I can have two separate *.debs for the Ubuntu system. Dale On Wed, 2010-07-28 at 10:57 +0200, Harry van der Wolf wrote: > > > 2010/7/28 Dale Beams <[email protected]> > Can Pablo's version of panomatic co-exist with panomatic? Do > the binaries have the same name? > > > > > The binaries do have the same name and can't coexist for that reason > unless you install them in several directories or reneame them. Even > with several dirtectories: with both directories in the path, the > directory that gets first mentioned in the path contains the panomatic > that gets first called. What I did on OSX for the Hugin bundle is > rename Pablo's panomatic to patfree-panomatic during the "make > install" (, for the bundle that is). In that way they can coexist. > > What you can do is: > - not a (sudo) make install, but rename the binary and library and > copy it manually to the correct location. for Pablo's panomatic: > keypoints and (renamed?) panomatic to the relevant bin folder, and > (lib)localfeatures.<lib extention> to the relevant lib folder. > - Or first rename the installed panomatic and then (sudo) make install > the next panomatic. > > Harry > > > -- > You received this message because you are subscribed to the Google > Groups "Hugin and other free panoramic software" group. > A list of frequently asked questions is available at: > http://wiki.panotools.org/Hugin_FAQ > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to hugin-ptx > [email protected] > For more options, visit this group at > http://groups.google.com/group/hugin-ptx -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
