On 2014-04-29, Michał Lesiak wrote:
> Hello Jérémie,
>
> On Tue, Apr 29, 2014 at 7:36 PM, Jérémie Courrèges-Anglas
> wrote:
>>
>> Try to deal with packages like the OpenBSD project does.
>> Just stuff your packages in http://foo/$release/packages/$arch/
>> Tell your clients to tweak their pkg.conf
Hello Jérémie,
On Tue, Apr 29, 2014 at 7:36 PM, Jérémie Courrèges-Anglas
wrote:
>
> Try to deal with packages like the OpenBSD project does.
> Just stuff your packages in http://foo/$release/packages/$arch/
> Tell your clients to tweak their pkg.conf and run pkg_add 10bees
> That's it.
That's ac
Hi,
Try to deal with packages like the OpenBSD project does.
Just stuff your packages in http://foo/$release/packages/$arch/
Tell your clients to tweak their pkg.conf and run pkg_add 10bees
That's it.
When you have a new version / a bumped package, just upload it there.
You don't need to purge th
On Tue, Apr 29, 2014 at 1:20 AM, Marc Espie wrote:
> Expect no help from me until you actually explain what you want to do in
> explicit terms. It looks like you're trying to pull a fast one on pkg_add,
> and obviously pkg_add isn't duped... you tell it you want to install
> something, and you
On Mon, Apr 28, 2014 at 3:05 PM, Michał Lesiak wrote:
> Hello,
>
> I'm trying to invent a oneliner for installing a specific package. The
> problem is, the destination file is a redirect file forwarding a request to
> a target package. The result is:
>
> # pkg_add -v
> http://10bees-agent.s3-w
You're not really explaining what you're trying to do, especially considering
you're redirecting agent.tgz to something that has a completely different
name...
So far, I see a very non transparent redirect to something having nothing
in common with the name you're trying to fetch. This looks very
6 matches
Mail list logo
