ote that at important I wouldn't see the bug in listbugs, even if it
were open.
"At the end of the day, the user either cares enough to read stuff
carefully, or they are prepared to pick up the pieces". discuss. :-)
Would any of this be any different if such a change were neces
take, then I see the attraction of
trying to design out the task altogether.
> So in the case of php-related packages, yes, I do think that new packages
> should not bother with the alternative dependencies on php4*.
I find this much easier to understand now.
Thanks for taking the time to help me understand.
Regards,
Paddy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
rily chasing details which are not
relevant to the main task. But if the info is handy anyway, why not
put it in ? It's not like it's mistakable for a promise to maintain
other people's builds of the software against versions not in unstable
or is it ?
sorry for the confusion, but
Hi,
I read Debian maintainers guide and could not find answer for my question.
I maintain a rpm package that installs files as non-root user. How do I control
file ownership and permissions in deb packages?
Thanks,
Paddy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
4 matches
Mail list logo