[ITA] X.Org X11R7.4

[ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I hereboy propose to take maintainership of Cygwin/X.

It was over two years ago that I started to work on the (then brand-new)
modular X11, and it was indeed in consideration of the sheer number of
packages involved that I created cygport.  Both cygport and X11 have
come a long way since then.  While there were several delays, both
personal and technical in nature, now I think we are (finally!) ready to
proceed.


WHAT'S NEW IN X11R7.4?

1) Each component (program, library, set of headers, set of fonts, etc.)
is shipped upstream in its own package, for a total of ~185 source
packages.  Sources are autotoolized, but the old imake system is still
available separately for external packages still using it.

2) /usr/X11R6 is gone; the standard /usr prefix is now used.

3) Fonts have been moved to /usr/share/fonts.

4) libX11 is XCB-based.  This adds a dependency on xcb-proto and libxcb,
which I propose to add now as well.

5) A number of X extensions (DMX, FontCache, LBX, XF86BigFont, Xinerama,
Xprint, XTrap, and the font server) have been deprecated upstream and in
most cases completely removed from the xserver; their corresponding
libraries and programs will therefore not be included.

6) OpenGL support is built from the upstream Mesa package, which I have
also split into individual library packages.


EXISTING X11 PACKAGES:

The current xorg-x11-* packages will be replaced by empty transitional
packages, and should now be considered OBSOLETE and standing in my name.

I will also take the X-start-menu-icons and X-startup-scripts packages,
which will be updated to reflect the new locations.

I would also ask the consent of the current maintainers of a few
X-related packages to take over these as well:

fontconfig (Jan Nieuwenhuizen)
lesstif (Brian Ford)
xterm (Jari Aalto)


TRANSITION PLAN:

1) Once approved, I will upload the new packages under release/X.Org/
for easier management; I request that this directory not be used for
other packages.

2) Empty xorg-x11-* transition packages will be uploaded, and these will
depend on the appropriate replacements ONLY as necessary, without
defeating the purpose of *modular* X11.

3) Existing packages which depend on X11 will have their dependencies
adjusted, with a notice here for maintainers to correct their local
copies accordingly.

4) An announcement will be made on cygwin-xfree-announce@ with all the
details.

5) X-dependent package maintainers should check their packages against
the new libraries, and rebuild if their package depends on an obsolete
library or if currently installed into /usr/X11R6.

6) Further development will continue on cygwin-xfree@.


WHAT I NEED:

1) PLEASE, don't even *think* about asking me to ITP all ~185 sources
individually. :-)

2) Approval of the addition of "_source" as a setup.hint package
category. This is used for library packages which are split up into
libfooN and libfoo-devel, with nothing to go in the "main" libfoo package.

3) cgf: I would like to coordinate a timeframe with you to do the move
into release/ and dependency-adjustment, so that we can handle any upset
errors by IRC rather than the list.

4) Write permissions for the Cygwin/X website, and moderator permissions
for cygwin-xfree-announce@ list.  (I already have upload permissions on
sourceware.)


THANKS:

Jon Turney for organizing everyone else's patches, and adding several
more of his own.

Colin Harrison for permission to use his Xming patches.

Janjaap Bos for pinpointing the font-finding problem to weak symbol
handling in libXfont, and helping with porting XWin to the new input API.

Larry Hall for continuing to answer questions on cygwin-xfree@.

Reini Urban for continual enthusiasm about this ever happening.

Previous Cygwin/X leaders Alan Hourihane, Alexander Gottwald, and Harold
L Hunt II, and all other previous maintainers and contributors.

And whomever else I may have inadvertently neglected to mention.


Yaakov


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkPjAsACgkQpiWmPGlmQSNj3QCeNqTA+W3YBXWzDILPBQ5OCUHE
jAUAoLsbFKCJGbnF+3yzm5gLgQaMFXsa
=cvKV
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yaakov (Cygwin Ports) wrote:
> I hereboy propose to take maintainership of Cygwin/X.

