Sven Köhler upb.de> writes:
>
> Hi,
>
> i had some orphaned files in /etc/udev/rules.d. Namely 40-fuse.rules and
> 60-fuse.rules.
>
> The files were never removed, since they are protected - aren't they?
>
> So that is _very_, _very_ unpractical, because the older your gentoo
> gets, the mor
g and QA teams, who
should poke developers to decrease number of similar problems.
I maintain a bunch of Debian/sparc, Debian/i386, Gentoo/amd64, Gentoo/x86,
Solaris/sparc, Ubuntu/i686 boxes and mind you, out-of-box experience at
install time means A LOT.
More respect to the users => more respect
contain one list of features and be stable, while Edgy (advertised
as developers' dream) can be somewhat rough but most probably will contain
another list of new and exciting features. Example [1].
> Or could project status reports (as discussed here recently) fit the
> same bill?
Thanks for
Maybe I should raise such concerns to the User Representatives first, but
the overall flow of ideas was IMO rather worth to be sent to the mailing
list in a complete form. If you feel otherwise, I apologize.
With best regards,
Wiktor Wandachowicz
[1] NetBSD: Founder Fears End Of Project
http://kerneltrap.org/node/7061
--
gentoo-dev@gentoo.org mailing list
ense to provide a full source code as
well.
But in the case of Gentoo offshot which intends to use existing Gentoo
infrastucture (mirrors, sources, etc.) I'd suggest to consult the original
copyright (copyleft?) holders, that means Gentoo officials. Just in case.
Cheers,
Wiktor Wandachowicz
if you haven't done so before:
http://www.gnu.org/licenses/gpl.txt
http://www.gnu.org/copyleft/gpl.html
Cheers,
Wiktor Wandachowicz (SirYes)
PS. Sorry for the noise, but I thought this issue needed clarification.
--
gentoo-dev@gentoo.org mailing list
both sent via e-mail and posted to the forums
right now).
I'm positively sure that it wouldn't be that much work, with the obvious
benefit for the users. More forum posters would definitely read GWN this way,
because, frankly, not every Gentoo user is subscribed to the GWN newsletter.
B
t course to take.
Summing up:
* UTF-8 manuals: good or bad?
* how to handle mixed encodings of manuals?
* should man and/or groff handle UTF-8 better?
* should an eclass function be created to aid in correcting the encoding
of manual pages while installing them?
Any constructive comments are more t
build.sh:
if [ -f "${PORTAGE_BASHRC}" ]; then
source "${PORTAGE_BASHRC}"
fi
So, if the documentation is updated (and possibly advertized in next GWN), no
change (even small) is necessary.
And while I can voice my (user's) opinion, I *really* like the idea of
> Having a Gentoo theme here helps to associate the
> theme with the distribution. Nobody forced me to do this. I just like it :)
In his blog (http://www.livingwithpenguins.blogspot.com/), Steven O.
writes in the "Fresh WORKING install of Gentoo":
> One of the coolest things about the Fluxbox gui
Carsten Lohrke gentoo.org> writes:
> How do you want not to enforce it?
Have you actually read the proposal? It's quite sensible and is entitled:
"Proposal: Integrated boot themes on LiveCDs and installations"
I suppose that the themes would be defaulted to on the LiveCDs and optional
for regu
11 matches
Mail list logo
