ecurity in case anyone here can update us
>> regarding the status of base packaging or has URLs for projects/release-pkg.
>>
>> Roger
>>
> Packaging base is happening here:
> https://svnweb.freebsd.org/base/projects/release-pkg/
>
> It is mostly stalled for month
On Fri, Dec 18, 2015 at 03:21:13PM -0800, Roger Marquis wrote:
> Forwarding this from freebsd-security in case anyone here can update us
> regarding the status of base packaging or has URLs for projects/release-pkg.
>
> Roger
>
Packaging base is happening here:
https://svnweb.f
On 2015-12-18 18:21, Roger Marquis wrote:
>> > The plan is for 11 to have a fully packaged base system. There should
>> > be some information in developer summit reports on the wiki. The code
>> > is in projects/release-pkg.
>>
I have mostly complete code to make openssl in base 'private', it ju
On Fri, Dec 18, 2015 at 03:21:13PM -0800, Roger Marquis wrote:
> Forwarding this from freebsd-security in case anyone here can update us
> regarding the status of base packaging or has URLs for projects/release-pkg.
>
> Roger
This is from the conversation Baptiste and I had over IR
Forwarding this from freebsd-security in case anyone here can update us
regarding the status of base packaging or has URLs for projects/release-pkg.
Roger
Date: Fri, 18 Dec 2015 14:21:04 -0800 (PST)
To: freebsd-secur...@freebsd.org
Subject: Re: [OpenSSL] /etc/ssl/cert.pem not honoured by
On Fri, 2003-09-19 at 02:10, M. Warner Losh wrote:
> P.S. How do you handle the packlist generation? The ports system
> doesn't automatically generate these things, as far as I can tell, and
> I didn't see anything that you've added to do this.
>
> My agenda, if you will, on this is to deal with
On Fri, 2003-09-19 at 02:02, M. Warner Losh wrote:
> Why would you want to package sbin? Where do you see this work going?
> What problems do you think this will solve? Doing things a top level
> directory at a time isn't very interesting, but since it looks like a
> demo, perhaps you could sketc
P.S. How do you handle the packlist generation? The ports system
doesn't automatically generate these things, as far as I can tell, and
I didn't see anything that you've added to do this.
My agenda, if you will, on this is to deal with:
upgrades: portupgrade can grok packages. If you had a
Why would you want to package sbin? Where do you see this work going?
What problems do you think this will solve? Doing things a top level
directory at a time isn't very interesting, but since it looks like a
demo, perhaps you could sketch out what the polishing you'd envision.
Warner
__
On Thursday, September 18, 2003, at 11:28 am, Paul Richards wrote:
On Thu, 2003-09-18 at 11:25, Alexander Leidinger wrote:
We have programs in the ports tree which use our bsd.*.mk
infrastructure. Will there be a problem if such a program gets
installed
from ports (will it try to register itself
On Thu, 2003-09-18 at 12:09, Alexander Leidinger wrote:
> On Thu, 18 Sep 2003 11:28:31 +0100
> Paul Richards <[EMAIL PROTECTED]> wrote:
>
> > > We have programs in the ports tree which use our bsd.*.mk
> > > infrastructure. Will there be a problem if such a program gets installed
> > > from ports
On Thu, 18 Sep 2003 11:28:31 +0100
Paul Richards <[EMAIL PROTECTED]> wrote:
> > We have programs in the ports tree which use our bsd.*.mk
> > infrastructure. Will there be a problem if such a program gets installed
> > from ports (will it try to register itself 2 times)?
>
> I don't know, have yo
On Thu, 2003-09-18 at 11:25, Alexander Leidinger wrote:
> On Wed, 17 Sep 2003 16:27:03 +0100
> Paul Richards <[EMAIL PROTECTED]> wrote:
>
> > > However, I suspect that a marginally better place to use these would be
> > > in the "make distribute" target that "make release" uses. This way, the
> >
On Wed, 17 Sep 2003 16:27:03 +0100
Paul Richards <[EMAIL PROTECTED]> wrote:
> > However, I suspect that a marginally better place to use these would be
> > in the "make distribute" target that "make release" uses. This way, the
> > files are already separated out into directory structures, and it
On Wed, Sep 17, 2003 at 06:53:41PM +0100, Nik Clayton wrote:
>
> On Wednesday, September 17, 2003, at 04:27 pm, Paul Richards wrote:
> >I was thinking of adding an option to install so it registers the file
> >in a plist rather than actually doing the install. A seperate "make
> >plist" target co
On Wednesday, September 17, 2003, at 04:27 pm, Paul Richards wrote:
I was thinking of adding an option to install so it registers the file
in a plist rather than actually doing the install. A seperate "make
plist" target could then be used as a helper target to automate the
generation of plists.
I
On Wed, 2003-09-17 at 15:45, Mark Murray wrote:
> Paul Richards writes:
> > I've got a prototype setup that packages the base tree. It turned out to
> > be very simple. It needs a lot more polishing and testing but it looks
> > like this can definitely be made to work with just some tidying up and
Paul Richards writes:
> I've got a prototype setup that packages the base tree. It turned out to
> be very simple. It needs a lot more polishing and testing but it looks
> like this can definitely be made to work with just some tidying up and
> re-arranging of our existing make files. I've succesfu
Paul Richards wrote:
> I've got a prototype setup that packages the base tree. It turned out to
> be very simple. It needs a lot more polishing and testing but it looks
> like this can definitely be made to work with just some tidying up and
> re-arranging of our existing make files. I've succesfu
I've got a prototype setup that packages the base tree. It turned out to
be very simple. It needs a lot more polishing and testing but it looks
like this can definitely be made to work with just some tidying up and
re-arranging of our existing make files. I've succesfully created
packages of /sbin
20 matches
Mail list logo
