On 04/02/2012 06:28, Matěj Laitl wrote:
> On 4. 2. 2012 Chow Loong Jin wrote:
>> Sounds like Depends would be the right choice here...
>>
>>> This would crate circular dependency between libgpod4{,-nogtk} and
>>> libgpod-
>>> common, but I think this is okay as they come from the same source
>>> pa
On 4. 2. 2012 Chow Loong Jin wrote:
> Sounds like Depends would be the right choice here...
>
> > This would crate circular dependency between libgpod4{,-nogtk} and
> > libgpod-
> > common, but I think this is okay as they come from the same source
> > package.
>
> ...But this sounds like a real
On 04/02/2012 05:42, Matěj Laitl wrote:
> On 4. 2. 2012 Chow Loong Jin wrote:
>> Considering libgpod4-nogtk (and presumably the gtk one as well) are, as you
>> mentioned, practically useless without the -common package, do you think
>> libgpod-common should be bumped up to Depends for both packages
On 4. 2. 2012 Chow Loong Jin wrote:
> Considering libgpod4-nogtk (and presumably the gtk one as well) are, as you
> mentioned, practically useless without the -common package, do you think
> libgpod-common should be bumped up to Depends for both packages instead?
Yes, that would be best from my po
On 04/02/2012 04:34, Matěj Laitl wrote:
> Hello,
> to explain further, in order for libgpod to be able to actually write valid
> iPod database on all new models, it needs to know its model, firewire id and
> sometimes more. This information is automatically extracted thanks to udev
> hook from l
Hello,
to explain further, in order for libgpod to be able to actually write valid
iPod database on all new models, it needs to know its model, firewire id and
sometimes more. This information is automatically extracted thanks to udev
hook from libgpod-common and written to
/iPod_Control/Device
6 matches
Mail list logo
