On Wed, May 09, 2001 at 02:07:16AM -0400, Carl Worth wrote:
> Here are some assorted notes I made as I was testing familiar over the
> last few hours:
>
> 1) I noticed that the /etc/rc*.d directories are disappearing from
> most packages. What's the rationale for this? It seems to me like
> /etc/rc*.d is clearly the right way to start daemons and such. Or
> is Familiar policy taking us in some other direction? Speaking of
> which, a Familiar Policy Manual might be a very good document to
> start writing about now, (as tedious as that might be).
rc*.d is the proper place to put things, but I haven't really decided
what is going to happen outside of runlevel 2 (besides 0, 1, and 6).
For the rest of the world: Carl and I decided today that runlevel 2
is going to provide getty to the iPAQ serial port, while other
runlevels won't. We're still working out support for external serial
devices such as GPSes and Stowaway keyboards. This'll probably
change again before too long.
Re: Policy Manual. As things start coming up, I'll make sure they
get documented. I think we're still experimenting with what policies
we should be making, so right now our Manual would be nearly empty. ;>
> 2) I know that things have been hectic and we've all been scrambling
> to get familiar v0.4 ready, but I think it's time that we really
> start respecting the Maintainer field in the packages. It's been
> painful for me as I've upgraded packages recently and not known if
> someone else had also made changes that I would obliterate by
> committing my new packages. I am still listed as the Maintainer for
> most of the Familiar ipkgs, (thank you Alexander for taking some
> of them off my hands). By no means do I intend to remain the
> Maintainer on many of these, (although I am interested in
> streamlining the .deb->.ipkg process so I may hold on to the ipkgs
> that came from Debian). If you would like to update a package for
> which I am the Maintainer, please let me know and I will gladly
> give it up for you to maintain. If you don't want to become an
> official Maintainer, then please send patches to the
> Maintainer. I'll also stop updating any ipkgs for which I am not
> the Maintainer.
Nod. Agreed.
[snip]
>
> 4) ipkg currently complains about several missing dependencies when
> you install several packages. The "ipkg install
[snip]
> of these false dependencies, although a few might be worth a closer
> look to make sure there isn't any real dependency there.
Nod, the polishing process continues.
> 5) Another funny leftover from Debian-stripping is that we have
> packages such as dpkg which doesn't even provide any dpkg
> program. It actually only contains start-stop-daemon and md5sum. We
> should probably rename any such packages and adjust dependencies
> to match.
I just pulled dpkg. I've moved s-s-d and md5sum into familiar-base, which
isn't great, but it's temporary.
[snip]
> the meantime, I will be putting ipkgs together for at least nvi,
> elvis-tiny, and vim-tiny to see what else we might use.
Killer.
>
> 7) I found some bugs in ipkg that I haven't fixed yet, (I also fixed
> several so don't use any ipkg before 0.5 anymore). I need to log
> these in GNATS, (I'll do that after I return from this trip):
[snip]
> package. Otherwise, this requires remembering to manually remove
> old versions every time we upload a new package. If anyone wants to
> beat me to the update of ipkg-make-index I think that would be
> great. ;)
Yup. It'd be nice.
> Well, that's it for now. I think familiar v0.4 is really starting to
> shape up.
Nod. Just a bunch of cleanup. We're pretty close to an initial release.
There's going to for sure be a ``v0.4.1''.
> Alexander, let me know if I can help on the documentation front.
Things go. I think the docs are pretty much shaping up,.. I'll
have them online soon.
Alexander
Received on Fri May 11 02:19:46 2001
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:38:24 EDT