> Soon I should also know if its possible to create openocd-devel port > that could build and install the package straight from the GIT > repository - this is a nice idea sparked by Xiaofan - so the testing > could be even more simple, however if someone wants to develop the > source code he/she will still need to use standard git repository > procedure, so its purpose might be questionable. Also with GIT > approach, the list of files for (de)installation might be a problem - > usually it is a static thing, and with git build it will be dynamic so > it can somehow leave trashes in the filesystem - some solution is to > install all devel files with some specific prefix, ie. > /tmp/devel/openocd so they can be easily removed without risking the > integrity of the system... but I will try to find the solution. > So is it sensible/worth to preape a port for this purpose, or assume > that developer use git anyway?
FYI, I for one would be very happy to see a standard FreeBSD port made for OpenOCD. Good for the lazy. Thanks, Steve _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
