On Mon, Jul 15, 2013 at 11:52:26AM -0500, Mark Felder wrote:
> On Mon, 15 Jul 2013 11:48:18 -0500, Teske, Devin
> wrote:
> > I think Mark was saying that libfetch doesn't yet support http proxy.
>
> Now that I've googled, I was referring to this PR
> http://www.freebsd.org/cgi/query-pr.cgi?pr=180
On Jul 14, 2013, at 11:42 PM, Baptiste Daroussin wrote:
> On Fri, Jul 12, 2013 at 11:52:19PM +, Teske, Devin wrote:
>> On Jul 12, 2013, at 4:16 PM, Baptiste Daroussin wrote:
>>
>>> Hi,
>>>
>>> I have just committed (r253305) a change the make pkg_install not being
>>> built
>>> and install
On Mon, 15 Jul 2013 11:48:18 -0500, Teske, Devin
wrote:
> I think Mark was saying that libfetch doesn't yet support http proxy.
Now that I've googled, I was referring to this PR
http://www.freebsd.org/cgi/query-pr.cgi?pr=180253
I thought it was complete missing functionality, not just that bug.
On Jul 14, 2013, at 11:38 PM, Baptiste Daroussin wrote:
> On Sat, Jul 13, 2013 at 06:51:00PM -0500, Mark Felder wrote:
>> On Sat, Jul 13, 2013, at 13:54, Teske, Devin wrote:
>>>
>>>
>>> If FTP access (or any of the other remote access methods) are going away
>>> for HEAD pkg access, I'll need t
On Jul 14, 2013, at 11:33 PM, Baptiste Daroussin wrote:
On Sun, Jul 14, 2013 at 04:52:26PM +, Teske, Devin wrote:
On Jul 14, 2013, at 8:01 AM, Chris Rees wrote:
On 14 Jul 2013, at 08:29, Teske, Devin wrote:
Simple, really.
Let's take RPM for example. The RPM package format has been porte
On Jul 14, 2013, at 11:27 PM, Baptiste Daroussin wrote:
> On Sun, Jul 14, 2013 at 07:29:50AM +, Teske, Devin wrote:
>>
>>> Or you
>>> can maintain the old cruft for your business -- just don't expect
>>> anyone else to use it, or even want to.
>>>
>>
>>
>> I have no intention of making ol
On Jul 14, 2013, at 11:23 PM, Baptiste Daroussin wrote:
On Sun, Jul 14, 2013 at 10:12:19AM +, Teske, Devin wrote:
On Jul 14, 2013, at 2:30 AM, Matthew Seaman wrote:
On 14/07/2013 06:48, Teske, Devin wrote:
Question: Where can I learn more about the actual format of what's in
the new tarball
On 7/15/13 10:12 AM, Teske, Devin wrote:
On Jul 14, 2013, at 3:43 PM, Craig Rodrigues wrote:
On Sat, Jul 13, 2013 at 10:54 PM, Teske, Devin
mailto:devin.te...@fisglobal.com>> wrote:
I assume that poudiere builds packages from ports.
Yes.
That's not how we build package repositories here
On 7/15/13 6:43 AM, Craig Rodrigues wrote:
On Sat, Jul 13, 2013 at 10:54 PM, Teske, Devin wrote:
I assume that poudiere builds packages from ports.
Yes.
That's not how we build package repositories here (and would expect that
there are many more like us).
How do you build packages if
On Fri, Jul 12, 2013 at 11:52:19PM +, Teske, Devin wrote:
> On Jul 12, 2013, at 4:16 PM, Baptiste Daroussin wrote:
>
> > Hi,
> >
> > I have just committed (r253305) a change the make pkg_install not being
> > built
> > and installed by default on HEAD.
> >
> > If you are still relying on it
On Sat, Jul 13, 2013 at 06:51:00PM -0500, Mark Felder wrote:
> On Sat, Jul 13, 2013, at 13:54, Teske, Devin wrote:
> >
> >
> > If FTP access (or any of the other remote access methods) are going away
> > for HEAD pkg access, I'll need to know so I can make the appropriate
> > changes in the HEAD
On Sun, Jul 14, 2013 at 04:52:26PM +, Teske, Devin wrote:
>
> On Jul 14, 2013, at 8:01 AM, Chris Rees wrote:
>
> > On 14 Jul 2013, at 08:29, Teske, Devin wrote:
> >>
>
> Simple, really.
>
> Let's take RPM for example. The RPM package format has been ported to other
> platforms.
So does p
On Sun, Jul 14, 2013 at 07:29:50AM +, Teske, Devin wrote:
>
> > Or you
> > can maintain the old cruft for your business -- just don't expect
> > anyone else to use it, or even want to.
> >
>
>
> I have no intention of making old-world packages... but I also have no
> intention of using "p
On Sun, Jul 14, 2013 at 10:12:19AM +, Teske, Devin wrote:
>
> On Jul 14, 2013, at 2:30 AM, Matthew Seaman wrote:
>
> > On 14/07/2013 06:48, Teske, Devin wrote:
> >> Question: Where can I learn more about the actual format of what's in
> >> the new tarballs? This is going to be important not f
On Jul 14, 2013, at 3:43 PM, Craig Rodrigues wrote:
On Sat, Jul 13, 2013 at 10:54 PM, Teske, Devin
mailto:devin.te...@fisglobal.com>> wrote:
I assume that poudiere builds packages from ports.
Yes.
That's not how we build package repositories here (and would expect that there
are many more
Am 15.07.2013 um 03:15 schrieb Adrian Chadd :
> Guys,
>
> Devin runs a _lot_ of FreeBSD stuff at his work.
Doubtlessly.
It wouldn't make sense on a small scale.
I assume, his system pre-dates most of the stuff nowadays filed under the
"dev-ops" moniker (chef, puppet…).
Probably also has (ha
Guys,
Devin runs a _lot_ of FreeBSD stuff at his work. If anything we as a
community should be making his life easier, not act like he's just
clueless and doing it wrong.
-adrian
On 14 July 2013 16:24, Rainer Duffner wrote:
>
> Am 15.07.2013 um 00:43 schrieb Craig Rodrigues :
>
>> On Sat, Jul
On Jul 14, 2013, at 11:50 AM, Adrian Chadd wrote:
> ... I bet you could do that. I bet you could build the rpm inside a
> linux jail and have the relevant uname bits overridden in the right
> way.
>
There's an idea.
--
Devin
> On 14 July 2013 09:52, Teske, Devin wrote:
>>
>> On Jul 14, 201
Am 15.07.2013 um 00:43 schrieb Craig Rodrigues :
> On Sat, Jul 13, 2013 at 10:54 PM, Teske, Devin
> wrote:
>
>>
>>
>> I assume that poudiere builds packages from ports.
>>
>
> Yes.
>
>
>>
>> That's not how we build package repositories here (and would expect that
>> there are many more l
On Sat, Jul 13, 2013 at 10:54 PM, Teske, Devin wrote:
>
>
> I assume that poudiere builds packages from ports.
>
Yes.
>
> That's not how we build package repositories here (and would expect that
> there are many more like us).
>
How do you build packages if you are not using FreeBSD ports? D
On 14 Jul 2013, at 08:29, Teske, Devin wrote:
>
> To give you an idea as to just how helpful this is...
>
> Imagine the following hierarchy:
>
> src/pkgbase/depend/mystuff/script1
> src/pkgbase/depend/mystuff/textfile1
> src/pkgbase/depend/mystuff/sourcefile.c
> src/pkgbase/depend/mystuff/Makefi
... I bet you could do that. I bet you could build the rpm inside a
linux jail and have the relevant uname bits overridden in the right
way.
-adrian
On 14 July 2013 09:52, Teske, Devin wrote:
>
> On Jul 14, 2013, at 8:01 AM, Chris Rees wrote:
>
>> On 14 Jul 2013, at 08:29, Teske, Devin wrote:
>
On Jul 14, 2013, at 8:01 AM, Chris Rees wrote:
> On 14 Jul 2013, at 08:29, Teske, Devin wrote:
>>
>> To give you an idea as to just how helpful this is...
>>
>> Imagine the following hierarchy:
>>
>> src/pkgbase/depend/mystuff/script1
>> src/pkgbase/depend/mystuff/textfile1
>> src/pkgbase/depe
In article <20130714064601$3...@grapevine.csail.mit.edu>,
dte...@freebsd.org writes:
>> [I wrote:]
>> It accesses the sqlite database in /var/db/pkg that was previously
>> retrieved from the remote repository.
>Now from what you explained of pkg, I'm worried that for bsdconfig:
>
>1. Browse packa
On 14/07/2013 11:12, Teske, Devin wrote:
> Interesting. I notice that (while looking ahead to see a prefix: of
> /usr/local in the +MANIFEST), the tarball itself has files that include
> /usr/local in their path.
Yes -- we consider the $PREFIX to be 'baked into' the package at compile
time. You
In article <20130714054840$7...@grapevine.csail.mit.edu>,
dte...@freebsd.org writes:
>How about rquery? What protocol does that use? and what does it talk to?
It accesses the sqlite database in /var/db/pkg that was previously
retrieved from the remote repository.
>Question: Where can I learn mor
On Jul 14, 2013, at 2:30 AM, Matthew Seaman wrote:
> On 14/07/2013 06:48, Teske, Devin wrote:
>> Question: Where can I learn more about the actual format of what's in
>> the new tarballs? This is going to be important not for bsdconfig,
>> but $work (we have our own build platform; I'm going to h
On 14/07/2013 06:48, Teske, Devin wrote:
> Question: Where can I learn more about the actual format of what's in
> the new tarballs? This is going to be important not for bsdconfig,
> but $work (we have our own build platform; I'm going to have to
> rewrite it from mastering PLIST files to masterin
On Jul 13, 2013, at 9:24 PM, Peter Wemm wrote:
> On Sat, Jul 13, 2013 at 11:54 AM, Teske, Devin
> wrote:
>
>> So yes... I'm asking... in a HEAD world, what is the "officially supported"
>> method of acquisition?
>
> * pkgng will be configured to pull via http from project
> infrastructure by
On 14/07/2013 04:18, Teske, Devin wrote:
> ASIDE: For efficiency, I will actually need three things: (1) a list
> of all packages (2) their descriptions and (3) their run-time dependencies.
That would be the repository catalogue, which you can download by 'pkg
update' (or it will happen automatic
On Jul 14, 2013, at 12:06 AM, Garrett Wollman wrote:
> In article <20130714064601$3...@grapevine.csail.mit.edu>,
> dte...@freebsd.org writes:
>
>>> [I wrote:]
>>> It accesses the sqlite database in /var/db/pkg that was previously
>>> retrieved from the remote repository.
>
>> Now from what you
On Jul 13, 2013, at 11:13 PM, Garrett Wollman wrote:
> In article <20130714054840$7...@grapevine.csail.mit.edu>,
> dte...@freebsd.org writes:
>
>> How about rquery? What protocol does that use? and what does it talk to?
>
> It accesses the sqlite database in /var/db/pkg that was previously
> re
On Jul 13, 2013, at 8:33 PM, Craig Rodrigues wrote:
On Sat, Jul 13, 2013 at 8:18 PM, Teske, Devin
mailto:devin.te...@fisglobal.com>> wrote:
Can you do an "rquery" on a local repository? (say, one that has been mounted
via NFS or some other media, local or otherwise but looking like a local
fi
On Jul 13, 2013, at 9:24 PM, Peter Wemm wrote:
> On Sat, Jul 13, 2013 at 11:54 AM, Teske, Devin
> wrote:
>
>> So yes... I'm asking... in a HEAD world, what is the "officially supported"
>> method of acquisition?
>
> This has been answered elsewhere, but to be absolutely clear:
>
> * 10.0 wil
On Sat, Jul 13, 2013 at 9:24 PM, Peter Wemm wrote:
> Footnote... *.cc.freebsd.org are generally project operated sites.
.. gah.. generally *NOT* project operated sites. They're third party
/ regional / local.
--
Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV
_
On Sat, Jul 13, 2013 at 11:54 AM, Teske, Devin
wrote:
> So yes... I'm asking... in a HEAD world, what is the "officially supported"
> method of acquisition?
This has been answered elsewhere, but to be absolutely clear:
* 10.0 will ship with pkgng format packages.
* pkgng will be configured to
On Sat, Jul 13, 2013 at 8:18 PM, Teske, Devin wrote:
>
> Can you do an "rquery" on a local repository? (say, one that has been
> mounted via NFS or some other media, local or otherwise but looking like a
> local filesystem once-mounted). What would be required to get a local
> repository like that
On Jul 13, 2013, at 4:51 PM, Mark Felder wrote:
> On Sat, Jul 13, 2013, at 13:54, Teske, Devin wrote:
>>
>>
>> If FTP access (or any of the other remote access methods) are going away
>> for HEAD pkg access, I'll need to know so I can make the appropriate
>> changes in the HEAD branch of bsdcon
On Sat, Jul 13, 2013, at 13:54, Teske, Devin wrote:
>
>
> If FTP access (or any of the other remote access methods) are going away
> for HEAD pkg access, I'll need to know so I can make the appropriate
> changes in the HEAD branch of bsdconfig.
>
It's simpler than you think. The new pkg uses lib
On Jul 13, 2013, at 11:16 AM, Kimmo Paasiala wrote:
> On Sat, Jul 13, 2013 at 7:46 PM, Teske, Devin
> wrote:
>>
>> On Jul 13, 2013, at 8:17 AM, Teske, Devin wrote:
>>
>>
>> On Jul 13, 2013, at 1:07 AM, Baptiste Daroussin wrote:
>>
>> On Fri, Jul 12, 2013 at 11:52:19PM +, Teske, Devin wr
On Sat, Jul 13, 2013 at 7:46 PM, Teske, Devin wrote:
>
> On Jul 13, 2013, at 8:17 AM, Teske, Devin wrote:
>
>
> On Jul 13, 2013, at 1:07 AM, Baptiste Daroussin wrote:
>
> On Fri, Jul 12, 2013 at 11:52:19PM +, Teske, Devin wrote:
> On Jul 12, 2013, at 4:16 PM, Baptiste Daroussin wrote:
>
> Hi,
On Jul 13, 2013, at 8:17 AM, Teske, Devin wrote:
On Jul 13, 2013, at 1:07 AM, Baptiste Daroussin wrote:
On Fri, Jul 12, 2013 at 11:52:19PM +, Teske, Devin wrote:
On Jul 12, 2013, at 4:16 PM, Baptiste Daroussin wrote:
Hi,
I have just committed (r253305) a change the make pkg_install not be
On Jul 13, 2013, at 1:07 AM, Baptiste Daroussin wrote:
On Fri, Jul 12, 2013 at 11:52:19PM +, Teske, Devin wrote:
On Jul 12, 2013, at 4:16 PM, Baptiste Daroussin wrote:
Hi,
I have just committed (r253305) a change the make pkg_install not being built
and installed by default on HEAD.
If you
On Sat, Jul 13, 2013 at 7:59 AM, Baptiste Daroussin wrote:
> On Sat, Jul 13, 2013 at 06:11:11AM -0500, Mark Linimon wrote:
> > fwiw, nanobsd also is still on pkg_*, but I intend to come up with
> > patches for that if someone else has not already done so.
> >
> > mcl
>
> There are lots of patches
On Sat, Jul 13, 2013 at 06:11:11AM -0500, Mark Linimon wrote:
> fwiw, nanobsd also is still on pkg_*, but I intend to come up with
> patches for that if someone else has not already done so.
>
> mcl
There are lots of patches available everyone to have nanobsd using pkgng
I didn't commit any, bec
fwiw, nanobsd also is still on pkg_*, but I intend to come up with
patches for that if someone else has not already done so.
mcl
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send a
On Fri, Jul 12, 2013 at 11:52:19PM +, Teske, Devin wrote:
> On Jul 12, 2013, at 4:16 PM, Baptiste Daroussin wrote:
>
> > Hi,
> >
> > I have just committed (r253305) a change the make pkg_install not being
> > built
> > and installed by default on HEAD.
> >
> > If you are still relying on it
On Jul 12, 2013, at 4:16 PM, Baptiste Daroussin wrote:
> Hi,
>
> I have just committed (r253305) a change the make pkg_install not being built
> and installed by default on HEAD.
>
> If you are still relying on it, be careful and add WITH_PKGTOOLS=yes in your
> src.conf(5)
I think while a good
Hi,
I have just committed (r253305) a change the make pkg_install not being built
and installed by default on HEAD.
If you are still relying on it, be careful and add WITH_PKGTOOLS=yes in your
src.conf(5)
regards,
Bapt
pgpc4PpvN64uc.pgp
Description: PGP signature
49 matches
Mail list logo
