Le 20/04/15 21:27, Domen Vrankar a écrit :
On the other hand, the risks might be limited if, by /convention/, we say
that all _cpack_deb_local_*** variables are reserved for local use only,
initialized at the beginning of the CPackDeb.cmake (or before).
Such agreements have the limitation of being forgotten so I prefer
enforcing it in code with a single base function in cmake script :)
I believe that if this is properly documented in the .cmake script, it
is maintainable. But you are the maintainer :)
I'll write a patch for that today and push it to next. I'll also add
link here so that you'll be able to use it before it gets to master.
Sounds like a bunch of conflicts on my side :)
Go ahead.
Sorry about that :( It's just that I noticed that in the past there
were many attempts at preventing accidental leakage of variables in
CPackRPM and I don't want to get the same problem in CPackDEB so it's
better to prevent it asap.
Is there any other thing you would like to do before I continue working
on this? Do you foresee any other change like this?
Best,
Raffi Enficiaud
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