s/hereboy/hereby/


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkPlNYACgkQpiWmPGlmQSOTIQCgj20cz5cp2/pCqcrfxwY7hKp0
DGIAn3vtEz7uTIqdOoo7qhR5ImF9Nfi3
=sJnf
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Mon, Nov 03, 2008 at 05:41:00PM -0600, Yaakov (Cygwin Ports) wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>I hereboy propose to take maintainership of Cygwin/X.
>
>It was over two years ago that I started to work on the (then brand-new)
>modular X11, and it was indeed in consideration of the sheer number of
>packages involved that I created cygport.  Both cygport and X11 have
>come a long way since then.  While there were several delays, both
>personal and technical in nature, now I think we are (finally!) ready to
>proceed.
>
>
>WHAT'S NEW IN X11R7.4?
>
>1) Each component (program, library, set of headers, set of fonts, etc.)
>is shipped upstream in its own package, for a total of ~185 source
>packages.  Sources are autotoolized, but the old imake system is still
>available separately for external packages still using it.
>
>2) /usr/X11R6 is gone; the standard /usr prefix is now used.
>
>3) Fonts have been moved to /usr/share/fonts.
>
>4) libX11 is XCB-based.  This adds a dependency on xcb-proto and libxcb,
>which I propose to add now as well.
>
>5) A number of X extensions (DMX, FontCache, LBX, XF86BigFont, Xinerama,
>Xprint, XTrap, and the font server) have been deprecated upstream and in
>most cases completely removed from the xserver; their corresponding
>libraries and programs will therefore not be included.
>
>6) OpenGL support is built from the upstream Mesa package, which I have
>also split into individual library packages.
>
>
>EXISTING X11 PACKAGES:
>
>The current xorg-x11-* packages will be replaced by empty transitional
>packages, and should now be considered OBSOLETE and standing in my name.
>
>I will also take the X-start-menu-icons and X-startup-scripts packages,
>which will be updated to reflect the new locations.
>
>I would also ask the consent of the current maintainers of a few
>X-related packages to take over these as well:
>
>fontconfig (Jan Nieuwenhuizen)
>lesstif (Brian Ford)
>xterm (Jari Aalto)
>
>
>TRANSITION PLAN:
>
>1) Once approved, I will upload the new packages under release/X.Org/
>for easier management; I request that this directory not be used for
>other packages.
>
>2) Empty xorg-x11-* transition packages will be uploaded, and these will
>depend on the appropriate replacements ONLY as necessary, without
>defeating the purpose of *modular* X11.

>3) Existing packages which depend on X11 will have their dependencies
>adjusted, with a notice here for maintainers to correct their local
>copies accordingly.
>
>4) An announcement will be made on cygwin-xfree-announce@ with all the
>details.
>
>5) X-dependent package maintainers should check their packages against
>the new libraries, and rebuild if their package depends on an obsolete
>library or if currently installed into /usr/X11R6.
>
>6) Further development will continue on cygwin-xfree@.
>
>
>WHAT I NEED:
>
>1) PLEASE, don't even *think* about asking me to ITP all ~185 sources
>individually. :-)
>
>2) Approval of the addition of "_source" as a setup.hint package
>category. This is used for library packages which are split up into
>libfooN and libfoo-devel, with nothing to go in the "main" libfoo package.

This is what the external-source: tag is for.  Can't you just use that?

>3) cgf: I would like to coordinate a timeframe with you to do the move
>into release/ and dependency-adjustment, so that we can handle any upset
>errors by IRC rather than the list.

Don't you have upset available to you already?  I thought you or someone
was maintaining a fork.  There is also genini which might be adequate
for this purpose.

>4) Write permissions for the Cygwin/X website, and moderator permissions
>for cygwin-xfree-announce@ list.  (I already have upload permissions on
>sourceware.)

You already have write permissions to the Cygwin/X web site.  It's
controlled via CVS -- just like the main cygwin site.  Check out
ext:sourceware.org:/cvs/cygwin/htdocs .

Thanks very much for doing this.

cgf

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> This is what the external-source: tag is for.  Can't you just use that?

