On Sat, 4 Oct 2014, Christian Schoenebeck wrote:
> Am 03.10.2014 um 23:02 schrieb Robert P. J. Day:
> >
> > one more question before i put things away for the day.
> >
> > short form: given that i just reflashed my TP-LINK TL-MR3220 with
> > the image file:
> >
> > openwrt-ar71xx-generic-tl-mr3220-v2-squashfs-sysupgrade.bin
> >
> > from the downloads directory:
> >
> > https://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/
> >
> > is there a record of the exact .config file that was used to generate
> > that image?
> >
> > longer form: if, to do the above build, i start with the config file
> > in that directory, config.ar71xx_generic, that configuration selects
> > pretty much everything to build, specifically numerous packages with
> > "=m".
> >
> > as i understand it, when selecting *packages*, "=y" means the
> > package will be built and incorporated into the final (squashfs)
> > image, while "=m" means the package will be built but will be left on
> > the side for possible installation later, correct?
> >
> > i ask since that config file selects all of the luci packages with
> > "=m", which means they *won't* be part of the final image, right? but
> > the fact that that image clearly incorporates luci means the config
> > file must have selected at least some luci packages with "=y".
> >
> > in fact, i ran "opkg list" on that image, and i can see precisely
> > the packages that are part of the squashfs image:
> >
> > base-files - 156-r42625
> > busybox - 1.22.1-2
> > dnsmasq - 2.71-4
> > dropbear - 2014.63-2
> > firewall - 2014-09-19
> > ... snip ...
> > lua - 5.1.5-1
> > luci - 0.12+svn-r10530-1
> > luci-app-firewall - 0.12+svn-r10530-1
> > luci-base - 0.12+svn-r10530-1
> > luci-lib-nixio - 0.12+svn-r10530-1
> > luci-mod-admin-full - 0.12+svn-r10530-1
> > luci-proto-ppp - 0.12+svn-r10530-1
> > luci-theme-bootstrap - 0.12+svn-r10530-1
> > ... snip ...
> >
> > so, as long as i understand all the above correctly, the config file
> > used to build that image *must* have selected those luci-related
> > packages as "y", yes? is there a record of that config file somewhere?
> > thanks muchly for all your patience ... now it's time for beer.
> >
> > rday
> >
> Hi Robert,
>
> I just looked into the config.ar71xx_generic file located in the directory
> you posted above.
> There are the following entries marked =y
>
> CONFIG_PACKAGE_luci=y
> CONFIG_PACKAGE_luci-mod-admin-full=y
> CONFIG_PACKAGE_luci-app-firewall=y
> CONFIG_PACKAGE_luci-theme-bootstrap=y
> CONFIG_PACKAGE_luci-proto-ipv6=y
> CONFIG_PACKAGE_luci-proto-ppp=y
> CONFIG_PACKAGE_luci-base=y
> CONFIG_PACKAGE_luci-base_source=y
> CONFIG_PACKAGE_luci-lib-nixio=y
> CONFIG_PACKAGE_luci-lib-nixio_notls=y
>
> CONFIG_PACKAGE_libiwinfo-lua=y
> CONFIG_PACKAGE_lua=y
>
> That's what you see in opkg list.
> What's your question ?
hmmmmmm ... that's weird, that's not what i was seeing, i was seeing
all "m". i must have done something strange. so it looks like this
might be good after all, i'll have just the luci components i need
built into the squashfs.
ok, apparently, i was just being an idiot. won't be the last time.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
