FUDCon Hackfests
by Josef Bacik
Hello,
Just curious about what exactly is entailed in a hackfest? For
example I plan on going to the kernel hackfest, do I need my laptop
for actual "hacking" or is it more of a bird of a feather type thing
like at OLS? Thanks much,
Josef
16 years, 2 months
Vanilla kernel RPM?
by Matthew Saltzman
Some time back, there was a discussion on fedora-list about vanilla
kernels. IIRC, Rahul offered to create an RPM for the vanilla
kernel.org kernels with no Fedora patches or only security patches for
those of us that wanted to test with vanilla kernels. I am wondering
whatever happened to that proposal.
I have a Thinkpad T61 with nVidia graphics. In F8, the machine refueses
to suspend--it goes into suspend mode and then spontaneously comes out.
This happens with the nVidia driver and the VESA driver (the nv driver
still doesn't work 8^(...). In RHEL5, an identical machine running the
VESA driver works perfectly.
I'd like to try to help troubleshoot this
(https://bugzilla.redhat.com/show_bug.cgi?id=254214), and I think having
a vanilla kernel might be useful.
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
16 years, 2 months
parted license change to GPLv3+
by David Cantrell
FYI
I am upgrading the parted package in Fedora to the latest upstream version. Among other things, the license for parted is now GPLv3 or any later version. I've checked everything in Fedora that uses parted and all things that are currently using it are [now] compatible with the license, but new components that want to use libparted will need to make sure the license is compatible.
If you have any questions, feel free to post here or email me directly.
Thanks,
--
David Cantrell <dcantrell(a)redhat.com>
Red Hat / Honolulu, HI
16 years, 2 months
RFC: Fedora Xfce Spin
by Rahul Sundaram
Hi
I have created a initial kickstart file for a Fedora Xfce spin available at
http://sundaram.fedorapeople.org/livecd-fedora-8-xfce.ks
I still have a problem in that a file called "Desktop", that is a
desktop file for the liveinst command is created on the default Xfce
desktop and Xfce complains about that during login. I am not sure where
that is coming from.
Before I submit this to release engineering, I would like to get some
feedback, fixes and suggestions on any improvements possible. My
intention it to do a initial release for Fedora 8 and continue with
incremental improvements over the Fedora 9 development period and have a
solid Xfce spin as part of the Fedora 9 release.
Rahul
16 years, 2 months
Re: heads up: tcl and tk 8.5
by Michael Thomas
John Ellson wrote:
> Michael Thomas wrote:
>> John Ellson wrote:
>>
>>> Michael Thomas wrote:
>>>
>>>> John Ellson wrote:
>>>>
>>>>
>>>>>> The 'restricted auto_path' patch that we are adding will limit the
>>>>>> search to %{_libdir}/tcl8.5 and %{_datadir}/tcl8.5. This greatly
>>>>>> improves the startup time for most Tcl applications. However, it
>>>>>> does
>>>>>> require that maintainers of Tcl extension packages make some
>>>>>> changes to
>>>>>> ensure that the extensions get installed into %{_libdir}/tcl8.5 (or
>>>>>> %{_datadir}/tcl8.5) instead of %{_libdir} (or %{_datadir}). I
>>>>>> will be
>>>>>> happy to help out any maintainers that want help with this change.
>>>>>>
>>>>> Will this information be available from some kind of introspection
>>>>> from
>>>>> running tclsh ?
>>>>>
>>>> Yes. You can start tclsh and run 'set auto_path'. This will print out
>>>> a list of the directories that will be searched for packages.
>>>>
>>>>
>>>>
>>>>> Has this change been accepted upstream so that it can be relied on on
>>>>> other platforms?
>>>>>
>>>> I had a discussion with upstream about this, and they blamed the
>>>> problem
>>>> on the distributions installing Tcl and the extensions into too-generic
>>>> directories. Unfortunately, most extensions were developed to be
>>>> installed directly into /usr/lib and /usr/share, and now need to be
>>>> patched to be installed elsewhere.
>>>>
>>>> In any case, you can always look at the contents of the auto_path
>>>> variable on any platform in Tcl to see where extensions are looked for.
>>>>
>>>> --Mike
>>>>
>>>>
>>> A bit more clarification please.
>>>
>>> This is not about where to look, its about where to install, so it must
>>> resolve to a single value.
>>>
>>
>> In that case, no, there is no introspection in Tcl to get this
>> information. This is because the choice of the directory in which to
>> install depends on whether you are installing an arch-specific or a
>> noarch package. But the rule is simple:
>>
>> noarch packages should get installed into
>> %{_datadir}/tcl8.5/%{name}-%{version}
>>
>> arch-specific packages should get installed into
>> %{_libdir}/tcl8.5/%{name}-%{version}
>>
>> The proposed Tcl packaging guidelines[1] have some scriptlets that you
>> can use at the top of your spec file to set the installation directory:
>>
>> %{!?tcl_version: %define tcl_version %(echo 'puts $tcl_version' | tclsh)}
>> %{!?tcl_sitelib: %define tcl_sitelib %{_datadir}/tcl%{tcl_version}}
>> %{!?tcl_sitearch: %define tcl_sitearch %{_libdir}/tcl%{tcl_version}}
>>
>> Use %{tcl_sitearch} as the base directory for arch-specific packages,
>> and %{tcl_sitelib} for noarch packages.
>>
>>
>>> Using a vanilla upstream build of tcl8.5 I get:
>>> % set auto_path
>>> /usr/local/lib/tcl8.5 /usr/local/lib
>>>
>>> Should I always install in the first member of the list? (which would
>>> be /usr/lib/tcl8.5 normally)
>>>
>>> And under that, I presumably install in a package-specific subdirectory?
>>> Such as: /usr/lib/tcl8.5/graphviz/
>>>
>>
>> Correct. You could add %{version} to the package-specific subdirectory
>> name so that it's possible to have multiple versions installed at the
>> same time, but that's not a requirement.
>>
>> --Wart
>> [1] http://fedoraproject.org/wiki/PackagingDrafts/Tcl
>>
>>
>
> Will tclConfig.sh remain in %{_libdir}/tclConfig.sh, or will it now be
> in %{_libdir}/tclsh8.5/tclConfig.sh ?
>
> (I think some other distros must do this already, since I already test
> for this in graphviz.)
tclConfig.sh will remain in %{_libdir}/tclConfig.sh.
--Wart
16 years, 2 months
Re: heads up: tcl and tk 8.5
by Michael Thomas
John Ellson wrote:
> Michael Thomas wrote:
>> John Ellson wrote:
>>
>>>> The 'restricted auto_path' patch that we are adding will limit the
>>>> search to %{_libdir}/tcl8.5 and %{_datadir}/tcl8.5. This greatly
>>>> improves the startup time for most Tcl applications. However, it does
>>>> require that maintainers of Tcl extension packages make some changes to
>>>> ensure that the extensions get installed into %{_libdir}/tcl8.5 (or
>>>> %{_datadir}/tcl8.5) instead of %{_libdir} (or %{_datadir}). I will be
>>>> happy to help out any maintainers that want help with this change.
>>>>
>>> Will this information be available from some kind of introspection from
>>> running tclsh ?
>>>
>>
>> Yes. You can start tclsh and run 'set auto_path'. This will print out
>> a list of the directories that will be searched for packages.
>>
>>
>>> Has this change been accepted upstream so that it can be relied on on
>>> other platforms?
>>>
>>
>> I had a discussion with upstream about this, and they blamed the problem
>> on the distributions installing Tcl and the extensions into too-generic
>> directories. Unfortunately, most extensions were developed to be
>> installed directly into /usr/lib and /usr/share, and now need to be
>> patched to be installed elsewhere.
>>
>> In any case, you can always look at the contents of the auto_path
>> variable on any platform in Tcl to see where extensions are looked for.
>>
>> --Mike
>>
>>
> A bit more clarification please.
>
> This is not about where to look, its about where to install, so it must
> resolve to a single value.
In that case, no, there is no introspection in Tcl to get this
information. This is because the choice of the directory in which to
install depends on whether you are installing an arch-specific or a
noarch package. But the rule is simple:
noarch packages should get installed into
%{_datadir}/tcl8.5/%{name}-%{version}
arch-specific packages should get installed into
%{_libdir}/tcl8.5/%{name}-%{version}
The proposed Tcl packaging guidelines[1] have some scriptlets that you
can use at the top of your spec file to set the installation directory:
%{!?tcl_version: %define tcl_version %(echo 'puts $tcl_version' | tclsh)}
%{!?tcl_sitelib: %define tcl_sitelib %{_datadir}/tcl%{tcl_version}}
%{!?tcl_sitearch: %define tcl_sitearch %{_libdir}/tcl%{tcl_version}}
Use %{tcl_sitearch} as the base directory for arch-specific packages,
and %{tcl_sitelib} for noarch packages.
> Using a vanilla upstream build of tcl8.5 I get:
> % set auto_path
> /usr/local/lib/tcl8.5 /usr/local/lib
>
> Should I always install in the first member of the list? (which would
> be /usr/lib/tcl8.5 normally)
>
> And under that, I presumably install in a package-specific subdirectory?
> Such as: /usr/lib/tcl8.5/graphviz/
Correct. You could add %{version} to the package-specific subdirectory
name so that it's possible to have multiple versions installed at the
same time, but that's not a requirement.
--Wart
[1] http://fedoraproject.org/wiki/PackagingDrafts/Tcl
16 years, 2 months