2016-02-01 22:31 GMT+01:00 Luke Small :
>
> I think that there is some unwritten policy that nobody can get something
> like this into the system. Why on earth hasn't this happened yet?
>
>
Yeah, I think that if anyone has something they want into base it should go
in,
even
On 2016 Feb 01 (Mon) at 15:31:25 -0600 (-0600), Luke Small wrote:
:I think that there is some unwritten policy that nobody can get something
:like this into the system. Why on earth hasn't this happened yet?
Your proposed addition has been rejected, and will continue to be rejected.
1) The code
1. You can pick a mirror relatively trivially, but since I've run the
program, the fastest one isn't the one I chose manually. Also, it can
choose multiple mirrors at once, so presumably if there is a failure, it
will choose the next mirror(s) that it wrote down in pkg.conf
2. You are saying that
Jorge Castillo said:
> Why not make it a port?
Making port for figuring out PKGPATH doesn't sound right.
See, there are four problems with the program:
1. It is not good enough in doing its job. Which is funny, because
picking right mirror is trivially done without any program.
2. It
On 2016/02/01 08:43, Jorge Castillo wrote:
> the only though that has come to me concerning mirrors,
> while using OpenBSD all this years is "damn it sure would be nice to know
> which mirrors there are without connecting to the internet first".
Fixed in -current, see
I can't comment on code quality since I suck at programming but you
yourself said your program does not follow style(9) as much as it could, I
think this is not a good start. Why not make it a port? If this becomes
useful to a lot of people then maybe it can be in base later, but not
before it
I'm not merely experimenting with kqueue because I like the shiny bells and
whistles. I want to know how fast a mirror will download the same file from
different mirrors. ftp() is shitty for expediency. It does one of three
things it fails fast, succeeds fast, or it could take FOREVERR!!! I
I fixed the uname(1) call and replaced it with uname(3) I read the style
man page. ran the program through indent.
I ran it through sed because it reduces code complexity. Why re-engineer
the wheel?
I use C because I can use kqueue from a fresh install. You have to use
unaudited packages to use
On Mon, Feb 1, 2016 at 6:18 AM, Luke Small wrote:
> I fixed the uname(1) call and replaced it with uname(3) I read the style
> man page. ran the program through indent.
>
>
2 seasoned OpenBSD developers have taken time to reply to you, and they do
not like the general idea.
Whoops, got rid of putting in a null character when I should have left it
in.
-Luke
/*
* Copyright (c) 2016 Luke N. Small
*
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and
Firstly, I don't think we need this in base and I think there is little
to no chance of it being taken, even if the code is improved.
Secondly:
- The code is still miles off style(9) and isn't really a consistent
style within itself either.
- Forking uname(1)? What? No offence, but that is
On Fri, Jan 29, 2016 at 12:44 PM, Jérémie Courrèges-Anglas
wrote:
> Luke Small writes:
>
> > I wanted to use kqueue. Name another script or programming language that
> > offers it from the base install. NONE!
>
>
>
Hi Luke,
I understand your perspective.
Luke Small writes:
> I wanted to use kqueue. Name another script or programming language that
> offers it from the base install. NONE!
If you want to discover how to use kqueue, fine, but that's not how
design decisions are done in OpenBSD land.
> Why should I write it in
I wanted to use kqueue. Name another script or programming language that
offers it from the base install. NONE!
Why should I write it in another language. I already did it in C. Is there
another way other than kqueue that you can wait for the ftp call to quit,
while being able to kill it if it
Luke, don't feel bad. Very little code that is "offered" gets taken by
the OpenBSD project. OpenBSD really only takes when they see benefit
for the project. An example for that is openssh. What you really want
to do is focus on your own projects and make them available somewhere so
that when
I think I fixed all your suggestions. I don't strictly adhere to kernel
normal in the use of comments and I parse command-line arguments without
using getopt(3), but the method is robust.
-Luke
/*
* Copyright (c) 2016 Luke N. Small
*
* Permission to use, copy, modify, and distribute this
pkg_ping [-s timeout]
[-n maximum_mirrors_written]
It scrapes each mirror's location and URL from openbsd.org/ftp.html and
tests the package repository with the version and architecture of the
machine. It kills the ftp() and sed() functions it calls from C if it takes
too long by using kqueue.
17 matches
Mail list logo