On 2016-07-05, Nick Holland wrote:
> Think about it. If someone is MAINTAINING multiple versions of a
> package, they are doing it because they feel there is some REASON that
> multiple versions.
Even in those cases, there is often one particular version which is
On Tue, 05 Jul 2016 10:12:01 +0800
Tinker wrote:
> Wait, can "%" be used to install the latest version for unimportant
> packages?
>
> Or at least make pkg_add choose *some* version for me because I
> totally don't care, this would just be a trick to automate system
>
How about you go read ports archive ? I posted a whole explanation of the
branch mechanism in current. Plus you've got nicely documented stuff inside
pkg_add(1) and the things it links to, for instance, packages-specs(7)
On 2016-07-05 04:21, Nick Holland wrote:
(
On 07/04/16 22:11, Tinker wrote:
..
The *oldest* version would be fine too!
Write a little script to fetch the directory of the package repository,
apply /whatever logic you want/, then pkg_add that exact package.
Done.
The contention that "99%"
On 07/04/16 22:11, Tinker wrote:
> On 2016-07-05 10:09, Tinker wrote:
> ..
>> What made me ask this problem was Squid on 5.8, where there were two
>> versions. I realize that two versions of a very similar package is
>> very rare otherwise though, so maybe in the bigger picture the
>> question
On 2016-07-05 10:09, Tinker wrote:
..
What made me ask this problem was Squid on 5.8, where there were two
versions. I realize that two versions of a very similar package is
very rare otherwise though, so maybe in the bigger picture the
question didn't really make sense.
Wait, can "%" be used
-> Noise
My original intention when I asked this question was for tools where I
never ever will care about version number.
For Squid I don't. I guess some compression tool, for instance, would
count too - likely its behavior is exactly the same, and if it's not I
would be fine with realizing
On Mon, 04 Jul 2016, Chris Bennett wrote:
> Don't want to rebuild your production web/business servers?
> Look up Mtier in the mailing list. Nice helpful infrastructure.
Yes, I use their services both at work and at home.
> Not to sound like I'm kissing ass,
On Mon, Jul 04, 2016 at 06:48:32PM +0200, Kamil Cholewiński wrote:
>
> I think we're confusing two different concepts here... Latest stable
> release (with most recent security patches) vs following bleeding edge.
>
> Former is almost always what you want in production. There might be only
> one
On Mon, 04 Jul 2016, Marc Espie wrote:
> YES, they're all wrong. There's a BIG difference between running new
> shitz in a test setup vs running "bleeding edge" in production.
I think we're confusing two different concepts here... Latest stable
release (with most recent security
On Mon, Jul 04, 2016 at 04:35:10PM +0200, Kamil Cholewi??ski wrote:
> > But choosing and running the latest version automatically ? that's the
> > computer equivalent of running blindfolded into traffic on a speedway.
>
> Many people run CURRENT, trunk, HEAD, 0.999-dev, sid, Arch, however you
>
On Sun, 03 Jul 2016, Raul Miller wrote:
> And then there's the use case of untangling the mess when this did the
> wrong thing.
Well, I think nobody here argues that a program, if facing a hard
decision, should throw an error rather than corrupt the system.
I'm well
On Sun, Jul 03, 2016 at 09:41:34PM +0200, Kamil Cholewi??ski wrote:
> On Sun, 03 Jul 2016, Chris Bennett
> wrote:
> > This can't be done and should NOT be done. if you are asked to choose
> > between two+ different versions, often that choice is based on the
On Sun, Jul 3, 2016 at 3:41 PM, Kamil Cholewiński
wrote:
> You've totally missed the 99% use case: "just give me the latest version".
That's closer to the 95% use case, in my experience.
And then there's the use case of untangling the mess when this did the
wrong thing.
On 2016-07-03, Tinker wrote:
> At least on 5.8, neither -z nor -I do it, and those are the only
> arguments that give any hint of containing such a feature
> (http://man.openbsd.org/OpenBSD-current/man1/pkg_add.1).
For 5.8-5.9 something like "pkg_add -z squid-3.5.99" is
On Sun, 03 Jul 2016, Chris Bennett wrote:
> This can't be done and should NOT be done. if you are asked to choose
> between two+ different versions, often that choice is based on the other
> package(s) that depend on a particular version. You may even need to
On Sun, Jul 03, 2016 at 07:17:55PM +0800, Tinker wrote:
> At least on 5.8, neither -z nor -I do it, and those are the only arguments
> that give any hint of containing such a feature
> (http://man.openbsd.org/OpenBSD-current/man1/pkg_add.1).
>
> Is this feature supposed to be included in
On 2016-07-03 19:46, Tinker wrote:
Yeah I know -
My question was, HOW do I make pkg_add auto-choose the newest (or just
any) version really?
E.g. on 5.9, what arguments do you pass to "pkg_add" for "automake",
so that it will choose version 1.15, or anyhow just any version
without asking for
Yeah I know -
My question was, HOW do I make pkg_add auto-choose the newest (or just
any) version really?
E.g. on 5.9, what arguments do you pass to "pkg_add" for "automake", so
that it will choose version 1.15, or anyhow just any version without
asking for interactive user confirmation
if logic isrespected
3.5.6 is more recent without patch than 3.4.13 with patch 0..
I guess
>
> From: Tinker
> Sent: Sun Jul 03 13:17:55 CEST 2016
> To:
> Subject: How make "pkg_add" auto-choose some package
At least on 5.8, neither -z nor -I do it, and those are the only
arguments that give any hint of containing such a feature
(http://man.openbsd.org/OpenBSD-current/man1/pkg_add.1).
Is this feature supposed to be included in "pkg_add" or is a user(me)
refered to implement some own script?
21 matches
Mail list logo