Writing multiarch proposals seems to be this week's most popular sport. I've written my own proposal. This one should address most issues people have, without pissing off anybody too much. We need a was to say "this package depends on this package with this architecture", but apart from that, my proposal seems fairly solid. (At least nobody's been able to really pick it apart yet.) It doesn't attack my sense of aestetics either, unlike some of the other proposals.
Tollef Fog Heen's blog
tfheen Sat, 17 Jan 2004 - Multiarch proposal
tfheen Sat, 17 Jan 2004 - nice day
Woke up at about 0700, went to a lecture at 0815, I was there almost on time. I haven't been on time for any of those lectures this year. Then, I went to a physics lecture, but left after 45 minutes -- it was too boring and the lecturer was just reading stuff off a compilation. I had a small argument with a friend of mine, then went to the book shop and bought the books for my "Software architechture" course and my "System Administration" course. A little later, I went to a silly math lecture; another friend asked me if I'd like to go with her and I did. It was actually quite useful, I got to read a lot of physics there.
Then I went home, cleaned and bought food.
Anders and
Magni visited me for
dinner; we had some chicken with almonds, garlic, ginger, salt and
pepper. In addition, I added some red wine. It was delicious, and we
had ice cream for dessert. I just love ice cream. They left at about
2300, and then I discussed my
multiarch multiarch proposal on
IRC. Most people seem to agree that it's fairly sane, except that we
need to add the Depends: apache-common [amd64] syntax to dpkg and
apt. It's doable, according to bartman.



