<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>Hey,
<br/>
<br/>Sorry about the bad formatting here. If anyone wants the original notes (with formatting) let me know.
<br/>
<br/>Tim
<br/>
<br/>--
<br/><a href="http://samoff.com">http://samoff.com</a>
<br/>
<br/>----- Original message -----
<br/>> Message: 1
<br/>> Date: Sun, 11 Oct 2009 13:44:06 +0200
<br/>> From: Tim Samoff <<a href="mailto:samoff@gmail.com">samoff@gmail.com</a>>
<br/>> Subject: Maemo Summit /opt BOF notes...
<br/>> To: <a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a>
<br/>> Message-ID: <<a href="mailto:1255261446.3548.6.camel@Nokia-N900-41-10">1255261446.3548.6.camel@Nokia-N900-41-10</a>>
<br/>> Content-Type: text/plain; charset="utf-8"
<br/>>
<br/>> Hi,
<br/>>
<br/>> Using /opt: Why, How & For How Long?
<br/>>
<br/>> What are the issues?
<br/>>
<br/>> ? Standards.
<br/>> ? What about introducing a new 'mobile' Linux standard.
<br/>> ? Repackaging.
<br/>> ? Differences in flash performance.
<br/>>
<br/>> How to use /opt correctly:
<br/>>
<br/>> ? Every Linux system has /opt, and using it has been a long-time debate.
<br/>> ? Directly from upstream.
<br/>> ? /opt must be made seamless for developers.
<br/>> ? How to deal with hard-coded paths?
<br/>> ? Is /opt a temporary "fix"?
<br/>> ? Are there any other long-term solutions?
<br/>> ? What is Nokia's choice?
<br/>> ? What about using fast flash for swap and apps on slow?
<br/>> ? Some packages should not get better flash.
<br/>> ? Whatever the solution, using it should not be decided by the developer.
<br/>>
<br/>> How to get space for your package:
<br/>>
<br/>> ? /opt should be a short-term solution.
<br/>> ? Issues
<br/>> ? /opt survives reflash (same with /home).
<br/>> ? Heuristic is heuristic.
<br/>> ? Symlinks are necessary.
<br/>> ? Ideas
<br/>> ? Magic should be on the device.
<br/>> ? Magic should not be contained in Debian rules.
<br/>> ? Call Magic in build-bot after Debian rules.
<br/>> ? Optionally.
<br/>> ? First option, but later opt_out.
<br/>> ? Must introduce efficient maintenance of the Magic.
<br/>> ? Call Magic in dpkg for build package?
<br/>> ? Call Magic in maemo-build package?
<br/>> ? Profiling.
<br/>> ? Next SSU must clean entire /opt directory.
<br/>> ? Fix dpkg, if needed.
<br/>> ? Hook for Magic from Extras?
<br/>> ? Idea might not be entirely embraced by some people at Nokia.
<br/>> ? Clear documentation is necessary.
<br/>> ? On maemo.org wiki?
<br/>>
<br/>> Tim
<br/>>
<br/>> --
<br/>> <a href="http://samoff.com">http://samoff.com</a><br/></p>
</body>
</html>