Arjen, let me know if this commit agrees with the intent of the recent Mandriva changes. It was breaking the automated builds. I'll apply it to Testing if there are no objections. - Charles On May 5, 2008, at 10:38 PM, Charles Lepple wrote:> Author: clepple-guest > Date: Tue May 6 02:38:05 2008 > New Revision: 1475 > > Log: > configure.in: tell autoconf to generate packaging/mandriva/nut.spec
> let me know if this commit agrees with the intent of the recent > Mandriva changes. It was breaking the automated builds.I think so. The reason why I committed these changes is that if we have a nut.spec.in, distributing a nut.spec is redundant at best and if there are differences, the freshly generated one would overwrite them. So it's either a nut.spec or nut.spec.in as far as I'm concerned, to avoid confusion about which one is used.> I'll apply it to Testing if there are no objections.I'm not a Mandriva guy, so I don't know (and we don't have buildbots for it either). Best regards, Arjen
Maybe Matching Threads
- [nut-commits] svn commit r1632 - in trunk: . packaging
- [nut-commits] svn commit r1734 - in trunk/scripts: hal hotplug udev
- [nut-commits] svn commit r1567 - in trunk: . drivers
- [nut-commits] svn commit r1560 - trunk
- [nut-commits] svn commit r975 - in trunk: . docs drivers