Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=2993920
By: flatcap
Hi Orion,
In the last two years, I've been through hundreds of combinations of smart rpms,
stupid rpms, dependencies, no dependencies and naming conventions.
Would it be possible to change the ntfs rpm naming/versioning scheme to allow
> for automatic updates to new kernel versions when they are installed?
>
No. The naming convention is the current "standard" for kernel modules.
kernel-module-ntfs-2.6.10-1.760_FC3-2.1.22-0.rr.4.3.i586.rpm
kernel-module A kernel module
ntfs Name
2.6.10 Linux kernel version
1.760_FC3 RedHat release
smp (Optional) kernel modifier
2.1.22 NTFS driver version
0 Epoch
rr Vendor (Richard Russon)
4 Spec file version
3 Distro version (2 = FC2, 3 = FC3)
i586 Architecture
rpm File type
but because the kernel version is part of the package name,
> this doesn't work for keeping the ntfs driver up to date.
>
The problem comes if you have more than one kernel type installed.
We use yum to keep our Fedora systems up to date,
>
Sourceforge have recently made some changes to their file release system. Soon
I may be able to create directories in the release area. If I can do that,
then I can create a yum repository, directly.
Also, shouldn't the rpm depend on the kernel package it is compiled for?
>
That would make sense, but it breaks certain update programs that don't expect
the kernel to be a dependency for something else.
Finally, I'm limited by sourceforge. Their file release mechanisms won't allow
me to make widespread re-releases. Since they are providing a HUGE amount of
storage and bandwidth (for free), I can't exactly change my hosting.
Cheers,
FlatCap (Rich)
______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=44084
|