Let me explain with an example.  The libXfixes packages are:

(libXfixes3)
/usr/bin/cygXfixes-3.dll
/usr/share/doc/Cygwin/libXfixes-*.README
/usr/share/doc/libXfixes-*/*

(libXfixes-devel)
/usr/include/X11/extensions/Xfixes.h
/usr/lib/libXfixes.*
/usr/lib/pkgconfig/xfixes.pc
/usr/share/man/man3/*

libXfixes3 and libXfixes-devel have category: X11 and external-source:
libXfixes.  AFAIK (and please correct me if I'm wrong) upset and/or
setup require a binary libXfixes package to go alongside the source
package, so they are empty.   I don't want the empty binary libXfixes to
pollute the package list, so I used the _source category for libXfixes
so that it's hidden by default.

> Don't you have upset available to you already?  I thought you or someone
> was maintaining a fork.  There is also genini which might be adequate
> for this purpose.

I use genini for the Ports setup.ini's, and I see no problems there.
But I also need to change 80+ other packages' dependencies, and between
it all I'm just being cautious if I make a mistake that you don't get
swamped with emails for hours on end.

> You already have write permissions to the Cygwin/X web site.  It's
> controlled via CVS -- just like the main cygwin site.  Check out
> ext:sourceware.org:/cvs/cygwin/htdocs .

OK, thanks.  How is the cygwin-xfree-announce moderation handled?


Yaakov
Cygwin Ports
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkPuPEACgkQpiWmPGlmQSOZCACfTaDc7CIb01X/WrZQerId+TE6
frsAmwRgiWeEsWRpV7Lc3sRIGTnMLLWQ
=ULAf
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Brian Dessent]

"Yaakov (Cygwin Ports)" wrote:

> libXfixes3 and libXfixes-devel have category: X11 and external-source:
> libXfixes.  AFAIK (and please correct me if I'm wrong) upset and/or
> setup require a binary libXfixes package to go alongside the source
> package, so they are empty.   I don't want the empty binary libXfixes to
> pollute the package list, so I used the _source category for libXfixes
> so that it's hidden by default.

I don't like the precedent this creates -- it's bad UI.  The user is
supposed to be able to get the source by just putting an X in the Src
box of the normal package.  But with this scheme they can no longer do
that, they have to know to first show hidden packages and then to select
the Src column of an empty dummy package that is otherwise never
displayed, used, or needed.  Why can't you just associate the source
package with one of the two existing binary packages instead of
inventing a third, empty, hidden package to associate it with?

Brian

Re: [ITA] X.Org X11R7.4

[Brian Dessent]

Brian Dessent wrote:

> I don't like the precedent this creates -- it's bad UI.  The user is
> supposed to be able to get the source by just putting an X in the Src
> box of the normal package.  But with this scheme they can no longer do
> that, they have to know to first show hidden packages and then to select
> the Src column of an empty dummy package that is otherwise never
> displayed, used, or needed.

Errr, nevermind.  That's nonsense.  Setup will follow the
external-source line and do the right thing when the user selects Src of
any of the packages.

> Why can't you just associate the source
> package with one of the two existing binary packages instead of
> inventing a third, empty, hidden package to associate it with?

But I still think this makes more sense.

Brian

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Brian Dessent wrote:
>> Why can't you just associate the source
>> package with one of the two existing binary packages instead of
>> inventing a third, empty, hidden package to associate it with?
> 
> But I still think this makes more sense.

Because this means jumping through a lot more hoops, believe me.  This
method (where there's no binary package corresponding to the source
package) has precedence in Debian as well.


Yaakov

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkPxZ8ACgkQpiWmPGlmQSPBVACdFjezrx6yxRqyEqK532Ddvun0
iTMAn1V0D7g1THH1Z9pnbfL6fopQQNPk
=LMN3
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Brian Dessent]

"Yaakov (Cygwin Ports)" wrote:

> Because this means jumping through a lot more hoops, believe me.  This
> method (where there's no binary package corresponding to the source
> package) has precedence in Debian as well.

If it really does save you time than I remove my objection.  Can I just
request that the sdesc of such packages say something informative and
explicit about their purpose, e.g.:

sdesc: "X.Org Xfixes library (dummy placeholder for source package)"

I realize this string will never be seen by end-users but it does help
to self-document the purpose behind the package's existance when one is
troubleshooting setup by looking at setup.ini or whatnot.

Brian

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Mon, Nov 03, 2008 at 09:46:39PM -0600, Yaakov (Cygwin Ports) wrote:
>Brian Dessent wrote:
>>> Why can't you just associate the source
>>> package with one of the two existing binary packages instead of
>>> inventing a third, empty, hidden package to associate it with?
>> 
>> But I still think this makes more sense.
>
>Because this means jumping through a lot more hoops, believe me.  This
>method (where there's no binary package corresponding to the source
>package) has precedence in Debian as well.

You can must make a package which contains nothing but source.  You
don't need a binary.

cgf

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Brian Dessent wrote:
> If it really does save you time than I remove my objection.  Can I just
> request that the sdesc of such packages say something informative and
> explicit about their purpose, e.g.:
> 
> sdesc: "X.Org Xfixes library (dummy placeholder for source package)"

Each library subpackage is already labeled (runtime), (development), or
(source) in sdesc.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkPz5MACgkQpiWmPGlmQSMVjwCglKYewJYcPk9C2HZGj3fQnqe+
cGwAn2O2IgVNIpJcD9EC++KsltIE3cw6
=76LT
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> You can must make a package which contains nothing but source.  You
> don't need a binary.

But a setup.hint is still required, correct?


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkPz74ACgkQpiWmPGlmQSMT6wCgy9x/cREcPUcx7G3/cgDx4lLM
ieYAmwZufj904LM2jOZT7NUGMpxKnlnO
=STyG
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Brian Dessent]

"Yaakov (Cygwin Ports)" wrote:

> Each library subpackage is already labeled (runtime), (development), or
> (source) in sdesc.

Yes, that's kind of my point: say "dummy placeholder for source package"
and not just "source" so that its purpose (and the reason why it's
hidden from the user) is clear.

Brian

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Mon, Nov 03, 2008 at 10:29:50PM -0600, Yaakov (Cygwin Ports) wrote:
>Christopher Faylor wrote:
>> You can must make a package which contains nothing but source.  You
>> don't need a binary.
>
>But a setup.hint is still required, correct?

Yes, unless you want the package to go to "Misc", which is wrong.  But I
don't see any reason to hide anything.  Just sdesc it as "Sources for
BLAH".  It won't be installed unless the user specifically chooses it.

Incidentally, I set up a scratch area:

/sourceware/snapshot-tmp/cgf/yselkowitz

You can make a copy of the release area there if you want to experiment
with dependencies and genini.  You'll have to make a temporary copy of
genini in your home directory though first.

And, that reminds me, for anyone who is following this thread: Please
don't use your home directory on sourceware as a holding place for
files.  The home partition isn't that large and sourceware isn't
supposed to be used for permanent storage.

cgf

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> Yes, unless you want the package to go to "Misc", which is wrong.  But I
> don't see any reason to hide anything.  Just sdesc it as "Sources for
> BLAH".  It won't be installed unless the user specifically chooses it.

The reason for wanting to hide it is to stop it from cluttering the
package list in setup.exe.  If I use category: X11, then e.g. libXfixes
will be right next to libXfixes3 and libXfixes-devel in both by-category
and by-alphabet sorting modes.  And frankly I don't want to answer the
inevitable questions of "does anybody know why setup.exe is broken?  I
installed libXfixes, but I still get an error from such-and-such that
cygXfixes-3.dll is missing." :-)

> Incidentally, I set up a scratch area:
> 
> /sourceware/snapshot-tmp/cgf/yselkowitz
> 
> You can make a copy of the release area there if you want to experiment
> with dependencies and genini.  You'll have to make a temporary copy of
> genini in your home directory though first.

There's space there for *all* of release plus 110MB for modular X11?


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkP24sACgkQpiWmPGlmQSP2CgCfV8dTVlf796wvA76WOADRsHqR
wJEAoLWo3d60wLi4yJ5opeSlsbjAdYkz
=ojlO
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> Yes, unless you want the package to go to "Misc", which is wrong.  But I
> don't see any reason to hide anything.  Just sdesc it as "Sources for
> BLAH".  It won't be installed unless the user specifically chooses it.

I tried removing the empty binary tarballs and re-ran genini (all
locally), and I got the following for each library:

error: release/X.Org/libfontenc/setup.hint:3: not enough package files
in release/X.Org/libfontenc

The setup.ini entry for each library source had only category, sdesc,
and ldesc tags.  The corresponding ABI-versioned-lib and -devel packages
had correct source tags.

Running setup.exe (2.602) from this setup.ini, these packages don't show
up *at all*, even under the _source category.

If those are indeed the expect results, and the error is ignored, then
the point is moot.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkP5D4ACgkQpiWmPGlmQSNJqQCfT6jvSLjiSrvixjxGIaVRqqRm
SIAAoKNHPm9Yaqw14k8C33egRqf6gahm
=Nfsz
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Mon, Nov 03, 2008 at 11:59:06PM -0500, Christopher Faylor wrote:
>On Mon, Nov 03, 2008 at 10:29:50PM -0600, Yaakov (Cygwin Ports) wrote:
>>Christopher Faylor wrote:
>>> You can must make a package which contains nothing but source.  You
>>> don't need a binary.
>>
>>But a setup.hint is still required, correct?
>
>Yes, unless you want the package to go to "Misc", which is wrong.  But I
>don't see any reason to hide anything.  Just sdesc it as "Sources for
>BLAH".  It won't be installed unless the user specifically chooses it.
>
>Incidentally, I set up a scratch area:
>
>/sourceware/snapshot-tmp/cgf/yselkowitz

Sorry, drop the /cgf from the above:

/sourceware/snapshot-tmp/yselkowitz

cgf

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Mon, Nov 03, 2008 at 11:57:18PM -0600, Yaakov (Cygwin Ports) wrote:
>Christopher Faylor wrote:
>> Yes, unless you want the package to go to "Misc", which is wrong.  But I
>> don't see any reason to hide anything.  Just sdesc it as "Sources for
>> BLAH".  It won't be installed unless the user specifically chooses it.
>
>I tried removing the empty binary tarballs and re-ran genini (all
>locally), and I got the following for each library:
>
>error: release/X.Org/libfontenc/setup.hint:3: not enough package files
>in release/X.Org/libfontenc

genini differs from upset in this way, then.  You can probably just remove
that error.

>The setup.ini entry for each library source had only category, sdesc,
>and ldesc tags.  The corresponding ABI-versioned-lib and -devel packages
>had correct source tags.
>
>Running setup.exe (2.602) from this setup.ini, these packages don't show
>up *at all*, even under the _source category.

I created a setup.ini which had only a -src package and it definitely
shows up in setup.ini.  I didn't try actually running setup.exe on that
setup.ini but I'd be surprised if it didn't show up.

I am as pessimistic as anyone about the ability of users to understand
what setup.exe is showing them but it seems to me that if you have a
package called foo-source and only the source is available it should be
pretty clear what is going on.

cgf

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> genini differs from upset in this way, then.  You can probably just remove
> that error.

This is probably where I got the idea that an empty bin was necessary.
I'll just ignore it.

> I created a setup.ini which had only a -src package and it definitely
> shows up in setup.ini.  I didn't try actually running setup.exe on that
> setup.ini but I'd be surprised if it didn't show up.

By me it shows up in setup.ini, but only the category, sdesc, and ldesc
tags, no install or source tags.

> I am as pessimistic as anyone about the ability of users to understand
> what setup.exe is showing them but it seems to me that if you have a
> package called foo-source and only the source is available it should be
> pretty clear what is going on.

I tried, and it didn't show up at all, which is fine by me.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkQbwEACgkQpiWmPGlmQSM+kACgr1ctM1SCC9NKFCYuTZVvbiBb
XVAAnjJSMa5AK9kO0aWsqXi0OjHm90Tr
=rP13
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Tue, Nov 04, 2008 at 09:49:22AM -0600, Yaakov (Cygwin Ports) wrote:
>Christopher Faylor wrote:
>>genini differs from upset in this way, then.  You can probably just
>>remove that error.
>
>This is probably where I got the idea that an empty bin was necessary.
>I'll just ignore it.
>
>>I created a setup.ini which had only a -src package and it definitely
>>shows up in setup.ini.  I didn't try actually running setup.exe on that
>>setup.ini but I'd be surprised if it didn't show up.
>
>By me it shows up in setup.ini, but only the category, sdesc, and ldesc
>tags, no install or source tags.

You're talking about genini.  Look at the code for genini and you'll see
why that is the case.  upset does not work this way.

cgf

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> You're talking about genini.  Look at the code for genini and you'll see
> why that is the case.  upset does not work this way.

I don't have access to upset; what does the entry look like?


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkQh4QACgkQpiWmPGlmQSM3SQCcDHvmYP8+B5yu+yvXFazMHrH2
79cAn2pKrBV9uy1M8X02YJi2XO/+fsom
=7GJs
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Tue, Nov 04, 2008 at 11:33:56AM -0600, Yaakov (Cygwin Ports) wrote:
>Christopher Faylor wrote:
>>You're talking about genini.  Look at the code for genini and you'll
>>see why that is the case.  upset does not work this way.
>
>I don't have access to upset; what does the entry look like?

It contains a "source" entry and no "install" entry just like you'd
expect.  That's what I meant when I said "it definitely shows up
in setup.ini".

It looks like just removing the error check in genini will make it work
similarly to upset.

cgf

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> It contains a "source" entry and no "install" entry just like you'd
> expect.  That's what I meant when I said "it definitely shows up
> in setup.ini".
>
> It looks like just removing the error check in genini will make it work
> similarly to upset.

There's still a difference that genini doesn't make a source entry
either, which I think makes a lot of sense and would eliminate the need
for a _source category.  But what is actually used for release, upset or
genini?


Yaakov

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkQjcsACgkQpiWmPGlmQSOfXgCfejXSdaKIrMCkQvkfFDLFCDlH
F7YAnA849aOkeqqc7k1XBrZvTdqucTmC
=NanN
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> Incidentally, I set up a scratch area:
> 
> /sourceware/snapshot-tmp/yselkowitz

Thanks for setting up the staging area.  Looks like everything is ready
now, EXCEPT:

1) I get "PROBLEMS WITH" errors on the new xorg-x11-* empty tarballs,
whether I use 46-byte or 14-byte tarballs.  (The list is in the OBSOLETE
file at the top of the staging area.)

2) I need ITA agreement for fontconfig and lesstif; new files are
already in place.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkRHYIACgkQpiWmPGlmQSP/lgCgyes9DLNrnM9KC9mtj7MUmEwj
GEMAoOyY2ZwzvibIdF+1loaonmirY1ot
=Rq6u
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Tue, Nov 04, 2008 at 10:15:04PM -0600, Yaakov (Cygwin Ports) wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>Christopher Faylor wrote:
>> Incidentally, I set up a scratch area:
>> 
>> /sourceware/snapshot-tmp/yselkowitz
>
>Thanks for setting up the staging area.  Looks like everything is ready
>now, EXCEPT:
>
>1) I get "PROBLEMS WITH" errors on the new xorg-x11-* empty tarballs,
>whether I use 46-byte or 14-byte tarballs.  (The list is in the OBSOLETE
>file at the top of the staging area.)

You can ignore those.

cgf

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> You can ignore those.

Good; there are no other messages from upset in the staging area.  All I
need then is permission to adopt fontconfig and lesstif.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkRN9UACgkQpiWmPGlmQSNldQCgvm96KM5MZ99Pnh3b8eQi1aud
qswAn3HTYRJQnCu7/JnaumbH2YAFi+2v
=LsKi
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yaakov (Cygwin Ports) wrote:
> Good; there are no other messages from upset in the staging area.  All I
> need then is permission to adopt fontconfig and lesstif.

Just waiting for fontconfig now.  ITA sent five days ago and no response
from Jan.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkWgUUACgkQpiWmPGlmQSPMswCg5/zlPIWJHr/WpWxeE13mRngW
6xcAoMNpElq+hHDkwCgCFUlUVRsE/y3q
=V6M3
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Corinna Vinschen]

[PING Jan :)]

On Nov  9 00:20, Yaakov (Cygwin Ports) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Yaakov (Cygwin Ports) wrote:
> > Good; there are no other messages from upset in the staging area.  All I
> > need then is permission to adopt fontconfig and lesstif.
> 
> Just waiting for fontconfig now.  ITA sent five days ago and no response
> from Jan.

Jan could be on vacation.  Let it simmer a couple more days.  I added
him to the recipients of this single mail just for the ping.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Mon, Nov 10, 2008 at 10:49:54AM +0100, Corinna Vinschen wrote:
>[PING Jan :)]
>
>On Nov  9 00:20, Yaakov (Cygwin Ports) wrote:
>> Yaakov (Cygwin Ports) wrote:
>> > Good; there are no other messages from upset in the staging area.  All I
>> > need then is permission to adopt fontconfig and lesstif.
>> 
>> Just waiting for fontconfig now.  ITA sent five days ago and no response
>> from Jan.
>
>Jan could be on vacation.  Let it simmer a couple more days.  I added
>him to the recipients of this single mail just for the ping.

It would help me if we could do this ASAP so there would be less bit rot
in Yaakov's private copy of release to contend with.  Can we just make
this switchover now and agree to work with Jan when he shows up?  I may be
wrong but I'll bet that fontconfig isn't something that Jan feels a lot of
personal ownership of fontconfig.

cgf

Re: [ITA] X.Org X11R7.4

[Jan Nieuwenhuizen]

Op maandag 10-11-2008 om 15:21 uur [tijdzone -0500], schreef Christopher
Faylor:

> >> Just waiting for fontconfig now.  ITA sent five days ago and no response
> >> from Jan.

Ouch.  Sorry for the late response, please adopt and go ahead.

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Jan Nieuwenhuizen wrote:
> Ouch.  Sorry for the late response, please adopt and go ahead.

No problem.  Thanks,


Yaakov
Cygwin/X

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkZtvQACgkQpiWmPGlmQSNuLgCfeHJrvLyLuHYuU2FCXc1Ae6sD
v1MAn3hUFk7yZ3L+G66xli3X9ir+a4KY
=7LQ/
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yaakov (Cygwin Ports) wrote:
> 4) An announcement will be made on cygwin-xfree-announce@ with all the
> details.

I sent an announcement this morning, and it showed on
cygwin-xfree-announce@, but it wasn't echoed to cygwin-xfree@.  The last
announcement (ted, on 19 May) *was* echoed, as were previous ones.


Yaakov
Cygwin/X
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkaHkMACgkQpiWmPGlmQSOcBACguOKq+jipQWGob/1IkGUrKwXh
1yUAnAoIU/Vh94bGaGHDCISZigVe+Mej
=GwP6
-----END PGP SIGNATURE-----

Re: [ITA] X.Org X11R7.4

[Christopher Faylor]

On Tue, Nov 11, 2008 at 06:07:31PM -0600, Yaakov (Cygwin Ports) wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>Yaakov (Cygwin Ports) wrote:
>> 4) An announcement will be made on cygwin-xfree-announce@ with all the
>> details.
>
>I sent an announcement this morning, and it showed on
>cygwin-xfree-announce@, but it wasn't echoed to cygwin-xfree@.  The last
>announcement (ted, on 19 May) *was* echoed, as were previous ones.

cygwin-xfree-announce doesn't have an automatic resender for
cygwin-announce.

I'll put it on my todo list.

cgf