can't we just optify /usr/include and /usr/lib ?<br><br><div class="gmail_quote">On Tue, Oct 20, 2009 at 3:48 PM, Nathan Anderson <span dir="ltr"><<a href="mailto:nathan@andersonsplace.net">nathan@andersonsplace.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Marius,<br>
<br>
Well, I agree dev packages are not really the target of a device.<br>
And as a dev I would probably feel comfortable moving things around (if they<br>
wanted to). I just noticed that about 75% of the .h files were optified<br>
and the rest weren't, and wanted to bring it up. Not really a huge issue.<br>
As a policy I've been optifing all the files it creates. Dev files actually<br>
would be a good canidate imho for the /opt folder since they aren't accesses<br>
often and can be large.<br>
<br>
Adding some more command line options might be useful.<br>
<font color="#888888"><br>
Nathan.<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
ext Nathan Anderson <<a href="mailto:nathan@andersonsplace.net">nathan@andersonsplace.net</a>> writes:<br>
<br>
> I noticed when I ran optification of a dev library is optified about<br>
<br>
> 75% of the c/c++ .h files. I would think for consistancy sake maybe<br>
> we should either optify all of them or none of them.<br>
<br>
Hmm, I think -dev libraries are not the primary target of optification right<br>
now. Would it be acceptable to have 'official' instructions (or a<br>
script) for moving all of /usr to the eMMC? I think this is preferable to<br>
using optified packages and people who want to develop on the device are<br>
probably willing and able to follow those instructions.<br>
<br>
> Yes, No?<br>
<br>
But if we optify a -dev package, we should probably tune the heuristic.<br>
Many -dev packages install into /usr/include/<name>/ where <name> is close<br>
to but not exactly the same as the package name. Right now, maemo-optify<br>
only moves whole directories if they are named exactly like the package. We<br>
could improve this heuristic carefully, or add some command line options or<br>
a control file for maemo-optify.<br>
<br>
I think the latter would be more useful.<br>
<br>
_______________________________________________<br>
maemo-developers mailing list<br>
<a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
</div></div></blockquote></div><br>