[Bug 880146] New: create a project for sdcc, probably in CrossToolchain:...
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c0 Summary: create a project for sdcc, probably in CrossToolchain:... Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: OBS Request AssignedTo: mrueckert@suse.com ReportedBy: sbrabec@suse.com QAContact: adrian@suse.com CC: duwe@suse.com, max@suse.com, cyberorg@opensuse.org, kte608@mail.usask.ca, bugs@vdm-design.de, novel_ns@linhard.dk, opensuse@dschung.de, dl8fcl@t-online.de, wk@ire.pw.edu.pl, rneuhauser@suse.com Found By: --- Blocker: --- sdcc is a cross compiler that covers Zilog z80, Maxim ds390 and ds400, Motorola HC08, PIC16 and PIC18. The project is spread over many places in the Build Service without any logical location. It would be nice to have a devel repository for that. As it targets different platforms than other CrossToolchain: projects, it would be good to create a dedicated project. Possible project names: CrossToolchain:sdcc CrossToolchain:small_devices CrossToolchain:micro CrossToolchain:8bit Possibly interested users: Roman Neuhauser (roman-neuhauser) Wojciech Kazubski (wkazubski) Torsten Duwe (duwe) Torben Mikael Hansen (torhans) Jigish Gohil (cyberorg) Walter Fey (dl8fcl) Reinhard Max (rmax) Thomas Zimmermann (Heinervdm) Peter Siegel (siegelpeter) (has no Bugzilla contact, submit is 7 years old) (MichaelSpr) (has no Bugzilla contact, submit is 5 years old) Karl Edler (kte608) Gregor Dschung (chkpnt) Stanislav Brabec (sbrabec) Note: CrossToolchain (master) project does not exist as well, so the project has to be crated by te BuildService admin. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c1 --- Comment #1 from Thomas Zimmermann <bugs@vdm-design.de> 2014-05-27 18:30:00 UTC --- I'm indirectly interested in sdcc. It's dependency of sigrok (a tool for serval logic analysers). sigrok could also be included in some devel project, but for this CrossToolchain is not the proper place. Another possible devel project for sdcc could be devel:tools:compiler -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c2 --- Comment #2 from Stanislav Brabec <sbrabec@suse.com> 2014-05-27 23:35:21 CEST --- Yes, devel:tools:compiler is another option. sigrok can fit to hardware or a dedicated project in driver: sdcc could be aggregated there. I have another candidate that can be hosted with sdcc: intelhex (already packaged), and one that would depend on sdcc: DPF-AX (digital photo frame firmware for use as a remote display; not yet packaged) Having a dedicated repository for sdcc could have a possible future benefit: Any project that requires sdcc can inherit the whole project without need to aggregate or link. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c3 Marcus Rückert <mrueckert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |sbrabec@suse.com --- Comment #3 from Marcus Rückert <mrueckert@suse.com> 2014-05-28 09:10:19 UTC --- devel:tools:compiler would be a good one imho or if you really want a different project devel:tools:microcontroller? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c4 --- Comment #4 from Thomas Zimmermann <bugs@vdm-design.de> 2014-05-28 09:29:12 UTC --- If we agree that sdcc is in a good shape, i think that we can get it into factory soon and then we don't need a separate repository any more. And then devel:tools:compiler would fit best in my opinion. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c5 --- Comment #5 from Reinhard Max <max@suse.com> 2014-05-28 14:59:25 CEST --- AFAICS devel:tools:compiler currently only has packages that are related to compiling stuff for the host OS and/or architecture. Therefore I don't think it is a good fit for sdcc and other compilers for microcontrollers. Also, I don't think CrossToolchain is a good name for what it is currently used. I'd rather expect to find cross-compilers for Linux on different architectures there (or for other OSes on the same architecture) than tools for microcontrollers which are often not even called cross compilers as they target CPUs for which native compilers are unfeasible. What I'd like to see is a project that can hold all sorts of tools related to microcontrollers and other electronics developmen, such as compilers, flashing tools, simulators, but also CAD software for electronic circuits and tools like sigrok. I am just not sure what the right name for such a project would be and where it best fits into the current hierarchy. Also, whether it should be a flat project or have subprojects for the different controller families etc. An argument against per family projects could be that e.g. SDCC supports several controller families (IIRC from a single binary). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c6 Stanislav Brabec <sbrabec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|sbrabec@suse.com | --- Comment #6 from Stanislav Brabec <sbrabec@suse.com> 2014-05-28 16:30:10 CEST --- Reinhard Max: Your suggestion also looks well. Should we have project like electronics or (for example) hardware:design? We already have: arduino in CrossToolchain:avr and many homes avr-gcc in CrossToolchain:avr and many homes avrdude in CrossToolchain:avr and many homes cross-msp430-jtag in CrossToolchain:msp430 openocd in hardware (and Factory) and many homes pcb in science (and Factory) and many homes geda* in science (and Factory) and many homes ems-flasher in hardware and one home *ftdi* in several homes (well, it can do also magic with serial cable, so it is not clearl whether hardware or new project) ... and something in perl project devel:languages:perl:CPAN-* The hardware project has a description: This repository contains tools for using, configuring or fine tuning various types of hardware, both external and internal. We can say, that hardware repository is intended for using this hardware on Linux, and the new repository will be intended for general development of such hardware. The new project can have a description: This repository contains tools for hardware design and development. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c7 --- Comment #7 from Torsten Duwe <duwe@suse.com> 2014-05-28 14:44:08 UTC --- May I add kicad, maybe fritzing (like geda) urjtag (like OpenOCD or flashers) Haven't checked whether there are packages yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c8 --- Comment #8 from Wojciech Kazubski <wk@ire.pw.edu.pl> 2014-05-28 15:22:17 UTC --- (In reply to comment #6)
Should we have project like electronics or (for example) hardware:design?
Project electronics already exists and contains 11 packages, 2 of them broken. The last openSUSE release there is 11.4 and also old Centos and RHEL. Wojciech Kazubski -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c9 --- Comment #9 from Stanislav Brabec <sbrabec@suse.com> 2014-05-28 17:47:32 CEST ---
Project electronics already exists and contains 11 packages, 2 of them broken.
Yes, and packages are relevant to those suggested here. Just needs to add more maintainers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c10 --- Comment #10 from Reinhard Max <max@suse.com> 2014-05-28 17:54:51 CEST --- (In reply to comment #6)
Should we have project like electronics or (for example) hardware:design?
Yes, I was thinking along these lines, but still search for a name that fits both, the hardware and the firmware aspects that we want to cover with the new project. If I had to pick among these two names, I'd prefer electronics, because hardware:design sounds too speciffic and doing electronics these days almost inevitably means that some sort of programmable device and firmware are involved.
We can say, that hardware repository is intended for using this hardware on Linux, and the new repository will be intended for general development of such hardware.
Yes, but the new repository shall include firmware and not be limited to "such" hardware (in the sense of computer periphery).
The new project can have a description:
This repository contains tools for hardware design and development.
How about "This repository contains tools for developing electronic circuits and firmware for microcontrollers" ? (In reply to comment #8)
Project electronics already exists and contains 11 packages, 2 of them broken. The last openSUSE release there is 11.4 and also old Centos and RHEL.
Seems to have quite some overlap with CrossToolchain:avr already. I'd say let's revive this for the new purpose, but shall it be flat or is it better to have subprojects for the different µC architectures and other tools? e.g.: electronics:avr electronics:msp430 ... electronics:tools (logic analyzers, oscilloscopes, target-independent programmers, JTAG) electronics:cad -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c11 --- Comment #11 from Stanislav Brabec <sbrabec@suse.com> 2014-05-28 18:07:49 CEST --- I would start with one project. Many projects combine several chips and need several toolchains. There could be several reasons for splitting to sub-projects: - Too many packages in one project. - Packages need customized toolchain. - Some packages need different versions of toolchain. - Some package breaks another one. I guess that nothing of it happens here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c12 --- Comment #12 from Torsten Duwe <duwe@suse.com> 2014-05-28 16:42:16 UTC --- (In reply to comment #10)
How about "This repository contains tools for developing electronic circuits and firmware for microcontrollers" ?
Sounds good. Where shall we draw the line, between RockBox and an android distribution? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c13 --- Comment #13 from Reinhard Max <max@suse.com> 2014-05-28 19:30:04 CEST --- Would "everything that is too small (in whatever dimension) to run a Linux kernel" be a suitable definition for "microcontroller" in the scope of this project? It would certainly rule out Android, but OTOH there are architectures like ARM and MIPS that have members on both sides of the line. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c14 --- Comment #14 from Thomas Zimmermann <bugs@vdm-design.de> 2014-05-30 11:38:10 UTC --- (In reply to comment #7)
May I add
kicad, maybe fritzing (like geda)
urjtag (like OpenOCD or flashers)
Haven't checked whether there are packages yet.
kicad is in science and Factory fritzing is in Education and Factory urjtag exists in 2 homes I would also add sigrok + all dependencies (but the released versions not the git snapshots) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c15 --- Comment #15 from Stanislav Brabec <sbrabec@suse.com> 2014-05-30 17:40:40 CEST --- Adrian or Marcus: Could you add me (and/or anybody else from this discussion) to users of electronics project? It seems that we reached a consensus. There is also a package electronics-menu in science. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c16 --- Comment #16 from Adrian Schröter <adrian@suse.com> 2014-06-02 07:00:41 UTC --- sbrabec got added to electronics project now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c17 Stanislav Brabec <sbrabec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #17 from Stanislav Brabec <sbrabec@suse.com> 2014-06-02 19:01:43 CEST --- Thanks, Adrian. If you want to participate, please ping me in a mail. I went through all sdcc instances and copied the one from Wojciech Kazubski (wkazubski) home:wkazubski:hamradio, as he already packaged the latest version. Also dependent gputils was copied from there. Packagers of sigrok are encouraged to participate as well. It would be good to create .changes files for packages to track important changes, names of patches, numbers of bugs etc. (For Factory packages it is mandatory.) Also please create osc package description (e. g. using "osc updatepacmetafromspec"), so people searching for packages will see the package description. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c18 --- Comment #18 from Thomas Zimmermann <bugs@vdm-design.de> 2014-06-02 19:14:20 UTC --- @Reinhard Max I've synced my sigrok packages (which were originally from you) again with yours. My changes are mainly that I've changed to released versions. Which version would you prefer for electronics? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c19 --- Comment #19 from Reinhard Max <max@suse.com> 2014-06-03 10:34:35 CEST --- For Factory integration we generally prefer released versions unless there is a really good reason to go for snapshots. For the sigrok packages in my home (which IIRC were the first sigrok packages in the build service) I went with the snapshots, because at that time the released versions were several months old and did not yet have the Cypress FX2 firmware I was interested in. As I haven't followed the sigrok project very closely over the last year or so, I can't really say what's better at this point in time. What do you think, are they now releasing frequently enough and/or has development settled down enough that we can go for released versions or is it still such a moving target that it seems better to stick with the snapshots? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c20 --- Comment #20 from Torsten Duwe <duwe@suse.com> 2014-06-03 08:48:33 UTC --- I need some GUI API features for my PWM decoder which were not available in the last release, hence the updated versions in my home. Also note that it needs a current libusb (post 13.1): -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c21 --- Comment #21 from Reinhard Max <max@suse.com> 2014-06-03 10:55:32 CEST --- (In reply to comment #20)
[...] hence the updated versions in my home.
Updated as in newer releases or updated as in snapshots?
Also note that it needs a current libusb (post 13.1):
OK, so still a moving target... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c22 --- Comment #22 from Thomas Zimmermann <bugs@vdm-design.de> 2014-06-03 08:56:47 UTC --- I was also only interested in support for the Cypress FX2. They are releasing new version about every half a year. As I'm not interested in support for new devices this is frequent enough for me. But if Torsten needs newer version we should stick to the snapshots (but update the versions in the spec file) I've also packages libserialport. For libusb: I don't know why they've put that version in there configure.ac, i've reduced that dependency to 1.0.9 and it still compiles. (Haven't tested it yet) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c23 --- Comment #23 from Reinhard Max <max@suse.com> 2014-06-03 17:02:45 CEST --- (In reply to comment #22)
As I'm not interested in support for new devices this is frequent enough for me.
Well, new development is not only about new devices, but also about new features such as more protocol decoders.
For libusb: I don't know why they've put that version in there configure.ac, i've reduced that dependency to 1.0.9 and it still compiles. (Haven't tested it yet)
Maybe the upstream developers just request the version they have themselves, because they don't test against older versions anymore. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c24 --- Comment #24 from Stanislav Brabec <sbrabec@suse.com> 2014-06-03 18:23:15 CEST --- I added all people from this discussion as maintainers of this project. Feel free to move and add packages there and add more interested people. Build repositories were updated to the standard set. If you need more repositories, you can add them.
Maybe the upstream developers just request the version they have themselves, because they don't test against older versions anymore.
There are subtle bugs in the code that may break particular hardware or use. It still compiles but it does not work properly. By the way, there is at least one package that works only with libusb0. The problem is deeply in the way how libusb handles incomplete transfers: bug 559697 comment 23 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c25 Stanislav Brabec <sbrabec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmitry@roshchin.org --- Comment #25 from Stanislav Brabec <sbrabec@suse.com> 2014-06-03 20:32:43 CEST --- Adding Dmitry Roshchin, maintainer of pcb, gEDA, kicad... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
electronics:tools (logic analyzers, oscilloscopes, target-independent programmers, JTAG) electronics:cad I think we can use subprojects for crosstoolchains, but all generic software must be in one repository. Many small repositories look like a hell for end user, and sometimes it's really difficult to choose which subproject id better to use for package. For example we have 500+ different packages in science
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c26 --- Comment #26 from Dmitry Roshchin <dmitry@roshchin.org> 2014-06-03 22:16:13 UTC --- 1. Project destination It's very important to decide would be electronics project just devel project for Factory, or it must be ready for end user (many people want to use latest stable applied software). 2. Project structure project without any problems for maintainers. 3. Moving packages I can move some packages from Science project: electronics-menu geda-gaf geda-xgsch2pcb gerbv gnucap gspiceui gtkwave ? iverilog ? kicad kicad-doc kicad-library ng-spice-rework (must be renamed to ngspice) pcb qucs 4. Unstable versions Electronics project must contain only stable releases, but in some cases we can provide unstable versions. For example I want to use devel version of kicad (there are too much difference between stable and devel branches). So we need to choose the best way. * all unstable packages in one repository (electronics:unstable) * separate repositories (electronics:unstable:kicad) * no unstable versions totally -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c27 --- Comment #27 from Stanislav Brabec <sbrabec@suse.com> 2014-06-04 17:06:02 CEST --- 1. It could be a Factory devel project for selected packages. 2. I agree. Subprojects make sense only for reasons listed in the comment 11. Over-sub-projecting ends with complicated setups and lots of aggregates. Large projects create no problems, as long as they do not replace generic libraries by later incompatible versions. 3. Yes. Feel free to move anything you consider as useful and replace obsolete versions in the current electronics projects. 4. Even two versions can co-exist in a single repository (and sometimes in a single computer) as long as they don't produce equally named packages. You just need a properly set Provides, Conflicts in the spec, and Prefer in prjconf. foo-next.spec Version: 1.1.1 Provides: foo = %{version} # Optional, only in case of file conflict # (update-alternatives could be another solution) # You can also use Conflicts # (then user will be asked for removal before replacement) Obsoletes: foo < %{version} %package devel ... similar same as above And project prjconf (if you see ambiguity build error): Prefer: foo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c28 --- Comment #28 from Marcus Rückert <mrueckert@suse.com> 2014-06-04 15:08:09 UTC --- do we really need to have this discussion in bugzilla or can we close it and you move it to mail? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c29 --- Comment #29 from Reinhard Max <max@suse.com> 2014-06-04 17:42:50 CEST --- Does it hurt in any way to have it here? ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c30 --- Comment #30 from Wojciech Kazubski <wk@ire.pw.edu.pl> 2014-06-05 16:54:55 UTC --- 1) We can remove avrdude and gtkwave. Both packages are broken here but avalable from main repository since openSUSE 12.2 or even earlier, so there is no need to repair them. RHEL6 also has them. I could not find them in CentOS however. 2) Shall we continue packaging for RHEL and CentOS? Those distributions are from Red Hat family and are not fully compatible with openSUSE/SLE. New packages here does not build well for them. There are some diferences in group system, library naming rules, tools used to install desktop files etc. It is posible to make a specfile covering all cases but it requires frequent use of "%if" command. See some of my packages for Fedora and openSUSE. There are some two possibilities here. One is to remove CentOS and RHEL totally and the other is to disable them by default and enable only for those packages that now build correctly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=880146 https://bugzilla.novell.com/show_bug.cgi?id=880146#c31 --- Comment #31 from Thomas Zimmermann <bugs@vdm-design.de> 2014-06-05 18:33:43 UTC --- As this repository wasn't very actively maintained I can't believe that many people out there used it. And if someone used it, it was probably not a RHEL or CentOS user. Therefore I would say we could drop these repositories. And if someone later requests repositories for other distributions we can add them again. One other thing: I've sent submit requests for sigrok and added a comment to the request for libserialport to discuss if we want to add the released packages and git packages in a subproject or just add the git packages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com