Hi,
Hope I am noat writiang to wrong address. I am nice, pretty looking
girl. I am planning on vibsiting your town this month. Can
we meet each other in person? Message me bback at [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contac
Goswin Brederlow wrote:
Two new fields are introduced:
Build-Depends-Arch, Build-Conflicts-Arch
You are aware, I hope, that the original proposal for the Build-* fields
contained these fields, and they were dropped from the proposal after
several people (buildd admins, if I recall correctly)
At 1150567172 past the epoch, SZERVÁC Attila wrote:
> ++ Contrib/Applications
> ++ Contrib/Games
> ...
> ++ Non-free/Applications
> ++ Non-free/Games
I think that could be confusing when packages migrate between
main,contrib,non-free. I don't know how often that happens.
> -- Text
> ++
Goswin von Brederlow wrote:
> On the other hand the savings can be huge. Think about how many
> packages install latex and fonts and generate the documentation
> needlessly during build. Installing and purging latex as well as all
> the initex runs and font generation takes up a awfull lot of time
At 1149960007 past the epoch, Ian Zimmerman wrote:
> I do not think this is an improvement. The main goal for
> menu items is (should be) clarity, not 100% grammatical or
> spelling correctness. Conservation of screen real estate
> is an important secondary goal, and should not be
> sacrificed to
My ideas:
++ Contrib/Applications
++ Contrib/Games
...
++ Non-free/Applications
++ Non-free/Games
...
-- Text
++ Text Tools/Utilities/Accessories...
sas-guest (Hungarian Translator)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contac
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> One question to ask is perhaps whether splitting the build dependencies
> into several sets is useful at all, considering that the current state
> of having effectively only one useful set has persistent for such a
> long time.
>
> Not a lot of peo
One question to ask is perhaps whether splitting the build dependencies
into several sets is useful at all, considering that the current state
of having effectively only one useful set has persistent for such a
long time.
Not a lot of people really understand the current definition, and this
p
8 matches
Mail list logo
