On Tue, 20 Jul 2010 17:37:50 +0200, Stefan Monnier <monn...@iro.umontreal.ca> wrote: >> In other words, I wonder why one would like to deblob. As long as you >> don't install the blobs in the image, you are not using it. So if you >> already downloaded it, what is the use of removing it above just not >> installing and using it. > > IIUC the issue is not whether to download this or not, but whether it > gets (installed and) used. So it's mostly a matter of marking the > un-free parts and then making them only available upon a very > explicit request. > > The degree to which the request should be explicit is of course > something that depends on how much you care about this kind of freedom.
OK, if you interpret it like that, one doesn't need to deblob the kernel source. We only need a configuration value that avoids installing the non-free stuff. > I personally would really like it if OpenWRT labelled each non-free part > and made it clear which part is free and which isn't (e.g. by placing > all the non-free packages (i.e. packages which include some non-free > element) in a separate (sub)menu). > I would recommend keeping the current menu structure based upon functionality and not free/non-free For non-free packages, would something like DEPENDS=-LIBRE work? If CONFIG_LIBRE is defined, these packages would simply disappear from the menu. -- Bas. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
