atom feed76 messages in org.freebsd.freebsd-stableRe: after the release ...
FromSent OnAttachments
Drew Derbyshire - UUPC/extended software supportMar 19, 1998 3:57 pm 
Daniel O'CallaghanMar 19, 1998 4:15 pm 
Eivind EklundMar 20, 1998 1:49 am 
Eivind EklundMar 20, 1998 1:52 am 
Drew Derbyshire - UUPC/extended software supportMar 20, 1998 5:51 am 
ni...@iii.co.ukMar 20, 1998 6:17 am 
Eivind EklundMar 20, 1998 7:47 am 
Mike SmithMar 20, 1998 8:02 am 
Jordan K. HubbardMar 20, 1998 8:22 am 
Mike SmithMar 20, 1998 8:51 am 
Brian BeattieMar 20, 1998 8:54 am 
Ted SpradleyMar 20, 1998 9:23 am 
Wes Peters - Softweyr LLCMar 20, 1998 9:40 am 
A. Karl HellerMar 20, 1998 10:04 am 
Matthew D. FullerMar 20, 1998 10:31 am 
Greg ShenautMar 20, 1998 11:00 am 
Brian BeattieMar 20, 1998 12:45 pm 
Ted SpradleyMar 20, 1998 1:08 pm 
Derek FlowersMar 20, 1998 1:10 pm 
Matthew D. FullerMar 20, 1998 1:18 pm 
melanie bMar 20, 1998 1:55 pm 
Jonathan M. BreslerMar 20, 1998 2:27 pm 
Daniel O'CallaghanMar 20, 1998 2:30 pm 
Daniel O'CallaghanMar 20, 1998 2:41 pm 
Daniel O'CallaghanMar 20, 1998 2:47 pm 
Ted SpradleyMar 20, 1998 3:02 pm 
Jordan K. HubbardMar 20, 1998 3:12 pm 
Jonathan M. BreslerMar 20, 1998 3:13 pm 
Eivind EklundMar 20, 1998 3:17 pm 
Chris FaehlMar 20, 1998 3:47 pm 
Jordan K. HubbardMar 20, 1998 3:59 pm 
Chad R. LarsonMar 20, 1998 4:38 pm 
Robert WatsonMar 20, 1998 5:36 pm 
Wes Peters - Softweyr LLCMar 20, 1998 5:44 pm 
Wes Peters - Softweyr LLCMar 20, 1998 5:52 pm 
Wes Peters - Softweyr LLCMar 20, 1998 5:58 pm 
Derek FlowersMar 20, 1998 6:22 pm 
Robert WatsonMar 20, 1998 6:33 pm 
Eivind EklundMar 20, 1998 6:50 pm 
Evan ChampionMar 20, 1998 7:02 pm 
Drew Derbyshire - UUPC/extended software supportMar 20, 1998 10:25 pm 
Cy Schubert - ITSD Open Systems GroupMar 20, 1998 11:48 pm 
Nate WilliamsMar 21, 1998 3:44 am 
Nate WilliamsMar 21, 1998 3:45 am 
Eivind EklundMar 21, 1998 6:47 am 
Derek FlowersMar 21, 1998 10:28 am 
allen campbellMar 21, 1998 12:39 pm 
Travis MikalsonMar 21, 1998 12:56 pm 
Matt BehrensMar 21, 1998 2:34 pm 
Jonathan M. BreslerMar 21, 1998 5:16 pm 
Drew Derbyshire - UUPC/extended software supportMar 21, 1998 8:33 pm 
Derek FlowersMar 22, 1998 12:38 am 
Jordan K. HubbardMar 22, 1998 7:38 am 
Robert WatsonMar 22, 1998 9:24 am 
Derek FlowersMar 22, 1998 10:12 am 
Derek FlowersMar 22, 1998 12:23 pm 
Jordan K. HubbardMar 22, 1998 2:45 pm 
Derek FlowersMar 22, 1998 4:16 pm 
Daniel O'ConnorMar 22, 1998 4:30 pm 
Daniel O'ConnorMar 22, 1998 5:00 pm 
Daniel O'CallaghanMar 22, 1998 10:34 pm 
Greg ShenautMar 22, 1998 10:56 pm 
Cy Schubert - ITSD Open Systems GroupMar 23, 1998 7:00 am 
Cy Schubert - ITSD Open Systems GroupMar 23, 1998 7:17 am 
Wes Peters - Softweyr LLCMar 23, 1998 9:20 am 
David WolfskillMar 23, 1998 9:51 am 
Cy Schubert - ITSD Open Systems GroupMar 23, 1998 11:41 am 
Derek FlowersMar 23, 1998 12:46 pm 
Derek FlowersMar 23, 1998 12:51 pm 
Wes Peters - Softweyr LLCMar 23, 1998 2:09 pm 
Cy Schubert - ITSD Open Systems GroupMar 23, 1998 2:35 pm 
Eivind EklundMar 23, 1998 2:36 pm 
Daniel O'ConnorMar 23, 1998 8:43 pm 
Derek FlowersMar 23, 1998 9:08 pm 
Eivind EklundMar 24, 1998 7:58 am 
Wes PetersMar 24, 1998 9:55 pm 
Subject:Re: after the release ...
From:Wes Peters - Softweyr LLC (soft@xmission.com)
Date:Mar 20, 1998 5:52:57 pm
List:org.freebsd.freebsd-stable

Daniel O'Callaghan opined:

The pkg system can be used here. pkgs record their own installation event, they have pre and post installation scripts which can display docs etc.

Yeah, I like this approach too. Figure out how to handle kernel patches and you've got it solved. One approach might be to make kernel object files mandatory, then you can at least re-link a new kernel, similar to the SunOS distribution.

Patches with dependencies could check for those.

pkg_add already handles dependency checking and installation.

Who would develop the patches? I would say that given a reasonably well-defined set of conventions, the developer should be able to create a patch corresponding to whatever changes he or she developed with very little extra work.

So what we want is a Makefile which will make an update patch, so the committer can create this new patch. We might end up with a lot of these, though. Perhaps it would be better to have a patchmeister (did I hear you volunteer, Drew? :-)) who could collect the patch-package creation requests and release an upgrade package every so often.

Or perhaps we'll just have to elect a 'Stable Collector' whose job is it create patches once they've been fully tested and OK'd by the users who cvsup -STABLE. This would lead to a smaller and more "stable" set of patches (hopefully). Richard Wackerbarth provided a service philosophically similar to this for the 2.1-STABLE community in the past.

What about security? This is an *excellent* point. It's a bit risky

PGP signature.

This isn't a bad idea for the package utility in general. We could make it complain about packages with no signature, and refuse to install packages whose signature doesn't match?

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message