cyg Simple writes:
> I assumed that this was the case. But the symlink is a conflict and I
> assume that if one exists already the package management system would
> not recreate one or would ask the user if it should be overwritten.
The symlink to the actual executable is not a conflict since it
Ken Brown writes:
>>> So we'd need to bolt on a feature space in setup as well.
>
> I'm not sure what you mean by this. setup doesn't need to know whether a
> requirement is a feature or a package. It simply passes the dependencies
> (and
> the provides) to libsolv, which handles them just
On 10/9/2018 11:10 AM, cyg Simple wrote:
> On 10/8/2018 12:24 PM, Ken Brown wrote:
>> On 10/8/2018 11:17 AM, cyg Simple wrote:
>>> On 10/8/2018 11:05 AM, Ken Brown wrote:
Here's an example (modeled on what Fedora does): Cygwin has four
packages that provide emacs binaries: emacs,
On 10/8/2018 12:24 PM, Ken Brown wrote:
> On 10/8/2018 11:17 AM, cyg Simple wrote:
>> On 10/8/2018 11:05 AM, Ken Brown wrote:
>>> Here's an example (modeled on what Fedora does): Cygwin has four
>>> packages that provide emacs binaries: emacs, emacs-X11, emacs-lucid, and
>>> emacs-w32. Users can
On 10/8/2018 4:04 PM, Achim Gratz wrote:
> Ken Brown writes:
>> I created a test repo with packages A, B, and C. I made A require foo (not a
>> package), and I made B and C provide foo. The attached script does all this
>> [**]. I then ran setup and selected A for installation.
>
> That really
Ken Brown writes:
> I created a test repo with packages A, B, and C. I made A require foo (not a
> package), and I made B and C provide foo. The attached script does all this
> [**]. I then ran setup and selected A for installation.
That really only makes sense if several packages provide
On 10/7/2018 6:02 PM, Ken Brown wrote:
> I've been experimenting with setup's support for the 'provides:' tag, and it's
> not behaving the way I expect [*]. I'm not sure if something in setup's
> interface with libsolv needs to be tweaked or if I'm just misunderstanding how
> this should work.
On 10/8/2018 11:17 AM, cyg Simple wrote:
> On 10/8/2018 11:05 AM, Ken Brown wrote:
>> Here's an example (modeled on what Fedora does): Cygwin has four
>> packages that provide emacs binaries: emacs, emacs-X11, emacs-lucid, and
>> emacs-w32. Users can install any or all of these if they want to be
On 10/8/2018 11:05 AM, Ken Brown wrote:
> On 10/8/2018 10:41 AM, cyg Simple wrote:
>> On 10/7/2018 6:02 PM, Ken Brown wrote:
>>> I've been experimenting with setup's support for the 'provides:' tag, and
>>> it's
>>> not behaving the way I expect [*]. I'm not sure if something in setup's
>>>
On 10/8/2018 10:41 AM, cyg Simple wrote:
> On 10/7/2018 6:02 PM, Ken Brown wrote:
>> I've been experimenting with setup's support for the 'provides:' tag, and
>> it's
>> not behaving the way I expect [*]. I'm not sure if something in setup's
>> interface with libsolv needs to be tweaked or if
On 10/7/2018 6:02 PM, Ken Brown wrote:
> I've been experimenting with setup's support for the 'provides:' tag, and
> it's
> not behaving the way I expect [*]. I'm not sure if something in setup's
> interface with libsolv needs to be tweaked or if I'm just misunderstanding
> how
> this should
11 matches
Mail list logo
