This is the mail archive of the cygwin-apps mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 12/6/2014 12:57 PM, Corinna Vinschen wrote:
On Dec 6 12:40, Ken Brown wrote:On 12/6/2014 11:57 AM, Corinna Vinschen wrote:Hi, isn't it rather annoying that even Base packages have dependencies outside the Base category? So, even if I perform a plain Base-only installation, I get asked if dependencies shall be fullfilled, which, as a question, is more than borderline anyway. Therefore, shouldn't we put all packages Base packages depend on into Base as well?That makes sense to me. The popup about dependencies could be confusing for someone installing Cygwin for the first time.ACK.Also, can we automate this?I'm not sure that's a good idea. If the dependencies of a Base package change, it's probably good for this to be noticeable, in case it was due to a packaging error.Uh, I was only talking about automating to add the categories to all affected packages once and get a list of packages to send to this list.
I just did a test install on each architecture and extracted the info from setup.log.
Both arches: ============ _autorebase _update-info-dir bzip2 ca-certificates groff less libargp libattr1 libblkid1 libbz2_1 libffi6 libgcc1 libgdbm4 libgmp10 libiconv libiconv2 libintl8 liblzma5 libmpfr4 libncursesw10 libopenssl100 libp11-kit0 libpcre1 libpipeline1 libpopt0 libsmartcols1 libstdc++6 libtasn1_6 libuuid1 lynx p11-kit p11-kit-trust popt xz zlib0 32-bit only: ============ libcharset1 libncurses10 64-bit only: ============ libreadline7 Ken
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |